Help a coach answer a request

The hackathon CLI does every read and every act, with the coach's own sign-in, and prints JSON with --json. This skill reads, looks at the code and drafts; every write (a claim, a post, an unclaim, a resolve, a reopen) waits for the coach's explicit OK on that exact act, and a post shows its exact text first. If hackathon connect --json does not answer with eligibility.role advisor or organizer, run the hackathon-coach-brief skill first: it signs the coach in and picks the event's workspace.

A refusal is { "ok": false, "error": { "code", "message" } }: relay the message, never retry in a loop.

1. What waits

hackathon requests list --status open --limit 100 --json
hackathon requests list --status claimed --limit 100 --json