ingest-performance

# /socialforge:ingest-performance — real numbers into the wins rung `/socialforge:ideate-month` compounds "what worked last month." Before this skill, that meant whatever someone remembered in the planning call — and memory favors the post that felt good, not the one that performed. This skill turns the platform's own export into the record ideation reads. ## Step 1 — Get the export Ask the user for the analytics export covering the month. Any CSV works if it has a column identifying the post (`post_id`, `post`, `id`) that matches the calendar's post ids, plus whichever metrics the platform provides (impressions/views, likes/reactions, comments, shares/reposts, saves, clicks, follows — header aliases are normalized automatically). If the export keys posts by URL or caption instead of the calendar id, help the user add a `post_id` column first — matching is by calendar id, deliberately: wins must map back to the topics and pillars that produced them. ## Step 2 — Ingest ```bash python ${CLAUDE_PLUGIN_ROOT}/scripts/ingest_performance.py --action ingest \ --brand {brand} --month {YYYY-MM} --csv {export.csv} --source "{platform} export" ``` - Rows matching calendar post ids are stored in `output/{brand}/{month}/performance.json` (repeat ingests append — one CSV per platform is normal). - **Unmatched rows are listed in the output, never silently dropped.** Show the user the unmatched list; a typo'd id is data lost from the wins rung. - Exit 3 = nothing matched. Stop...