Briefast Daily Pre-Market Report

Pre-Execution Checks

1. Read configurations from the

   .env

   file in the root directory of the execution workspace. This is the only source of configurations; do not retrieve values from environment variables or read files in the skill directory. The format is one

   KEY=VALUE

   pair per line:

   BRIEFAST_URL=https://briefast.example.com
   BRIEFAST_API_KEY=Key created in the backend

   skills/daily-brief/.env.example

   is a template; copy it to the workspace root directory, rename it to

   .env

   , and fill in the actual values.
2. If

   .env

   does not exist, or either

   BRIEFAST_URL

   or

   BRIEFAST_API_KEY

   is missing or contains only whitespace, stop immediately. Clearly report which item is missing; do not collect news, draft the report, or send a POST request.
3. Do not display, record, or return the full API key.
4. Determine the report date and

   generated_at

   using Taipei Time Zone.
5. Trading Day Gate: After passing the above checks and before starting news collection, verify whether the current date (in Taipei Time Zone) is a Taiwan stock trading day. If it is a non-trading day, terminate immediately—do not collect news, analyze, draft the report, or send a POST request, and explain the reason for the market closure (weekend, or the name of the calendar entry) in the execution report. Judgment must follow only the verifiable rules below; do not rely on memory or common sense:
   • Saturdays and Sundays are always considered non-trading days; no need to check the endpoint.
   • For other dates, verify using the TWSE holiday schedule endpoint:

     https://openapi.twse.com.tw/v1/holidaySchedule/holidaySchedule

     The

     Date

     in the response uses the Minguo calendar format (e.g.,

     1150101

     corresponds to 2026-01-01). Entries are divided into two categories: those with

     Name

     or

     Description

     indicating "no market trading", "holiday", or "make-up holiday" are non-trading days; informational entries such as "start of trading period" or "last trading day" are trading days and must not be misjudged as non-trading days. Weekdays that do not match any non-trading entries are trading days; proceed as normal.
   • If verifying the endpoint fails on a weekday, retry once. If it still fails, treat it as unable to confirm closure, proceed with the full process as normal, and include the endpoint failure in the execution report. This request occurs before starting collection, and is not performed concurrently with the rate-limited sequence of TWSE requests in Batch 2; do not apply the interval rules of that batch.
   • The verification process and endpoint success/failure of the gate are only included in the execution report. In accordance with the "collection mechanism not disclosed" rule, they must not appear in the report content.

1. Collect Industry and Stock Market News

Time Window

generated_at

generated_at

curl --silent --show-error \
  --output previous.json \
  --write-out '%{http_code}' \
  --header "Authorization: Bearer ${BRIEFAST_API_KEY}" \
  "${BRIEFAST_URL%/}/api/report/2026-08-06"

404

200

generated_at

previous.json

404

401

Batch Collection

Batch 1: Cnyes (Primary Source)

{category}

https://api.cnyes.com/media/api/v1/newslist/category/{category}?limit=30

tw_stock

headline

tech

tw_macro

cnyeshouse

wd_stock

overview_md

content

stock

publishAt

Batch 2: TWSE

• https://openapi.twse.com.tw/v1/opendata/t187ap04_L

  (Major Announcements)

• https://openapi.twse.com.tw/v1/opendata/t187ap05_L

  (Monthly Revenue)

429

Batch 3: CTEE

{category}

policy

stock

finance

industry

house

tech

https://www.ctee.com.tw/rss_web/livenews/{category}

Batch 4: CNA, TechNews, LTN

https://feeds.feedburner.com/rsscna/finance

https://technews.tw/feed/

https://news.ltn.com.tw/rss/business.xml

Batch 5: International Financial News (CNBC)

https://www.cnbc.com/id/100003114/device/rss/rss.html

overview_md

calls

stock_news

Five-Batch Summary Table

Source Success/Failure and Integrity Check

