welcome

First-touch experience for new Ouroboros users

Quality

46%

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 ./skills/welcome/SKILL.md

Quality

Content

63%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 is highly actionable with a well-sequenced, validation-aware onboarding workflow, but it is materially hurt by a verbatim-duplicated readiness block and heavy inline parsing logic that should live in script files. Numbering (two 'Step 4' headers) and length are the main clarity/efficiency drags.

Suggestions

Extract the duplicated Codex readiness Python block into a shared script under scripts/ and source it from both the Pre-Check and Setup Gate sections to remove the verbatim copy.

Fix the duplicate 'Step 4' header (Quick Reference vs First Action) so the step sequence is unambiguous.

Move the long TOML/YAML fallback parsers into a referenced utility file so SKILL.md reads as an overview pointing to detailed mechanics.

Dimension	Reasoning	Score
Conciseness	The ~1000-line body duplicates the entire ~150-line Codex readiness Python block verbatim in both the Pre-Check and Setup Gate sections, and inlines lengthy TOML/YAML fallback parsers, making it noticeably verbose with padded sections rather than just tightly written.	2 / 5
Actionability	Every branch supplies complete, copy-paste-ready bash heredocs and full AskUserQuestion JSON payloads with concrete commands (e.g. `gh api -X PUT /user/starred/Q00/ouroboros`, `ouroboros setup --runtime codex`), covering the common cases fully executable as written.	5 / 5
Workflow Clarity	The flow is explicitly sequenced (Pre-Check, Setup Gate, Steps 1-5, Completion) with validation checkpoints (readiness probe, atomic tempfile+os.replace config rewrite, partial-migration re-detection), but the duplicate 'Step 4' header and dense conditional branching leave minor clarity gaps short of the feedback-loop/checklist anchor 5.	4 / 5
Progressive Disclosure	Section headers and one-level-deep sibling-skill references (../setup/SKILL.md, ../config/SKILL.md, ../interview/SKILL.md) provide some structure, but the large duplicated inline Python blocks are content that clearly belongs in a scripts/ bundle, and no bundle files exist to factor them out.	3 / 5
	Total	14 / 20 Passed

Description

28%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 noun phrase that identifies the onboarding niche but provides no concrete actions, no natural trigger terms, and no explicit use-when guidance. It is distinguishable yet vague enough to risk overlap with the setup skill.

Suggestions

Add concrete actions, e.g. 'Detects existing Ouroboros setup, shows a welcome banner, and guides new users through first commands'.

Append an explicit trigger clause such as 'Use when a user is new to Ouroboros or asks to start onboarding/welcome'.

Include natural synonyms users would say ('onboarding', 'getting started', 'first run') to improve trigger-term quality.

Dimension	Reasoning	Score
Specificity	"First-touch experience for new Ouroboros users" names the onboarding domain but lists no concrete actions (no 'guides', 'detects setup', 'shows banner'), matching the 'names the domain but actions are minimal or generic' anchor rather than the entirely-vague anchor 1.	2 / 5
Completeness	It gives only a vague 'what' (an onboarding 'experience') and entirely omits any 'when'/'Use when' trigger guidance, matching the 'has a vague what and no when' anchor; the missing trigger clause caps it well below 3.	2 / 5
Trigger Term Quality	The phrase offers only the generic keyword "new Ouroboros users"; "first-touch experience" is jargon a user would not naturally say, and there are no natural trigger phrases like 'onboarding' or 'getting started', placing it just above the no-keywords anchor.	2 / 5
Distinctiveness Conflict Risk	Tying itself to "new Ouroboros users" gives it a recognizable niche, but the generic 'first-touch experience' framing overlaps with the sibling setup/config skills it itself references, fitting the 'somewhat specific but could still overlap' anchor.	3 / 5
	Total	9 / 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 (1011 lines); consider splitting into references/ and linking	Warning

	Total	15 / 16 Passed

Repository: Q00/ouroboros
Path: 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.