Stock Proactive Daily Briefing

Problem It Solves

“Which stocks matter today, at what price, and if only one trade is allowed, which one should be prioritized?” are easy to scatter across files and ad-hoc chat. A plain answer often stops at “report generated” or a list of tickers, without connecting candidates, entry levels, execution style, and the day’s action. This skill turns that into a daily actionable briefing for routine A-share review workflows.

How It Works

• Cache first: It checks a_share_daily_report_latest.md, a_share_agent_top5.csv, and a_share_agent_execution_plan.csv before regenerating the daily package when missing, stale, or explicitly requested.
• Candidate and execution plan: It builds on script capabilities such as generate_daily_report.py, trade_execution_plan.py, and manual_order_ticket.py to produce five candidates, detailed execution price levels, and manual order-ticket context.
• Daily action focus: Instead of saying only that files exist, it highlights one or two names to review first, distinguishes candidates better suited to breakout buying or pullback buying, compares risk-reward, and identifies the priority watch if only one trade is possible.
• Next step: If the user does not specify a follow-up, it proposes shrinking five names to two main watchlist items, cleaning up order-range lists, or creating a close-of-day/next-day summary.

Boundaries And Caveats

It is suited to A-share daily reporting, candidate selection, and execution-plan follow-through, not real-time market push. Cache usage should be stated clearly; failed market data should fall back without stopping the workflow. The output should focus on actionable value, and local file generation should not be framed as “already pushed”. For single-stock Q&A or deep fundamental research, the scope is narrower.