CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

llm-council

Run any question, idea, or decision through a council of 5 AI advisors who independently analyze it, peer-review each other anonymously, and synthesize a final verdict. Based on Karpathy's LLM Council methodology. MANDATORY TRIGGERS: 'council this', 'run the council', 'war room this', 'pressure-test this', 'stress-test this', 'debate this'. STRONG TRIGGERS (use when combined with a real decision or tradeoff): 'should I X or Y', 'which option', 'what would you do', 'is this the right move', 'validate this', 'get multiple perspectives', 'I can't decide', 'I'm torn between'. Do NOT trigger on simple yes/no questions, factual lookups, or casual 'should I' without a meaningful tradeoff (e.g. 'should I use markdown' is not a council question). DO trigger when the user presents a genuine decision with stakes, multiple options, and context that suggests they want it pressure-tested from multiple angles.

Quality

87%

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

71%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 highly actionable, with complete prompt templates and a clear six-step process that faithfully implements the council methodology. Its main weaknesses are verbosity (motivational asides and trigger guidance duplicating the description) and a monolithic single-file structure that inlines template and example content better suited to reference files.

Suggestions

Trim the motivational prose in the intro and advisor sections, and remove or drastically shorten the 'when to run the council' section since that guidance already lives in the frontmatter description.

Move the three sub-agent prompt templates and the worked example into a references/ file (e.g. references/prompt-templates.md and references/example-session.md), keeping SKILL.md as a lean overview with clearly signaled one-level-deep links.

Add a brief validation step after the advisor and peer-review rounds — e.g. what to do if a response is hedged, off-angle, or a sub-agent fails — so the workflow has explicit checkpoints rather than assuming ideal outputs.

DimensionReasoningScore

Conciseness

The body is mostly functional but carries noticeable padding: motivational prose ("That answer might be great. It might be mid.", "This is the most underrated advisor", "That's the point."), and a "when to run the council" section that duplicates the frontmatter trigger guidance. It sits at anchor 3 ('some unnecessary explanation or could be tightened') rather than 4, where over-explanation would be only minor.

3 / 5

Actionability

The skill provides complete, copy-paste-ready sub-agent prompt templates for the advisor, reviewer, and chairman rounds, exact output filenames (council-report-[timestamp].html, council-transcript-[timestamp].md), a specified report structure, and a fully worked example of a session. This matches anchor 5: 'copy-paste ready... specific examples cover the common cases'.

5 / 5

Workflow Clarity

Six steps are clearly sequenced with parallelism, anonymization, and file outputs specified, and step 1 includes an error-recovery loop ("If the question is too vague... ask one clarifying question"). It falls short of anchor 5 because there are no explicit validation checkpoints for sub-agent outputs — no handling for weak, hedged, or failed advisor responses.

4 / 5

Progressive Disclosure

There are no bundle files (no references/, scripts/, or assets/), so everything lives in a single ~190-line SKILL.md. The sections are well-organized, but ~80 lines of prompt templates plus a worked example are inlined content that would serve better as one-level-deep reference files — matching anchor 3 ('content that should be separate is inline') rather than 4.

3 / 5

Total

15

/

20

Passed

Description

96%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.

An exemplary description: it states concrete capabilities in third person, gives exhaustive natural trigger phrases with both mandatory and strong tiers, and includes explicit negative guidance to prevent false firings. The only weakness is that a few of the strong triggers are generic enough to overlap with adjacent review/validation skills.

DimensionReasoningScore

Specificity

The description lists three concrete actions covering the full workflow — "independently analyze it, peer-review each other anonymously, and synthesize a final verdict" — which is comprehensive coverage for this skill. It fits anchor 5 rather than 4 because no meaningful capability is left out.

5 / 5

Completeness

It explicitly answers both what ("Run any question, idea, or decision through a council of 5 AI advisors...") and when ("MANDATORY TRIGGERS", "STRONG TRIGGERS", "Do NOT trigger on...") with concrete trigger phrases — an exact match to anchor 5.

5 / 5

Trigger Term Quality

Trigger coverage is comprehensive and natural: "council this", "run the council", "war room this", "pressure-test this", "stress-test this", "debate this", "should I X or Y", "I can't decide", "I'm torn between", plus explicit anti-triggers. Anchor 4 requires 'a few natural terms missing', and none are missing.

5 / 5

Distinctiveness Conflict Risk

Primary triggers like "council this" and "war room this" are highly distinctive, but "validate this", "debate this", and "get multiple perspectives" are generic phrases with minor overlap risk against general review/brainstorm skills. This matches anchor 4 ('mostly distinct; minor overlap risk') rather than 5, though the explicit anti-trigger guidance mitigates the risk.

4 / 5

Total

19

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

saski/arnesto

Path

.agents/skills/llm-council/SKILL.md

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.