stock-growth-quality-analysis

name	stock_growth_quality_analysis
description	Use this standalone stock strategy skill for 成长质量 (growth_quality) 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/growth_quality.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/growth_quality/

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/growth_quality.yaml
• Strategy id: growth_quality
• Display name: 成长质量
• Category: framework
• Aliases: 成长, 成长股, 成长质量
• Required source tools: get_stock_info, get_realtime_quote, search_stock_news, analyze_trend
• Summary: 结合收入利润增长、ROE、现金流和行业空间，识别高质量成长股与成长失速风险。

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/growth_quality/.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/growth_quality/prompts/, use the current Codex agent to generate the final analysis, and write that analysis to a Markdown file under ~/.stock_analysis/growth_quality/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/growth_quality/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/growth_quality/final_reports/<report>.md --base-report ~/.stock_analysis/growth_quality/reports/<base_report>.md

Strategy Rules

成长质量策略（Growth Quality Strategy）

适用场景：

• 关注公司中长期成长能力，而不是只看短线技术形态。
• 适合高景气行业、业绩持续改善或商业模式扩张阶段的公司。

分析框架：

1. 成长性

   • 优先查看财报字段中的营业收入、归母净利润、经营现金流和 ROE。
   • 判断收入增长和利润增长是否同向，是否存在“增收不增利”。
   • 若只有概念热度但财报尚未验证，应降低成长确定性。

2. 质量

   • ROE 越高且稳定，质量越好。
   • 经营现金流与净利润方向一致，说明盈利质量更可靠。
   • 现金流显著弱于利润时，要提示回款、存货或应收风险。

3. 估值承受力

   • 使用 PE/PB、市值等估值字段判断市场是否已经提前透支成长。
   • 高成长可承受更高估值，但必须说明增长能否覆盖估值。
   • 估值高且成长放缓时，应明显下调评分。

4. 趋势确认

   • 使用 analyze_trend 判断长期成长逻辑是否被市场资金确认。
   • 基本面向好但技术面未确认时，优先给观察条件而不是直接追买。

输出要求：

• 明确公司处于：高质量成长 / 成长验证中 / 成长放缓 / 成长证伪。
• 说明成长来自收入扩张、利润率改善、行业景气，还是一次性因素。
• 给出适合成长股的买点：业绩验证后突破、回踩长期均线或估值回落。

评分调整建议：

• 收入、利润、现金流和 ROE 同向改善：sentiment_score +15
• 行业景气与公司新闻互相验证：额外 +6
• 高估值但成长未验证：sentiment_score -8
• 增收不增利或现金流恶化：sentiment_score -12

Guardrails

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