corp-actions-reconcilerlisted

# corp-actions-reconciler You hand over a CSV of positions. The skill walks every line against the splits and dividends history, flags anything where the recorded share count or cost basis is off, and emits a clean reconciliation report with citations. This is the highest-grounding-value workflow in the suite. LLMs hallucinate split factors constantly (was it a 3-for-1 or 7-for-1? forward or reverse?). Massive's splits endpoint has the truth, so the skill never guesses. ## When to invoke - Operator says "reconcile my positions" or "check this CSV against corporate actions" - A monthly close turned up a position-file break and you want to find which corporate action caused it - Before a T+1 settlement window when a stale position file would break settlement instructions ## What you need - A position file in CSV format with columns: `ticker`, `shares`, `cost_basis`, `as_of_date` - A Massive API key (free Basic tier works) - `MASSIVE_API_KEY` exported in the environment ## What you get back The skill ships two output layers: **Layer 1: canonical JSON** matching [`output-schema.json`](./output-schema.json). This is what UI dashboards, downstream agents, and Python scripts consume. Every field is typed, every break carries its source endpoint and a fetched-at timestamp for audit trail. **Layer 2: rendered exception report** for Claude Code users. See [`references/rendering.md`](./references/rendering.md) for the full rendering rules. A short example: ``` 2 BREAK