CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

consciousness-council

Structures a multi-perspective council exercise for decisions, research trade-offs, and creative challenges. Simulates thinking archetypes, separates evidence from assumptions and values, and synthesizes a conditional recommendation. Use when the user requests a council, panel, devil's advocate analysis, "mind council", or deliberate comparison of perspectives on a difficult choice.

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

81%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 delivers an unusually well-structured, actionable instruction workflow with explicit templates, a worked example, and real validation checkpoints, and it correctly delegates deep configuration detail to one clearly signaled reference file. Its main cost is token weight: the same epistemic-hedging caveat is restated in nearly every section, which could be consolidated to respect the context budget.

Suggestions

Consolidate the repeated 'these are simulated viewpoints / not validated' caveats (currently restated in the intro, When to use, Before deliberation, configurations, worked example, and synthesis sections) into a single 'Limits' statement near the top, saving roughly a dozen lines of tokens.

Move the domain-mix lists out of the main body (they duplicate the 'Domain-Specific Councils' section of references/advanced-configurations.md) and keep only the general selection heuristic plus the reference link.

Consider moving the 'Evidence and limits' citation discussion into the references file, keeping one summary sentence in SKILL.md, so the main body stays a lean operational overview.

DimensionReasoningScore

Conciseness

The core material (archetype table, phase formats, worked example) is efficient and assumes competence, but the same anti-overclaim caveat is repeated many times — 'These are generated viewpoints from one system', 'not validated accuracy settings', 'This is a presentation option; no bias-reduction effect is established', 'a simulated Empiricist is not a source', 'This is a fictional, manually worked illustration' — where a single stated-once limitation would do. The content is mostly efficient but could be meaningfully tightened by consolidating the repeated disclaimers.

3 / 5

Actionability

As an instruction-only skill, guidance is fully concrete and executable: exact copy-paste output templates for deliberation ('Position: [One-sentence stance]... Decision Check: [Evidence or a changed constraint...]') and synthesis, a 12-row archetype table with thinking styles and blind spots, and a fully worked numeric example (pilot costing 20 of 100 units) with a sensitivity check. No vague 'process the perspectives' style direction appears.

5 / 5

Workflow Clarity

The three phases are clearly sequenced with explicit validation checkpoints: a numbered 'Before deliberation' step to 'Verify facts that could change the recommendation using original sources', a pre-synthesis checklist ('check that every consequential factual claim traces to the evidence brief'), and a stated feedback rule ('If verification is unavailable, keep the conclusion conditional and identify what must be checked'). The worked example's sensitivity check adds an error-recovery style loop.

5 / 5

Progressive Disclosure

The single reference is one level deep and clearly signaled with its contents described ('See [advanced configurations](references/advanced-configurations.md) for domain mixes, optional editorial scoring, and bounded multi-round or synthesis-only output'), and the referenced file exists and matches. Minor gaps: the body's domain selection heuristics duplicate the reference's 'Domain-Specific Councils' section, and the 'Evidence and limits' citation section could live in a reference file.

4 / 5

Total

17

/

20

Passed

Description

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

A strong description that clearly states concrete actions in third person and pairs them with an explicit, well-phrased 'Use when' trigger clause. Its only weaknesses are a slightly generic trigger word ('panel') and a few missing natural synonyms, both of which pose only minor mis-trigger risk.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — 'Simulates thinking archetypes, separates evidence from assumptions and values, and synthesizes a conditional recommendation' — plus the domains ('decisions, research trade-offs, and creative challenges'), comprehensively covering the skill's workflow without vague filler. It stays in third person ('Structures', 'Simulates').

5 / 5

Completeness

Both what and when are explicitly answered: 'what' via the concrete actions (simulates archetypes, separates evidence from assumptions and values, synthesizes a conditional recommendation) and 'when' via the explicit 'Use when the user requests a council, panel, devil's advocate analysis...' clause with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural trigger phrases are present — 'a council, panel, devil's advocate analysis, "mind council", or deliberate comparison of perspectives' — which users would genuinely say. A few plausible natural variants (e.g., 'debate both sides', 'second opinion', 'pros and cons') are missing, keeping it just below comprehensive.

4 / 5

Distinctiveness Conflict Risk

The niche is distinct with named triggers ('council', 'mind council', 'devil's advocate analysis'), so it is mostly distinguishable from other skills. However, 'panel' is a broadly used word that could cause minor overlap with unrelated panel/dashboard/discussion requests, matching 'minor overlap risk with closely related skills' rather than minimal risk.

4 / 5

Total

18

/

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

K-Dense-AI/scientific-agent-skills

Path

skills/consciousness-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.