CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

unstuck

Use when the user is stuck or going in circles: the same fix failed twice or more, 'nothing works', 'I've tried everything', or a consequential choice with no clear winner that is hard to undo or splits the team (which database, which architecture). Brings hacker, researcher, simplifier, architect, and contrarian perspectives and converges on one recommendation. Not for a first error or normal progress.

Quality

95%

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

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

An exceptionally tight operational skill: every step carries executable specifics (exact commands, parameters, wire formats, and output templates) with explicit validation and error-recovery paths, and zero concept explanations. The only structural improvement would be offloading the detailed dispatch-block and footer protocol specs into reference files to slim the always-loaded body.

DimensionReasoningScore

Conciseness

The ~124-line body is dense with operational specifics delivered via tables and terse imperatives ("Validate every persona name against the pool; never coerce silently", "Never split the joined display text on `---`: user content can contain the separator") and contains no tutorial prose or explanations of concepts Claude already knows. Every token earns its place, matching the level-5 anchor; no identifiable padding to trim for a 4.

5 / 5

Actionability

Fully executable guidance throughout: exact CLI invocations (`ooo lateral debate <p1> <p2> ...`), exact MCP tool names and parameters (`persona=<one>`, `problem_context`, `current_approach`, `failed_attempts`), exact tool-discovery strings (`"+ouroboros lateral"`), verbatim user-question wording, the dispatch-block JSON shape, and a copy-paste-ready synthesis output template. Not 4 because concrete specifics cover the common cases with no gaps.

5 / 5

Workflow Clarity

Steps 1-4 are clearly sequenced with explicit validation checkpoints (arg-validation error rows, "never fabricate these fields", the deferred-schema guard before every `ouroboros_*` call) and error-recovery feedback loops (ask the user when context is missing; present the handler's markdown as-is when no payloads are recoverable; stop and report when the tool is genuinely absent). This matches the level-5 anchor; no destructive/batch cap applies.

5 / 5

Progressive Disclosure

Good structure with clear, well-labeled sections (Usage, Personas, Instructions with numbered steps, footer spec) and no buried or nested references, but all content is inlined in a >50-line SKILL.md with no bundle files. Detailed protocol material (the base64 inline-dispatch wire format, the RFC #1392 footer spec) could live in reference files. Not 5 because the score-5-without-references exception applies only to skills under 50 lines, and not 3 because organization is clean and nothing is misplaced.

4 / 5

Total

19

/

20

Passed

Description

95%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: it states concrete capabilities (five named perspectives converging on one recommendation), gives verbatim user phrasings as triggers for both the stall and decision use cases, and closes with an explicit negative boundary. The only gap is that the 'what' side is slightly less comprehensive than the trigger side.

DimensionReasoningScore

Specificity

Names the domain and several concrete actions ("Brings hacker, researcher, simplifier, architect, and contrarian perspectives and converges on one recommendation"), but coverage of what the skill does is narrower than the level-5 anchor (solo/debate modes and option presentation are not mentioned). Not 3 because more than 1-2 concrete actions are explicitly listed.

4 / 5

Completeness

Explicitly answers both what ("Brings hacker, researcher, simplifier, architect, and contrarian perspectives and converges on one recommendation") and when ("Use when the user is stuck or going in circles...") with concrete trigger phrases, and adds a negative boundary ("Not for a first error or normal progress"). This matches the level-5 anchor; the 'when' is maximally explicit.

5 / 5

Trigger Term Quality

Includes verbatim natural phrases users say when stuck ("stuck or going in circles", "'nothing works'", "'I've tried everything'", "the same fix failed twice or more") plus decision-side triggers ("which database, which architecture", "hard to undo or splits the team"), giving comprehensive coverage of natural terms. Not 4 because no common variation or synonym for these scenarios is missing.

5 / 5

Distinctiveness Conflict Risk

Clear niche (stagnation and hard-choice deliberation) with distinct triggers and an explicit exclusion ("Not for a first error or normal progress") that prevents overlap with routine debugging skills. Minimal conflict risk, matching the level-5 anchor.

5 / 5

Total

19

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

Q00/ouroboros

Path

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