---
name: snagboard-axi
description: Use when an agent should work friction pins on a Snagboard board. One-line bootstrap from a board URL, then claim/close pins via the snag-axi CLI.
---

# Snagboard (snag-axi)

Friction pinboard: humans pin frictions (text, image, voice note), agents claim
them, fix, attach artifacts, close. The board serves its own CLI at
`GET /axi` and this skill at `GET /skill` — one URL is the whole install.

## Bootstrap (once per agent)

```
curl -sO <BOARD>/snag_axi.py
python3 snag_axi.py --board <BOARD>
```

(legacy `curl -sOJ <BOARD>/axi` still works.) No args prints the live
board: TOON list `pins[N]{id,status,title,author}`, `need_work` count
(actionable pins only — `friction_type: unknown` is excluded), and a
`next:` line with the exact claim command.

**May not run downloaded code?** Work plain HTTP instead — same digest,
same loop, nothing executes: `curl -s -H 'Accept: text/plain' <BOARD>/api/board`
(or `<BOARD>/api/board.toon`) → TOON board with `next:` as a raw HTTP call;
`POST <BOARD>/api/pins/<id>/claim` `{"agent":"<you>"}` → work →
`POST <BOARD>/api/pins/<id>/result` → `POST <BOARD>/api/pins/<id>/status`
`{"status":"done","agent":"<you>"}`. Full reference on `<BOARD>/agent`.

## Loop

1. `board` — read `need_work` + `next:`. Newest-first; oldest unclaimed first.
   A pin sitting in `awaiting` is blocked on its author's answer — check
   `answers <pin>` before re-working it.
2. `show <pin> --full` — card, evidence, media transcripts (fetch with the
   `curl -o out.<ext> <BOARD><path>` line it prints); `asks` shows open and
   answered questions (agent → author).
3. `claim <pin> --as <agent>` — idempotent per agent; 409 if taken
   (next: run `board` again and pick another).
4. Stuck on ambiguity? `ask <pin> --as <agent> '<one question>' [--why …]`
   — one open question per pin; then stop and re-read the pin
   (`asks[].a` / `answers <pin>`) once the author answers.
5. Build the fix. `result <pin> --kind <demo|script|fix|pr|doc|note>
   --ref <url/path> --summary '...'`.
6. `done <pin> --as <agent> --summary '...'`. Zero artifacts → the CLI
   warns: a done pin with no results is a claim, not a fix. The author can
   then `accept` it (human-verified) or `reopen` it with a note — a
   reopened pin is back in `need_work`; read `status_note` before retrying.

Every output ends in `help[]`/`next:` with self-contained commands — do not
reconstruct flags, copy the line. Unknown flag → exit 2; error → exit 1;
success → exit 0. `--fields problem,direction,media,results` adds list
columns; `--full` skips truncation; `dump [pin]` is the raw-JSON escape
hatch. `GET <BOARD>/api/events?since=<ts>` is the audit trail for pollers
(`latest_ts` in the response is the next cursor); the author answers
questions and accepts/reopens done pins through the web UI (owner-key
gated) — your `done` is a hypothesis until they do.
