skills/octopus-starter-pack/council-verdicts/SKILL.md
Starter: interpret a council run's verdict artifacts — quorum, dissent, cross-lab validity, and what to do next
npx skillsauth add nyldn/claude-octopus council-verdictsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
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.tools
Prototype one risky assumption within a fixed budget, then keep or discard the result
testing
Break a plan or spec into vertical slices that each declare what blocks them — use when work is agreed but not yet cut into fileable pieces
testing
Interrogate a plan, decision, or design one question at a time until it holds — use to stress-test your own thinking before committing to it
business
Move incoming issues and pull requests through triage states until each is actionable or closed — use when the queue has piled up or a report arrives unsorted