CtrlK
BlogDocsLog inGet started
Tessl Logo

council-verdicts

Starter: interpret a council run's verdict artifacts — quorum, dissent, cross-lab validity, and what to do next

65

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/octopus-starter-pack/council-verdicts/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

86%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is concise, well-structured, and actionable with a clear sequenced workflow; it loses only minor points for relying on directory hints rather than exact commands and for implicit rather than explicit error-recovery loops.

DimensionReasoningScore

Conciseness

Lean and efficient; assumes Claude's competence with no padding or explanation of concepts Claude already knows, and every line (steps, guardrails) earns its place.

5 / 5

Actionability

Provides concrete, actionable guidance with specific paths (summary.json, hooks/subagent-stop-gate.sh, usage log) and clear decision rules; minor gap is the absence of literal commands or code for locating the newest run beyond a directory hint.

4 / 5

Workflow Clarity

Five clearly sequenced steps with explicit checks (roster validity, quorum, dissent, gate usage log) and a recommendation mapping; this is an interpretive/non-destructive skill so the destructive-operation cap does not apply, but explicit validation/error-recovery feedback loops are only implied rather than stated.

4 / 5

Progressive Disclosure

Well-organized sections (When to use, Steps, Guardrails) under 50 lines with no external bundle files needed; for a self-contained simple skill this is appropriately structured and easy to navigate.

5 / 5

Total

18

/

20

Passed

Description

70%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific and occupies a distinct niche with good natural trigger phrases, but it omits an explicit 'Use when...' clause in the description itself, capping completeness at 3.

Suggestions

Add an explicit 'Use when ...' clause to the description, e.g. 'Use when a /octo:council run has finished and you need to explain what the council decided.'

Expand the action list to mention tallying APPROVE/REJECT/ABSTAIN/REVISE counts directly in the description for more comprehensive coverage.

DimensionReasoningScore

Specificity

Names the domain (council verdict artifacts) and several concrete analytical actions — quorum, dissent, cross-lab validity, next-step recommendation — though it stops short of listing all five verdict tallies or specific artifact fields exhaustively.

4 / 5

Completeness

It states a clear 'what' (interpret a council run's verdict artifacts) but the 'when' is only weakly implied inside the body's 'When to use' section rather than explicit in the description; the description itself lacks a 'Use when...' clause, which caps completeness at 3.

3 / 5

Trigger Term Quality

Includes natural trigger phrases ('so what did the council decide?', summary.json path) and domain terms (council, verdict, quorum, dissent); a few common synonyms or variations a user might say are missing.

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche (council verdict interpretation) with distinct triggers tied to /octo:council runs; minimal overlap risk with other skills.

5 / 5

Total

16

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
nyldn/claude-octopus
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.