CtrlK
BlogDocsLog inGet started
Tessl Logo

skill-council

Run a configurable multi-LLM council with personas, budget caps, synthesis, veto gates, and optional implementation handoff.

60

Quality

70%

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/skill-council/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

88%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 body is highly actionable and well-sequenced with explicit validation checkpoints and feedback loops, and it avoids concept-padding. Minor room to tighten a few inlined blocks or move the large clarification example into a reference file.

DimensionReasoningScore

Conciseness

Mostly efficient with concrete command/code and no generic concept padding; the detailed sandbox-allowlist paragraph is earned operational guidance rather than fluff, though a few inlined blocks could be trimmed.

4 / 5

Actionability

Provides a copy-paste bash invocation, a complete AskUserQuestion code block, explicit flag translations, and concrete quorum/gate rules covering the common cases.

5 / 5

Workflow Clarity

Clear phased sequence (Phase 0A through Implementation Gates) with explicit validation checkpoints (quorum checks, budget re-checks before each phase) and feedback loops (retry on chair failure, stop on lost quorum).

5 / 5

Progressive Disclosure

Well-organized into clear sections with a single SKILL.md and no bundle files; minor gaps since the large clarification code block and sandbox details could be split into references, though no bundle directory exists.

4 / 5

Total

18

/

20

Passed

Description

51%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 clearly states what the skill does and lists distinctive features, but it omits any "Use when..." trigger guidance and relies on technical jargon over natural user phrases. Adding explicit trigger terms and a use-when clause would raise both completeness and trigger-term quality.

Suggestions

Add a "Use when..." clause with natural trigger phrases (e.g., "Use when the user wants multi-model debate, a council of advisors, or cross-LLM review of a decision").

Include user-facing synonyms alongside jargon (e.g., "council", "panel of models", "multi-model review", "advisor debate").

Lead with the concrete action (e.g., "Runs a multi-LLM council...") in third person and keep feature enumeration concise.

DimensionReasoningScore

Specificity

Enumerates several concrete features ("personas, budget caps, synthesis, veto gates, and optional implementation handoff") but stops short of comprehensive discrete action coverage.

4 / 5

Completeness

Has a clear "what" but no "Use when..." trigger clause; per guidelines a missing explicit trigger caps completeness at 3.

3 / 5

Trigger Term Quality

Only "council" is a user-facing term; the rest ("multi-LLM", "personas", "veto gates", "budget caps") is technical jargon with no natural synonyms or phrases users would actually say.

2 / 5

Distinctiveness Conflict Risk

The multi-LLM council niche is mostly distinct with minor overlap risk, though unspecified trigger phrases keep it from being fully unambiguous.

4 / 5

Total

13

/

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.