market-daily-strategist

name	market-daily-strategist
description	Use when the user asks for daily market strategy, broad-market trading guidance, pre-market strategy, close recap, or one-name long-term recommendation reports covering US stocks, Japanese stocks, or A-shares. Also use for natural current-session or next-session market questions such as "明天日股如何做", "今天日股怎么做", "日经明天怎么看", "美股今晚怎么做", "纳指今晚怎么看", "A股明天怎么操作", or "大盘今天怎么办" when the intent is market-level strategy. Applies to ad-hoc requests that need live market/news data, strict no-fabrication data discipline, price-confirmed catalysts, and decision-oriented trading guidance.
metadata	{"short-description":"Daily market strategy and one-stock recommendation reports"}

Market Daily Strategist

Use this skill for the user's market reports. This is not a scheduler; ignore any clock-trigger wording from the original prompts. Route by user intent:

• 美股盘前、开盘前、pre-market、盘前策略、美股今晚怎么做、美股明天如何做、今天美股怎么看、纳指今晚怎么看、标普明天怎么看、美国市场怎么做、美股大盘策略: read references/us-pre-market.md.
• 美股收盘、昨晚美股、复盘、close recap: read references/us-close-briefing.md.
• 日股盘前、日经盘前、日本开盘前、明天日股如何做、今天日股怎么做、日经明天怎么看、日本市场怎么做、日股大盘策略: read references/jp-pre-market.md.
• 日股收盘、今天日股复盘、日本市场复盘: read references/jp-close-briefing.md.
• A股盘前、A股早盘、开盘前策略、明天A股如何做、今天A股怎么做、A股明天怎么操作、大盘今天怎么办、沪指明天怎么看、创业板明天怎么看、科创板今天怎么做、A股大盘策略: read references/cn-pre-market.md.
• A股收盘、A股复盘、今天A股市场回顾: read references/cn-close-briefing.md.
• 美股长线推荐、推荐一只美股: read references/us-long-term.md.
• 日股长线推荐、推荐一只日股: read references/jp-long-term.md.
• A股长线推荐、推荐一只A股/ETF/LOF: read references/cn-long-term.md.

If the user asks a broad current-session or next-session question such as 明天/今天/今晚 + 市场/大盘/美股/纳指/标普/日股/日经/TOPIX/A股/沪指/创业板/科创板 + 如何做/怎么做/怎么看/怎么操作/怎么办, treat it as a pre-market, current-session, or next-session strategy request for the named market, not as a generic macro question. If the market is named by an index, map it to the corresponding market reference above. If the user says only 盘前信息, 收盘复盘, 大盘怎么做, or 推荐一只股票, infer the market from the conversation. If unclear, ask one concise question for the market: 美股、日股、还是A股.

Always read references/shared.md first, then only the one task-specific reference that matches the user request.

Reference reading rule: when this skill selects a reference file, first scan the file structure, then read the sections and nearby guardrails relevant to the current task. Read the complete file when it is short, when the task is broad or strategic, or when partial reading could miss constraints. Do not rely on stale memory or heading-only scans.

During question decomposition, actively expand broad market, sector, theme, and long-term stock questions into mainline x funds x game x cycle when that lens can change the conclusion, even if the user did not explicitly ask for it. In those cases, read the relevant sections of references/global-mainline-funds-game-cycle.md.

Core Workflow

1. Identify the report type and market.
2. Confirm current date/time in Japan time and whether the relevant next or current session is open. If the market is closed, follow the task-specific closed-market rule instead of forcing a normal report.
3. Gather latest data from reliable live sources. Use market-specific primary sources listed in the task reference.
4. For U.S. and Japan market reports, treat the current DayTrading.monster 24H Feed as the most important public theme-discovery source before synthesis. Use both current-page layers when they materially fit the question: the Market narrative monitor for condensed cross-topic state, and the X account monitor for raw account-level market posts. These layers guide what to verify; they do not replace live market news, price/sector confirmation, filings, or official disclosures.
5. Optionally run the narrative-status helper as a pre-screen for the active market when a broad report needs current theme discovery:
   • US: python3 skills/market-daily-strategist/scripts/narrative_status.py --market us
   • Japan: python3 skills/market-daily-strategist/scripts/narrative_status.py --market jp
   • A-shares/China: python3 skills/market-daily-strategist/scripts/narrative_status.py --market cn
   • Global/cross-asset: python3 skills/market-daily-strategist/scripts/narrative_status.py --market global Treat the output as social-media-derived narrative candidates from the current Market narrative monitor only. Account quality is assumed acceptable; the required check is timeliness: feed generatedAt/reviewedAt should be fresh, and each entry's sourceCreatedAt/updatedAt must fit the report window. If the helper returns stale_feed, errors, or stale entries, skip or downgrade that layer rather than forcing it into the report. The helper reads the current DayTrading.monster Market narrative monitor (https://daytrading.monster/tools/24hfeed/narrative_status.json). For pre-market and close-review reports, use only the current runtime JSON state or rendered page state when the report needs current cross-asset or theme discovery, then verify decisive items with live news, original/source reporting when available, and prices. Do not fetch or mine historical/archive 24H Feed data for normal reports. Do not use the HTML page's noscript or static SEO summary as current evidence because it can lag the runtime app. When raw X account context would materially improve a report, the same page also exposes an X account monitor: https://daytrading.monster/tools/24hfeed/accounts.json lists accounts and freshness; per-account current market posts are available at paths such as https://daytrading.monster/tools/24hfeed/{handle}/market_recent.json. Treat this as social-media-derived source context, not verified news. For Japan PTS discovery, https://daytrading.monster/pts/ is a frontend app. Do not read its noscript SEO fallback as current PTS evidence because it can lag the rendered app. Use the current runtime JSON (https://daytrading.monster/pts/data.json) or a rendered page/browser view. Interpret mode1 as day-session movers, mode2 as after-close movers, and mode3 as night-session movers; always check the matching mode*UpdatedAt timestamp before citing movers. For broad macro price context, DayTrading.monster home (https://daytrading.monster/) is useful for discovering TradingView symbols and whether a symbol is D, 24h, or 365d, but the latest widget prices and runtime news state are not visible in plain HTML/noscript fetches. Use a rendered browser/widget view or a programmatic TradingView/scanner equivalent before citing live prices from that dashboard. In the final report prose, do not name DayTrading.monster, 24H Feed, dashboard/widget names, page names, or other aggregator/source names by default. Describe the evidence generically as 当前叙事预筛, 当前价格代理, PTS异动, 评级线索, or 行情确认. URLs may be included only in a dedicated source list when the user asks for sources or when an audit trail is required.