• Proceed with analysis and publication as normal, using the content actually retrieved to compile the report. Failure of any single source will not stop the entire report from being published, including Cnyes—TWSE's major announcements include company symbols, monthly revenue is hard facts, and CTEE, CNA, etc., also cover Taiwan stocks. Losing any source reduces coverage density, but not the feasibility of the report. If Batch 5's foreign news (CNBC) fails, proceed with publication as normal: only the density of international context is lost, and international dynamics can still be obtained from Taiwanese media reports.
• List each missing source and the reason for failure in the execution report, so operators know the coverage level for the day. This is for operators, not readers.

overview_md

summary_md

sources

Deduplication (seen.py)

skills/daily-brief/scripts/seen.py

1. Retrieve list page data (title, URL, native ID) from the batch's source, without downloading the content.
2. Feed the candidates to

   seen.py peek

   , and only retrieve unread items.
3. Download the content of unread articles.
4. For articles with sufficient content length, use

   echo "content" | seen.py similar

   to check if they are rewritten reprints of processed articles. A similarity ≥ 0.5 is considered the same article; skip it.
5. After analysis is complete, record all processed articles (including those determined not to be reported) using

   seen.py record

   . For articles determined not to be reported, set

   "decision": "skipped"

   to avoid re-evaluating the same noise tomorrow.
6. For cross-day events, register them using

   seen.py event add 'symbol|event type|period'

   . Before writing individual stock details, check using

   seen.py event check

   ; for registered events, use continuation descriptions (e.g., "continues yesterday's revenue upside") instead of re-announcing.

seen.py similar

seen.py record

"decision": "skipped"

overview_md

event check

Previous Closing Price Reference Data

• Listed Stocks:

  https://openapi.twse.com.tw/v1/exchangeReport/STOCK_DAY_ALL

• OTC Stocks:

  https://www.tpex.org.tw/openapi/v1/tpex_mainboard_daily_close_quotes

Date

1150814

2. Analyze Industry and Individual Stocks

Common Rules

One-Sentence Headline

industries[].events[]

stock_news[]

headline

• Do not use short phrases with only a topic, no event or impact, such as "memory supply and demand" or "capacity expansion".
• Do not copy or rephrase the first sentence of

  summary_md

  with minor changes. The headline should first condense the event and its significance, and the content should then provide cause and effect, conditions, and details.
• News in the same industry category should be merged into events by topic. One event covers a set of interrelated dynamics; do not split each source article into a separate event.

Memory contract prices continue to rise; upstream product mix improves but module manufacturers face margin pressure

Memory supply and demand

New capacity to be put into operation ahead of schedule in Q4, expected to accelerate order digestion

Company announces new capacity will be put into operation in Q4

Fundamental Reference Discipline

• Revenue, EPS, gross margin, order amount, or other fundamental figures can only be referenced from public sources actually retrieved during this execution; do not fill in values based on model memory, past conversations, or common sense.
• Each figure must clearly indicate the data period in the content, e.g., "July revenue", "2026 Q2 EPS", and include the actual source in the

  sources

  of the corresponding

  stock_news

  .
• If current public data cannot be retrieved during this execution, omit the fundamental figures and related context, and only interpret based on verified news. Do not use old figures, estimates, or force-fit approximate values.

Entry Observation Focus

industries

stock_news

watch_md

• Industry observation points should link to supply and demand, price, or policy dynamics reported in each event of the category, such as the results of the next contract price announcement or the implementation of regulatory measures.
• Individual stock observation points should link to the news referenced in the entry or fundamentals retrieved during this execution, such as the actual commissioning time of new capacity or whether the next period's revenue reflects orders.
• Do not rewrite the content of

  watch_md

  into the

  summary_md

  of industry events or individual stocks, and do not use templated empty phrases without specific events, indicators, or time points, such as "continue to follow up on subsequent developments".

First Round: Industry

industries

Sorting Criteria

1. Actual changes in price and supply/demand — price increases/decreases, production cuts, inventory turning points, freight rate changes, which have altered the industry's profit and loss structure.
2. Policy regulation to be enforced — tariffs, bans, new regulations, exogenous and applicable to the entire industry.
3. Scope of impact — affecting the entire supply chain or multiple companies, greater than affecting only a single link.
4. Sustainability — structural turning points (capacity cycles, technology generations) are greater than one-time events.
5. Certainty — occurred facts > official outlook > institutional estimates > market rumors.

