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

69

Quality

83%

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

SKILL.md
Quality
Evals
Security

Quality

Content

100%

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

The body is a tight, well-organized instruction set with concrete file paths, explicit validation checkpoints, and a clear re-run feedback loop, hitting the top anchor on every content dimension.

DimensionReasoningScore

Conciseness

The body is lean and action-focused with no generic concept explanations (it never explains what a council or quorum is); every line earns its place, matching the anchor for lean, efficient content that assumes competence.

3 / 3

Actionability

Although it is instruction-only with no code, the guidance is concrete and specific — exact paths ("~/.claude-octopus/results/", "summary.json", "hooks/subagent-stop-gate.sh"), an explicit verdict enum, and precise decision mappings — which the rubric's carve-out rewards for actionable instruction-only skills.

3 / 3

Workflow Clarity

Five steps are clearly sequenced with explicit validation checkpoints (confirm real provider/model, check quorum, treat malformed verdicts as ABSTAIN) and a feedback loop (re-run when seats disagree on facts), satisfying the anchor for a clear sequence with validation and error recovery.

3 / 3

Progressive Disclosure

At under 50 lines with no external references needed (no references/scripts/assets bundles exist) and well-organized sections (When to use, Steps, Guardrails), the skill meets the rubric's allowance for simple skills to score 3 on organization alone.

3 / 3

Total

12

/

12

Passed

Description

67%

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 distinctive niche, but it omits an explicit "when to use" trigger and relies on some jargon over natural user phrasing, capping trigger quality and completeness at 2.

Suggestions

Add an explicit trigger clause, e.g. "Use when a /octo:council run finishes and the user asks what the council decided or pastes a summary.json path."

Swap jargon like "cross-lab validity" for natural user phrasing such as "whether the panel's agreement is independent" to improve trigger-term quality.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — "interpret a council run's verdict artifacts — quorum, dissent, cross-lab validity, and what to do next" — matching the anchor for listing several specific concrete actions rather than a single vague domain.

3 / 3

Completeness

It clearly answers "what" (interpret artifacts, quorum, dissent, validity, next step) but lacks any explicit "Use when..." trigger clause; per the rubric guidelines a missing explicit trigger caps completeness at 2.

2 / 3

Trigger Term Quality

It contains relevant domain keywords ("council", "quorum", "dissent") but leans on jargon ("verdict artifacts", "cross-lab validity") and omits the natural user phrasing ("what did the council decide") that the body itself uses, so it has some but not full coverage of natural terms.

2 / 3

Distinctiveness Conflict Risk

"council run's verdict artifacts" carves out a clear niche tied to the octopus council system, making it unlikely to trigger for unrelated skills.

3 / 3

Total

10

/

12

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.