What problem does it solve? Adding a new securities or crypto broker statement importer often produces wrong cash legs, double-counted fees, or incorrect cost basis because developers invent schemas instead of calibrating against real statements. This Skill provides a proven playbook for parsing broker PDFs/CSVs into investment_events with correct SWAP, commission, and CHECKIN semantics. ## Core Features & Use Cases - Fee and cash-leg contract design: Fill a native-field census and fee table from at least five real sample trades before writing any map code, ensuring each fen of fee appears in either the cash leg or the commission field, never both. - CHECKIN-based calibration: Emit cash and per-ticker holdings CHECKIN events from statement headers so end shares, cost price, and cash match the broker statement exactly. - Idempotent import wiring: Wire parsers into the CLI with stable source_identity keys, password-file handling for encrypted PDFs, and dual-backend (SQLite/PostgreSQL) parity. - Use Case: When onboarding a new broker like Futu or IBKR, run the census, fee contract, and calibration loop against a real statement until cash, shares, and cost price reconcile with the statement header. ## Quick Start Ask the AI to onboard a new broker statement importer for your brokerage PDF using the investment statement importer playbook, starting with a native field census and fee contract table.