Event Writing Method

industries[].events[]

headline

summary_md

Industry Event Writing Tips

1. Start with the amount of change — write direction, magnitude, and period, not state descriptions like "market is booming". Magnitude and comparison basis are limited to those stated in the news (e.g., if the news writes "highest in nearly 45 months", use it as is), do not reference historical figures or seasonal common sense from memory. If the news does not provide a magnitude, rewrite it as specific facts for policy events: effective time and constrained objects.
2. Attribute to supply side or demand side — the same price increase, supply contraction (production cuts) will end with resumption of production, while demand-driven increases are more sustainable; this is the basis for judging sustainability. If the news does not state which side the driver comes from, clearly write "driver unknown", do not infer the cause on your own—this is the only entry where explicitly stating missing data is allowed, because silence in attribution will be interpreted as implicit certainty.
3. Write impact distribution — a change usually affects more than one party: who benefits, who faces pressure, who can pass on costs. For manufacturing, write about upstream, midstream, and downstream; for financial regulation, write about regulated objects and exempt objects; for real estate, write about buyers, sellers, and developers.
4. Indicate cycle or structure — for events ranked higher and written in depth, the content should explain whether this is a cyclical fluctuation (e.g., freight rate rebound) or a change in the rules of the game (e.g., capacity relocation), corresponding to the sustainability judgment in Sorting Criterion 4.

Fixed Four Industry Categories

industries

events

headline

summary_md

Second Round: Individual Stocks

calls

stock_news

Sorting Criteria

1. Quantifiable profit impact — financial reports, monthly revenue, orders with specific amounts and delivery periods.
2. Fact level — company announcements > company outlook > foreign institutional views > supply chain news > market rumors.
3. Reflection time point — verifiable this quarter, greater than next year, greater than long-term vision.
4. Change in competitive position — irreversible position shifts such as new customers, new markets, technological breakthroughs.
5. Capital and chip dynamics — only used as supporting bonus points, cannot alone constitute importance.

Entry Writing Method

stock_news[].summary_md

Individual Stock Entry Writing Tips

1. Judgment first — the first sentence of the content should state what judgment this news has changed, then go back to explain the event; do not narrate in chronological order. This sentence should be one level deeper than the

   headline

   : the headline gives the conclusion, the first sentence gives the mechanism or conditions. For entries with

   call: "none"

   , rewrite the first sentence to "why the direction cannot be judged", do not force a judgment for the sake of sentence structure.
2. Magnitude conversion — amounts in the news are only meaningful when converted to relative magnitudes for the company, but only write this if the benchmark figures (revenue, capital, etc.) are actually retrieved during this execution. If not retrieved, only write the absolute amount stated in the news, omit the entire conversion sentence, and do not leave a placeholder.
3. Expectation gap positioning — indicate whether this is new information or a continuation of what the market already knows; this is the core of bullish/bearish judgment. Only rely on expectations stated in the news itself (e.g., "better than institutional estimates") or cross-day events registered in

   seen.py event check

   ; if neither exists, do not write the expectation gap.
4. Translate PR language —还原形容词 in press releases to facts: "deepen layout" or "strategic cooperation" without amounts and delivery periods are downgraded to intentions rather than orders. If there are figures, retain the strength of the figures, do not weaken them.
5. Named attribution — write who said it as stated in the news: which foreign institution, target price adjusted from how much to how much. If the news only uses vague subjects like "foreign institutions" or "supply chain", retain the vagueness, do not fill in institution names on your own, and simultaneously lower the fact level by one level according to Sorting Criterion 2.

Individual Stock Bullish/Bearish Judgment

short_bull

short_bear

long_bull

long_bear

none

Judgment Principles

