CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ooo

Start Ouroboros onboarding. Use when the user sends bare `ooo`, asks to start Ouroboros, or is using Ouroboros for the first time.

Quality

84%

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

78%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 a tight, well-structured delegation wrapper with a clear footer constraint and one cleanly signaled reference. It is efficient and appropriately scoped, with only minor abstraction in the state-derivation guidance.

Suggestions

Add one concrete example breadcrumb line (e.g. '◆ onboarding: welcome read → next: complete profile setup') to make the state-derivation guidance immediately actionable.

Trim the justifying clauses ('because Ouroboros is an evolutionary loop', 'This is the explicit Marketplace-plugin entry point...') to tighten the body further.

Clarify what 'follow its instructions exactly' should produce if welcome/SKILL.md is missing or unreadable, so the delegation has a defined fallback.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence, with only minor rationale that could be trimmed (e.g. 'because Ouroboros is an evolutionary loop', 'This is the explicit Marketplace-plugin entry point...').

4 / 5

Actionability

Provides a concrete, executable directive ('Read `../welcome/SKILL.md` and follow its instructions exactly') and a concrete footer template, but the substantive onboarding work is delegated rather than specified inline.

4 / 5

Workflow Clarity

The single delegation action is unambiguous and the breadcrumb footer rule is clearly stated, but the state-derivation branch (MCP available vs. fallback) is somewhat abstract with no concrete example breadcrumb beyond the format template.

4 / 5

Progressive Disclosure

Under 50 lines with well-organized sections and a single clearly-signaled one-level-deep reference (`../welcome/SKILL.md`); no bundle files exist to require deeper structure.

5 / 5

Total

17

/

20

Passed

Description

82%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 concise, third-person, and cleanly answers both what and when with concrete, natural triggers and low conflict risk. Its only weakness is that it names a single action rather than a fuller capability set.

DimensionReasoningScore

Specificity

Names the domain (Ouroboros onboarding) and one concrete action ('Start Ouroboros onboarding'), but coverage is not comprehensive — it is a single start action rather than a list of capabilities.

3 / 5

Completeness

Explicitly answers both 'what' (Start Ouroboros onboarding) and 'when' with concrete trigger phrases ('Use when the user sends bare `ooo`...').

5 / 5

Trigger Term Quality

Natural trigger phrases are present ('bare `ooo`', 'asks to start Ouroboros', 'using Ouroboros for the first time') covering what a user would actually say, with only minor synonym gaps.

4 / 5

Distinctiveness Conflict Risk

The `ooo` token and Ouroboros name form a clear, distinct niche with minimal overlap risk against other skills.

5 / 5

Total

17

/

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/ooo/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.