stock-dragon-head-analysis

---

name: stock_dragon_head_analysis description: Use this standalone stock strategy skill for 龙头策略 (dragon_head) analysis. Accept one or more A-share stock codes, Chinese stock names, US stock tickers, or Hong Kong stock codes, collect market/news data, and produce a Codex-readable Markdown report focused on the 龙头策略 strategy. Source strategy: ~/daily_stock_analysis/strategies/dragon_head.yaml.

龙头策略 Stock Analysis Skill

This skill is a strategy-specific variant of stock_ai_analysis. It uses the same bundled analyzer structure. User config, generated prompts, reports, and final reports for this strategy live under:

~/.stock_analysis/dragon_head/

Downloaded market-data caches are shared across strategies under ~/.stock_analysis/cache/ so users do not need to fetch the same data repeatedly.

Strategy Source

• Source file: ~/daily_stock_analysis/strategies/dragon_head.yaml
• Strategy id: dragon_head
• Display name: 龙头策略
• Category: trend
• Aliases: 龙头, 龙头战法
• Required source tools: get_realtime_quote, get_sector_rankings, search_stock_news
• Summary: 板块轮动中识别龙头股。适用于板块启动或行业催化剂出现时。

Workflow

1. Work only inside this skill directory. Do not import, inspect, or depend on files outside it during normal analysis.
2. The script creates and reads user config at ~/.stock_analysis/dragon_head/.env. Always run config check first:

python scripts/analyze.py --check-config

3. First-run hard rule: if --check-config shows CONFIG_CREATED: yes, explicitly tell the user initialization config is required before any analysis. Do not run --stocks in the same turn.
4. Incomplete-config hard rule: if required capability keys are missing for the user request, stop and ask the user to complete configuration using references/configuration.md before running analysis. Never run partial/incomplete analysis.
5. Ask for stock codes, names, or tickers if not supplied. Accept 600487, 北方华创, AAPL, 00700.HK, or mixed input like 北方华创,600487,AAPL,00700.HK.
6. Only after configuration is complete, run analysis:

python scripts/analyze.py --stocks <codes>

Use --no-llm for data-only smoke runs. Use --send-email only after the user confirms email delivery. Use --no-email for validation runs when EMAIL_ENABLED=true.

7. Open the latest prompt files under ~/.stock_analysis/dragon_head/prompts/, use the current Codex agent to generate the final analysis, and write that analysis to a Markdown file under ~/.stock_analysis/dragon_head/final_reports/.
8. The final analysis must apply the strategy rules below. Do not return a generic stock report when this skill is invoked.
9. Send email only from a finalized current-agent report:

python scripts/analyze.py --send-final-report ~/.stock_analysis/dragon_head/final_reports/<report>.md

If a generated base report exists, merge the final analysis back into the original report before sending:

python scripts/analyze.py --send-final-report ~/.stock_analysis/dragon_head/final_reports/<report>.md --base-report ~/.stock_analysis/dragon_head/reports/<base_report>.md

Strategy Rules

龙头策略（Dragon Head Strategy）

评估标准：

1. 板块领涨地位：

   • 使用 get_sector_rankings 检查该股所在板块是否为近期涨幅前列。
   • 确认该股是否在板块启动周期中率先上涨或涨停。

2. 换手率与动能（关联理念7：强势趋势股放宽）：

   • 使用 get_realtime_quote 检查换手率。龙头股换手率通常 > 5%。
   • 量比 > 1.5 说明有活跃的交易兴趣。

3. 相对强度：

   • 对比个股涨跌幅与板块平均值。
   • 真正的龙头在上涨日应跑赢板块 2% 以上。

4. 新闻催化：

   • 使用 search_stock_news 搜索板块级催化剂（政策、事件、业绩）。
   • 龙头行情常伴随板块整体催化。

5. 乖离率检查（关联理念1：严进策略）：

   • 龙头股可适当放宽乖离率至 7%，但超过 10% 仍需谨慎。

评分调整：

• 确认为龙头股：sentiment_score +10
• 板块正处于主动轮动期：额外 +5
• 在 buy_reason 中注明"龙头策略"判断结果。

Guardrails

• Never print real API keys, passwords, webhook URLs, or tokens.
• Ask before overwriting an existing ~/.stock_analysis/dragon_head/.env value.
• Ask before sending email. Do not enable EMAIL_ENABLED=true unless the user explicitly wants automatic delivery.
• Do not block the user on optional keys. Offer a skip path and explain the consequence.
• Required-capability keys are not optional. If missing, stop and ask for config instead of running degraded analysis.
• First run always requires an explicit initialization prompt to the user before analysis.
• Never run partial or incomplete functionality; this is mandatory.
• Explain failures by impact: blocking, fallback succeeded, or data-quality degradation.
• Do not call local Hermes or other local agent CLIs from this skill. The current Codex agent is responsible for reading generated prompt files and writing the final analysis.
• Reports and emails must contain the strategy analysis result, not raw prompt context.

Bundled Resources

• scripts/analyze.py: deterministic entry point.
• scripts/stock_agent/: self-contained helper functions for config, data, search, LLM, and report rendering.
• scripts/stock_agent/data.py: strategy-local data extraction code that reuses the shared ~/.stock_analysis/cache/ directory to avoid duplicate downloads across strategies.
• assets/env.example: template copied to ~/.stock_analysis/dragon_head/.env on first run.
• requirements.txt: Python dependency list.
• references/configuration.md: API-key setup details for this strategy folder.
• references/reporting.md: report and interface-status interpretation.