public-equity-research: Skill for Claude Code

Staleness Checker — SKILL.md

Role: Step 0 — Evaluate whether existing snapshot data is fresh enough to reuse, or whether new data collection is required. Triggered by: CLAUDE.md at the start of Workflow 1 (Single Stock Analysis) and Workflow 3 (Watchlist Scan) Reads: output/data/{ticker}/latest.json, staleness rules from this file Writes: Nothing (read-only evaluation; result is reported inline to orchestrator) References: references/staleness-rules.md

---

Instructions

Step 0.1 — Check for Existing Snapshot

Check if output/data/{ticker}/latest.json exists. New files are pointer-only documents; legacy full-snapshot files may still appear and must remain readable.

IF file does not exist:
    → Routing decision: FRESH_COLLECTION (no cached data)
    → Proceed to Step 1 (query-interpreter)

If file exists, read it and extract:

• analysis_date (YYYY-MM-DD)
• expires_at and refs.analysis_result when kind is stock-analysis.latest-snapshot-pointer
• data_mode (enhanced / standard)
• output_mode (A / B / C / D)
• rr_score
• verdict

If latest.json is a pointer, verify that refs.analysis_result exists before routing to REUSE or DELTA_FAST. If the pointer is missing, expired, or points to a missing file, route to FRESH_COLLECTION.

Step 0.2 — Calculate Staleness

Calculate days_since_analysis = today - analysis_date. For pointer files, treat expires_at as the primary 24-hour reuse boundary; analysis_date remains the coarser fallback for older files and user-facing explanations.

Mode E hard override (OD-F1): When the orchestrator has set pipeline_state.mode_override == "E" (because earnings-window-detector returned window in {preview, review} at CLAUDE.md Step 0.5, or the user passed --mode E / --earnings-mode preview|review), skip the staleness table entirely and route to FRESH_COLLECTION. Mode E should never reuse a stale snapshot — implied moves, options chains, and consensus EPS shift fast in the D-7~D+3 window.