welcome

First-touch experience for new Ouroboros users

Quality

38%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.claude-plugin/skills/welcome/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 thorough, executable onboarding flow with clear sequencing and validation gates, but it is too long and repeats large code blocks instead of factoring them out. It would benefit from extracting shared helpers into reference files and tightening the duplicated YAML/prefs logic.

Suggestions

De-duplicate the two near-identical yaml_mapping Python blocks and the two prefs-merge snippets into a single shared helper sourced once at the top.

Move the command quick-reference table and the YAML parser into reference files under references/ and link to them, reducing the SKILL.md body and improving progressive disclosure.

Trim the prose around runtime internals (e.g. the MCP 1.x/MCP 2 launcher explanation) to the minimum Claude needs, since much of it restates environment behavior Claude can observe.

Dimension	Reasoning	Score
Conciseness	At ~600 lines the body is noticeably verbose and duplicates large blocks: the yaml_mapping parser appears twice nearly verbatim and the prefs-merge Python snippet is repeated, padding the skill beyond what Claude needs.	2 / 5
Actionability	Guidance is mostly executable — concrete bash, heredoc Python, real AskUserQuestion JSON, and specific `gh`/`ooo` commands — with only minor gaps where it delegates to sibling skills like ../setup/SKILL.md.	4 / 5
Workflow Clarity	The flow is a clearly sequenced Pre-Check → Setup Gate → Steps 1-5 → Completion with explicit readiness validation gates and a gh-availability check, though a few checkpoints (e.g. confirming prefs writes succeeded) are implicit.	4 / 5
Progressive Disclosure	Headers give reasonable structure but there are no reference files — large inline content like the full YAML parser and command quick-reference table that could live in separate files is inlined, and the only links point to sibling skills rather than within-skill references.	3 / 5
	Total	13 / 20 Passed

Description

21%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 a terse, product-scoped label rather than a capability statement: it lacks concrete actions, natural trigger terms, and any explicit 'when to use' guidance. It distinguishes itself mainly via the Ouroboros name, not via what it does.

Suggestions

Rewrite in third-person action form listing concrete behaviors, e.g. 'Guides new users through interactive onboarding: detects persona, checks runtime readiness, and routes to first action.'

Add an explicit trigger clause such as 'Use when a new user first invokes Ouroboros or runs /ouroboros:welcome for the first time.'

Include natural trigger terms users would actually say ('onboarding', 'welcome', 'getting started', 'first run') instead of internal phrasing like 'first-touch experience'.

Dimension	Reasoning	Score
Specificity	The phrase 'First-touch experience' names the domain but uses no concrete action verbs, only a generic noun phrase, matching the 'names the domain but actions are minimal or generic' anchor rather than the entirely-vague 1.	2 / 5
Completeness	It offers only a vague 'what' and no 'when' / 'Use when...' trigger clause; the missing explicit trigger guidance keeps it at the vague-what-no-when level, not the clear-what anchor of 3.	2 / 5
Trigger Term Quality	No natural user keywords appear; 'First-touch experience' and 'new Ouroboros users' are internal jargon and a generic audience label, with no phrase like 'onboarding' or 'welcome' a user would actually say.	1 / 5
Distinctiveness Conflict Risk	Scoping to 'new Ouroboros users' makes it product-specific and mostly distinct, but the functional description ('first-touch experience') is generic enough to overlap with other onboarding-style skills.	3 / 5
	Total	8 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (601 lines); consider splitting into references/ and linking	Warning

	Total	15 / 16 Passed

Repository: Q00/ouroboros
Path: .claude-plugin/skills/welcome/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.