• No upper limit on quantity. List all that can be judged from the day's news.
• No mandatory threshold. The execution model independently judges whether the news content is sufficient to give a direction.
• Distinguish between occurred facts, company outlook, analyst views, and market rumors. Do not write rumors as confirmed facts.

• calls

  and

  stock_news

  only include listed and OTC Taiwan stocks and their Taiwan stock symbols. International market dynamics and news of foreign listed companies are only written into

  overview_md

  ; even if related to Taiwan's supply chain, foreign symbols must not be included in

  calls

  or

  stock_news

  .
• Foreign news articles in Batch 5 can only be used as material for

  overview_md

  and industry event background context; do not create or support any entries in

  calls

  and

  stock_news

  —even if foreign news directly mentions Taiwanese companies, individual stock-level analysis must still be based on Taiwanese media and TWSE sources.
• Previous closing prices are only used as analysis context (judging whether upside has been reflected, as a benchmark for magnitude comparison) and as a source for report references. When citing previous closing prices, clearly indicate the price date (e.g., "previous close (8/14) 1,080 yuan"), and only use data retrieved during this execution and passed date verification. For stocks with no news within the window, even if the previous close rose or fell sharply, do not create entries in

  calls

  or

  stock_news

  ; price changes can at most be used as context in entries with existing news basis.

Calls Entry Rules

• Use a single line, specific

  reason

  supported by news.
• Have corresponding details with the same

  symbol

  in

  stock_news

  .
• The corresponding

  stock_news

  lists at least one news source.

call: "none"

stock_news

3. Compose and Verify Report JSON

{
  "date": "2026-08-07",
  "headline": "US stocks closed red, pre-market sentiment is bullish; Bullish: TSMC",
  "overview_md": "Four major US stock indices closed red; SOX was driven by AI demand; Taiwan stock pre-market sentiment is bullish.",
  "watch_md": "- TSMC will announce July revenue after market close\n- US July CPI will be announced tonight\n- Observe foreign futures net short positions",
  "calls": {
    "short_bull": [
      {
        "symbol": "2330",
        "name": "TSMC",
        "reason": "2nm production ramps up ahead of schedule and foreign institutions raise target prices; short-term themes and capital dynamics turn bullish simultaneously."
      }
    ],
    "short_bear": [],
    "long_bull": [],
    "long_bear": []
  },
  "industries": [
    {
      "name": "Technology",
      "events": [
        {
          "headline": "2nm production ramps up ahead of schedule; demand for equipment and materials is expected to rise",
          "summary_md": "TSMC's advanced process schedule is ahead of plan; order visibility for related equipment and material suppliers is expected to improve."
        },
        {
          "headline": "AI accelerator repeat orders drive up packaging and testing utilization; upstream benefits directly",
          "summary_md": "Repeat orders for accelerators have increased packaging and testing capacity utilization; revenue momentum for advanced packaging and testing supply chains is more clear."
        }
      ],
      "watch_md": "- Track whether TSMC maintains the 2nm mass production schedule in its next earnings call\n- Observe whether packaging and testing companies' next month's revenue reflects repeat orders"
    }
  ],
  "stock_news": [
    {
      "symbol": "2330",
      "name": "TSMC",
      "call": "short_bull",
      "headline": "2nm production ramps up ahead of schedule and foreign institutions upgrade ratings; short-term themes and capital dynamics turn bullish simultaneously",
      "summary_md": "Supply chain sources report that 2nm production is ramping up ahead of schedule; multiple foreign institutions have raised target prices.",
      "watch_md": "- Track the 2nm mass production schedule announced in the company's next earnings call",
      "sources": [
        {
          "title": "TSMC's 2nm production reported to ramp up ahead of schedule",
          "url": "https://example.com/tsmc-2nm"
        }
      ]
    },
    {
      "symbol": "2317",
      "name": "Hon Hai",
      "call": "none",
      "headline": "Electric vehicle cooperation remains at memorandum stage; order visibility is insufficient to judge direction",
      "summary_md": "Announced an electric vehicle cooperation memorandum; short-term contribution and long-term formal orders are still unclear.",
      "watch_md": "- Track whether the cooperation memorandum is converted into a formal order with amount and delivery period",
      "sources": [
        {
          "title": "Hon Hai announces electric vehicle cooperation memorandum",
          "url": "https://example.com/hon-hai-ev"
        }
      ]
    }
  ],
  "generated_at": "2026-08-07T07:50:00+08:00"
}