6. Never invent prices, index levels, futures, percentage moves, gamma/options levels, flows, valuation, financials, or news. If unavailable, say 暂无具体数值 or 初步.
7. Apply shared.md market-news and local-data discipline: scan enough current news before finalizing, avoid broad local-data sweeps, and prioritize items confirmed by price action, volume, flows, earnings, ratings, policy catalysts, or direct trading relevance.
8. Produce pure simplified Chinese output in the exact structure required by the task reference.

Supporting Skills

This skill is a report router and synthesis layer. Use other market skills when they materially improve the report, but keep calls selective.

• Use macro-news-check when the report depends on current macro tape: rates, FX, oil, gold, commodities, central banks, economic data, geopolitics, broad risk sentiment, or live futures confirmation.
• For U.S. reports, use official moomoo skills as selective evidence helpers when installed: moomoo-news-search and moomoo-stock-digest for timely company/news context, moomoo-comment-sentiment for community heat, moomoo-capital-anomaly for capital-flow anomalies, moomoo-derivatives-anomaly for U.S.-applicable option anomaly dimensions, and moomoo-technical-anomaly for a first-pass technical anomaly scan. These are data and anomaly layers; keep this skill responsible for strategy synthesis.
• Use us-stock-move-reason for 1-3 important U.S. movers when the catalyst, earnings/guidance acceptance, news interpretation, option/flow anomaly, or community reaction needs a dedicated move-reason pass.
• Use us-stock-gamma-moomoo for US index/ETF option structure when SPX/SPY/QQQ/NQ gamma, GEX, 0DTE, dealer positioning, option walls, or intraday conversion levels could change the strategy.
• Use stock-technical-analysis for selected index/ETF/stock levels when the answer needs support/resistance, trend confirmation, intraday execution timing, breakout/pullback validation, or stop levels.
• Use jp-stock-move-reason or cn-stock-move-reason for 1-3 genuinely important Japanese/A-share movers when the catalyst is unclear or the stock drives the day's theme. Do not run move-reason analysis on every mover.
• Use stock-sentiment-analysis when crowding, leader/follower status, emotion cycle, old-leader rebound, or theme acceptance/rejection affects the trading conclusion.
• Use the narrative-status helper only as a theme-discovery and sentiment pre-screen. It can suggest which narratives to test, but it must not replace macro-news confirmation, market prices, filings/news, PTS/pre-market movers, sector breadth, gamma/options checks, or technical confirmation.
• Use 东方财富妙想 skills for A-share reports and sector questions when available, as supplemental data/search/screening only. They do not replace the report's existing market-news discipline, price-confirmed catalyst checks, emotion-cycle and leader/follower judgment, macro/technical confirmation, or source hierarchy. Use mx-data for quote, valuation, fund-flow, financials, index/sector data; mx-search for timely news, announcements, research, policy, and event explanations; mx-xuangu for sector/concept constituents, related-stock lists, condition screens, and peer comparisons. For questions like A股某板块有哪些股票, 相关股, 概念股, 龙头股, or 板块成分, try mx-xuangu first when available. Use mx-zixuan only when the user explicitly asks about 东方财富 self-selected stocks, and mx-moni only for explicit simulated-trading tasks.

Cross-skill calls are operational: actually load the supporting skill's SKILL.md and required references when using it. Keep supporting-skill output compressed into the final report instead of pasting separate mini-reports.

Style

• Professional, concise, strategy-first.
• The first line is always a 60-80 Chinese-character decisive title when the task reference requires it.
• Prioritize actionable conclusions: 追高、等回踩、低吸、减仓、观察、避开财报风险、仓位与止损.
• Attribute important live figures and news to sources.
• When internal/current-page helper data is used, do not name DayTrading.monster, 24H Feed, dashboard/widget names, page names, or other aggregator/source names in the report prose by default; source URLs may appear in a separate source list when needed.
• For recommendation reports, clearly state that the output is not financial advice.

Guardrails

• Do not open or depend on the DTM /themes project or https://daytrading.monster/themes/ unless the user explicitly asks to update or inspect that project.
• For long-term recommendation reports, recommend exactly one target and avoid recently recommended names when that history is available in the conversation, logs, or user-provided context.
• Buy prices must be near the latest available price and within the task-specific limit, generally no more than 2% above current/latest price.