CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

setup

Guided onboarding wizard for Ouroboros setup

Quality

78%

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/setup/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 content is a strong, highly actionable setup wizard: concrete executable commands, exact tool-call payloads, explicit sequencing, and thorough validation and error-recovery paths. Its only real weaknesses are mild redundancy (repeated mcp.json warnings) and a long inline footprint where a couple of verbatim blocks could be split into bundle files.

DimensionReasoningScore

Conciseness

The body is dense with product-specific, non-obvious instructions (Python resolver, MCP profile boundaries, deferred-schema guard) and assumes Claude's competence rather than explaining known concepts. Minor trimming is possible — the warning to never touch `~/.claude/mcp.json` is repeated in the intro, Step 1.5, Step 2, Step 4, and Uninstall — so it is 'efficient with minor instances that could be trimmed' rather than fully lean.

4 / 5

Actionability

Guidance is fully executable and copy-paste ready: complete bash function definitions (`ouroboros_python`, `ouroboros_cli`), exact commands (`ouroboros_cli setup --runtime claude --non-interactive`), a verbatim CLAUDE.md template, exact MCP tool arguments with JSON (e.g. `{ "action": "set_defaults", "indices": "..." }`), and literal prompts to show the user. It is above level 4 because the common cases are covered with specific, runnable content rather than high-level hints.

5 / 5

Workflow Clarity

The wizard is explicitly sequenced (Steps 0.5 through 6) with validation checkpoints: the Step 1.5 welcome-gate conditions, Step 4 verification, error-recovery paths ("If it fails, show the error and continue the wizard"), retry-on-invalid-input for repo selection ("anything else gets the prompt again (never guess)"), and skip conditions when tools are absent. Destructive operations (uninstall, CLAUDE.md edits) are guarded by confirmation and backup, so the workflow-clarity cap for missing validation does not apply.

5 / 5

Progressive Disclosure

The body is well-organized into clearly headed steps with a single, clearly signaled one-level-deep reference (`../config/SKILL.md`), and no bundle files exist to mis-navigate. It falls short of 5 because at ~350 lines, large verbatim blocks (the ~25-line resolver and ~45-line CLAUDE.md template) are inlined and could live in separate reference/asset files to keep the overview leaner.

4 / 5

Total

18

/

20

Passed

Description

57%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 is short, accurate, and unambiguous about its niche thanks to the product name, but it omits any 'when to use' trigger guidance and enumerates none of the wizard's concrete capabilities. It reads more like a title than an invocation description, which limits its usefulness for triggering and scope signaling.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user wants to set up, install, or configure Ouroboros in Claude Code".

Enumerate the wizard's concrete capabilities (environment detection, runtime configuration, CLAUDE.md integration, brownfield repository scan, uninstall) so the 'what' is comprehensive rather than a single action.

Include natural user phrasings and synonyms such as "install", "configure", or "initialize Ouroboros" to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

The description names the domain ("Ouroboros setup") and one action ("Guided onboarding wizard"), which matches the anchor for naming a domain plus 1-2 concrete actions without comprehensive coverage. It does not list the several specific actions the wizard actually performs (environment detection, runtime config, CLAUDE.md integration, brownfield scan), so it is not at the 'lists several specific actions' level.

3 / 5

Completeness

The 'what' is clear (a guided onboarding wizard for Ouroboros setup), but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. It is above the vague-'what' level because the stated purpose is unambiguous.

3 / 5

Trigger Term Quality

"setup" and "onboarding" are relevant, natural keywords anchored by the product name "Ouroboros", but the description misses common variations a user might say (e.g., "install", "configure", "initialize", "get started"). This sits at 'some relevant keywords but missing common variations or synonyms', not at 'good keyword coverage'.

3 / 5

Distinctiveness Conflict Risk

The product name "Ouroboros" gives this a clear niche; no other plausible skill would claim Ouroboros setup, so conflict risk is minimal. It is not at 4 because the unique product identifier eliminates even minor overlap with closely related setup/onboarding skills.

5 / 5

Total

14

/

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

Q00/ouroboros

Path

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