stock-volume-breakout-analysis

---

name: stock_volume_breakout_analysis description: Use this standalone stock strategy skill for 放量突破 (volume_breakout) 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/volume_breakout.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/volume_breakout/

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/volume_breakout.yaml
• Strategy id: volume_breakout
• Display name: 放量突破
• Category: trend
• Aliases: 放量突破, 突破
• Required source tools: get_daily_history, analyze_trend, get_realtime_quote
• 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/volume_breakout/.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/volume_breakout/prompts/, use the current Codex agent to generate the final analysis, and write that analysis to a Markdown file under ~/.stock_analysis/volume_breakout/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/volume_breakout/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/volume_breakout/final_reports/<report>.md --base-report ~/.stock_analysis/volume_breakout/reports/<base_report>.md

Strategy Rules

放量突破（Volume Breakout Strategy）

突破判定标准：

1. 阻力位识别：

   • 使用 analyze_trend → resistance_levels 获取阻力位。
   • 通常为 20 日高点或前期震荡平台顶部。

2. 量能确认（关联理念3：效率优先）：

   • 当日成交量 > 5 日均量的 2 倍。
   • 使用 get_realtime_quote → volume_ratio > 2.0 确认。
   • 使用 get_daily_history 计算均量进行交叉验证。

3. 价格确认（关联理念1：严进策略）：

   • 收盘价必须站上阻力位。
   • 收盘应在当日振幅上方 30%（强势收盘）。
   • 突破后乖离率检查：仍需 < 5%，避免追高。

4. 后续验证（如有数据）：

   • 次日开盘应在突破位之上，区分真突破与假突破。

5. 风险过滤（关联理念5：风险排查）：

   • 通过 search_stock_news 检查无重大利空。
   • PE 不应过高（避免泡沫型突破）。

评分调整：

• 放量突破确认：sentiment_score +12
• 突破伴随板块共振（板块也走强）：额外 +5
• 理想买点设在突破位附近，止损设在突破位下方 3%。
• 在 buy_reason 和 volume_analysis 中注明"放量突破"。

Guardrails

• Never print real API keys, passwords, webhook URLs, or tokens.
• Ask before overwriting an existing ~/.stock_analysis/volume_breakout/.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/volume_breakout/.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.