• date

  is a valid

  YYYY-MM-DD

  date.

• headline

  ,

  overview_md

  ,

  watch_md

  all have non-blank content.

• calls

  exactly contains four arrays:

  short_bull

  ,

  short_bear

  ,

  long_bull

  ,

  long_bear

  .

• stock_news[].call

  only uses the five values in the table.

• industries[].name

  only uses "Technology", "Finance", "Traditional Industries", "Real Estate".
• Each

  industries

  entry has at least one

  events

  event.
• Each

  industries[].events[]

  has non-blank

  headline

  and

  summary_md

  .
• Each

  stock_news[]

  has a non-blank

  headline

  .
• Each

  industries

  and

  stock_news

  entry has 1–2 non-blank, verifiable observation points in

  watch_md

  that are not repeated in the

  summary_md

  of industry events or individual stocks.

• calls

  and

  stock_news

  do not contain foreign listed companies or foreign symbols; only include listed and OTC Taiwan stocks.
• Each

  symbol

  in calls entries can be found in

  stock_news

  .
• Each calls entry has a one-line reason, and the corresponding

  stock_news

  has at least one source.
• Each source has a non-blank URL.
• Major news with unclear direction uses

  call: "none"

  and does not appear in the calls lists.

• generated_at

  uses RFC 3339 format with time zone.
• All figures, expectations, and attributions can be traced back to news or retrieval results from this execution; no memory-filled values; missing data is omitted entirely instead of using placeholder phrases (the only exception is "driver unknown" in industry events).
• The five-batch summary table is complete: all five batches have counts, no missing items; if sources failed, the missing list is prepared for reporting (only included in the execution report, not in the report content).
• Previous closing price retrieval has reported the number of items and data date; previous closing prices cited in the report all indicate the price date and come from data retrieved during this execution and passed date verification; no calls or stock_news entries are based solely on price changes.
• The report content does not mention source lists, batch structure, or any source omissions.
• Remember to use

  GET /api/report/{date}

  to confirm whether a report already exists for the current

  date

  before sending the POST in Step 4; if it exists, compare the number of industry entries and individual stock entries.

report.json

4. POST to Website API

Overwrite Comparison for Same-Day Re-runs

curl --silent --show-error \
  --output existing.json \
  --write-out '%{http_code}' \
  --header "Authorization: Bearer ${BRIEFAST_API_KEY}" \
  "${BRIEFAST_URL%/}/api/report/2026-08-07"

404

200

industries

stock_news

existing.json

• If both are no less than the existing version: proceed with POST as per the process below, no additional confirmation needed.
• If either is less than the existing version: stop, do not send POST. Explain why the content is less this time (e.g., a source failed, there were indeed few news items on the day), and wait for instructions before deciding whether to overwrite.

401

401

Submission

.env

curl --silent --show-error \
  --output response.json \
  --write-out '%{http_code}' \
  --request POST \
  --header "Authorization: Bearer ${BRIEFAST_API_KEY}" \
  --header "Content-Type: application/json" \
  --data-binary @report.json \
  "${BRIEFAST_URL%/}/api/report"

• 200

  : Confirm that the response is

  {"ok":true,"date":"current date"}

  , report successful publication.

• 400

  : Considered a failure. Read and retain the complete response body; correct the payload according to

  errors

  and resend once. If the correction method cannot be determined or it still fails after correction, stop and report the response body verbatim.

• 401

  : Considered a failure. Do not retry, do not guess or change keys; stop and attach the complete response body.

• 5xx

  : Considered a failure. Retry once using the exact same payload; if it is still not 200 on the second try, stop and attach the last response body, and note the first and second statuses.
• Other non-

  200

  : Considered a failure, do not retry, stop and attach the complete response body.

date