Install any skill in seconds. Free to start, no credit card required.
Get Started Free →nyldn/council-verdicts
Starter: interpret a council run's verdict artifacts — quorum, dissent, cross-lab validity, and what to do next
Passed 15 of 19 test cases with the skill, and 10 of 19 without it.
and 3 more in the full report
6 fixed11 passed either way5 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 5 test cases the skill fixed. Same model, same prompt, with and without the skill.
During our 4-seat council run, Seat 1 returned APPROVE, Seat 2 returned REJECT, Seat 3 returned APPROVE, but Seat 4's verdict file is completely missing from the results folder. How should Seat 4's vote be counted in the final tally?
| Checked | Without skill | With skill |
|---|---|---|
| Counts the missing verdict from Seat 4 as ABSTAIN. | Missed | Passed |
The instructions your model reads when the skill loads.
Read a completed council run's artifacts and explain what the verdicts actually mean before anyone acts on them.
A /octo:council run has finished and the user asks "so what did the council decide?" or pastes a summary.json path.
~/.claude-octopus/results/ (look for summary.json and per-seat verdict files). If none exist within the session window, say so; never invent a verdict.summary.json, confirm each seat's real provider and model (the agy seat records its resolved model, not default). Flag same-lineage panels: two seats backed by the same model family weaken the verdict's independence.hooks/subagent-stop-gate.sh) may have flagged it; check the gate's usage log for quality scores.test cases passed, vs 10 / 19 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.