agami-save-goldenlisted

Writes golden-dataset items for a profile through two doors. The import door turns a question bank — a CSV, or a table pasted into chat — into items after the parsed rows have been shown and agreed to: a row that already carries a statement is written confirmed, a bare question is written unconfirmed. The save door writes one question, the statement that answered it and the result the person accepted, as a confirmed item. The curation door applies the changes queued on the golden-dataset explorer page, which may weaken a claim and may never grant one. Every write goes through agami-core's writer, is re-read by the runner's own reader before it is kept, and is append-only: a write that would change an item that already exists stops and shows the before and the after. This skill writes only; it never runs or scores a dataset.
AgamiAI/agami-core · ★ 29 · Data & Documents · score 68

Install: claude install-skill AgamiAI/agami-core

# agami save-golden You are writing to the answer key. Goal: get a question — or a bank of them — into the profile's golden dataset in the state it has actually earned, and never in a better one. A dataset is what `/agami-eval` gates on, so an item that claims to be confirmed when nobody vouched for the answer turns the whole suite green on nothing — and equally, a question the sheet already carries a validated answer for should not sit unconfirmed for no reason beyond which door wrote it down. **This skill has three doors and they write different things.** Everything below is organized around them, because confusing them is the one failure that matters: | Door | Input | What it writes | Can it gate a run? | |---|---|---|---| | **Import** | A CSV of questions, or a table pasted into chat | `sql_confirmed: true` for a row that already carries a statement, `false` for a bare question | Yes, for the rows that carried an answer | | **Save** | One question, the statement that answered it, the result the person accepted | One item with `sql_confirmed: true` and its `confirmed_by` | Yes | An imported row with no statement **has none until somebody runs it and saves the answer through the save door.** That is the intended shape for a bare question, not a gap to close: it is an honest in-progress case that reports and cannot gate. A row that arrived already carrying a statement is different — it is somebody's own pre-validated answer, brought into the dataset already vouched for,