Stock Strategy Tracker

Problem: turning one-off analysis into durable action

Stock analyses often stop at a one-time report: entry conditions, stop-loss lines, and target prices are written down, but when prices move later it is hard to check whether any condition has triggered. This skill extracts the key decision fields from an analysis report and writes them to a local Markdown file, creating a reusable strategy ledger.

How it works: save and check are separate

• Save mode: after DCF, Buffett framework, technical analysis, or similar reports, extract fields such as stock_code, entry_conditions, stop_loss, target_price, and exit_signals; unspecified items are marked as “unspecified” instead of fabricated.
• Check mode: read the strategy file, use market data available to the agent, and mark each condition as ✅ triggered, ❌ not triggered, or ⚠️ close to triggering, then recommend next steps.
• Repeated saves for the same stock update the existing entry and preserve dated change notes.

Boundary: it does not place trades

The scripts only read and write the local strategy file; they do not execute trades or collect credentials. Market data depends on the agent’s external tools or search, so trigger quality depends on that data source. It is useful for strategy tracking and reminders, not for order execution.