setup

Guided onboarding wizard for Ouroboros setup

Quality

52%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./skills/setup/SKILL.md

Quality

Content

56%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 skill is a highly actionable, well-sequenced wizard with concrete code throughout, but it is burdened by marketing/celebration padding and a monolithic structure with no bundle-file split, which drag conciseness and progressive disclosure down.

Suggestions

Trim motivational copy and celebration checkpoints to essentials, and de-duplicate the uv install one-liner that currently appears twice in Step 1, to recover token budget.

Move the CLAUDE.md preview block and the troubleshooting section into reference files (e.g. references/claude-md-block.md, references/troubleshooting.md) referenced one level deep, improving progressive disclosure.

Add an explicit confirmation before the batch `ouroboros_brownfield set_defaults` call when it would clear existing defaults, closing the workflow-clarity validation gap.

Dimension	Reasoning	Score
Conciseness	The ~700-line body carries several padded sections that don't help Claude execute — motivational hooks ("Let's unlock your full AI development potential"), ASCII-bordered celebration checkpoints, a "Conversion Metrics Track", and a duplicated uv install one-liner — fitting "noticeably verbose; several unnecessary explanations or padded sections" above the severely-padded level 1 but below an efficient level 3.	2 / 5
Actionability	The body is rich with copy-paste-ready bash (the ouroboros_python resolver), Python heredocs, AskUserQuestion JSON, and concrete MCP tool invocations, but a few directives are abstract ("Explain that advanced MCP workflows require a host-managed isolated launcher"), so it sits at "mostly executable guidance; concrete code or commands with minor gaps" rather than a clean 5.	4 / 5
Workflow Clarity	Steps 0 through 6 are explicitly sequenced with celebration/verification checkpoints, a deferred-schema guard before each brownfield MCP call, and a backup-before-edit safety net for CLAUDE.md, matching "clear sequence with most checkpoints present; minor validation gaps" — the gap being that the batch `set_defaults` call clears all existing defaults without an explicit confirmation prompt.	4 / 5
Progressive Disclosure	No bundle files exist (references/, scripts/, assets/ are empty) and the entire wizard — including the ~45-line CLAUDE.md preview block, troubleshooting, and conversion metrics — lives inline in one ~700-line SKILL.md, so it matches "some structure but could be better organized; content that should be separate is inline" despite clear section headers.	3 / 5
	Total	13 / 20 Passed

Description

48%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 third-person and names a clear niche, but it is a single short clause with no concrete actions and no explicit trigger guidance, which caps completeness at 3.

Suggestions

Add 1-2 concrete actions to lift specificity, e.g. "Guided onboarding wizard that detects the runtime environment, configures the Claude SDK profile, and integrates a CLAUDE.md quick-reference."

Append an explicit trigger clause such as "Use when the user runs `ooo setup`, asks to install/configure Ouroboros, or wants to onboard."

Include natural keyword variations (install, configure, get started) alongside "setup" to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	The phrase "Guided onboarding wizard for Ouroboros setup" names the domain (Ouroboros setup) and the form (a wizard) but lists no concrete actions, matching the "names the domain but actions are minimal or generic" anchor rather than the level-3 anchor which requires 1-2 concrete actions.	2 / 5
Completeness	It clearly states what the skill is ("Guided onboarding wizard for Ouroboros setup") but provides no explicit "Use when..." trigger guidance, so per the missing-trigger cap it cannot exceed 3 and matches the "clear what but when missing or only weakly implied" anchor.	3 / 5
Trigger Term Quality	"setup" and "onboarding" are relevant, natural keywords a user might say, but the description misses common variations or synonyms (e.g., "install", "configure", "get started"), fitting the "some relevant keywords but missing common variations" anchor.	3 / 5
Distinctiveness Conflict Risk	The "Ouroboros setup" niche is mostly distinct from sibling Ouroboros skills (interview, seed, evaluate), with only minor overlap risk against other setup/config skills, fitting the "mostly distinct; minor overlap risk" anchor.	4 / 5
	Total	12 / 20 Passed

Validation

87%

Warnings & errors only

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

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (710 lines); consider splitting into references/ and linking	Warning
relative_links	Relative link issues: 1 missing	Warning

	Total	14 / 16 Passed

Repository: Q00/ouroboros
Path: skills/setup/SKILL.md
Commit: 80333ae

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.