CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

tutorial

Interactive tutorial teaching Ouroboros hands-on

Quality

76%

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/tutorial/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

92%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 strong example of an instructional skill: a concrete, well-sequenced five-phase flow with executable commands, exact question scripts, fallbacks, and explicit done-criteria. Its only weakness is mild redundancy between the Principles section and the Flow phases.

DimensionReasoningScore

Conciseness

The body is efficient — concrete commands, scripted questions, and no explanations of concepts Claude already knows — but the Principles section mildly duplicates the Flow ('Show something useful in the first 30 seconds' restates the Hook phase; 'Reveal features gradually' restates the phased structure), so minor trimming is possible.

4 / 5

Actionability

Fully executable guidance: copy-paste-ready commands with inline comments ('ooo interview "your idea" # expose assumptions'), exact Socratic questions to ask, a concrete Mini-Seed output template, a fallback example (task-management CLI), scripted objection handling, and an exact footer format. Specific examples cover the common cases.

5 / 5

Workflow Clarity

The five phases are clearly sequenced with timing ('about 5 minutes'), each phase ends with a specific next action per the stated principle, and there is an explicit completion checklist ('done when the user has experienced the interview, understands what a Seed is, and has chosen a next step') plus recovery paths for the no-idea and objection cases.

5 / 5

Progressive Disclosure

A self-contained, single-purpose tutorial with no bundle files (no references/, scripts/, or assets/ exist, and none are needed) and no nested references; sections (Usage, Principles, Flow, footer) are well organized with nothing that belongs in a separate file.

5 / 5

Total

19

/

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 concise and names its domain, but it is too thin to serve its discovery purpose: it lists no concrete actions, no trigger phrases a user would naturally say, and no 'use when' guidance. It reads as a label rather than a capability statement.

Suggestions

List concrete actions instead of the generic 'teaching hands-on', e.g. 'Runs a five-minute interactive tutorial for Ouroboros: Socratic interview, Seed drafting, and a first ooo run/evaluate cycle.'

Add natural trigger phrases users would actually say, e.g. 'Use when the user wants to learn Ouroboros, asks for a tutorial or getting-started guide, or asks what Ouroboros is.'

State the audience or outcome in the description (e.g. 'for users new to Ouroboros') to sharpen the 'when' component and further distinguish it from generic tutorial skills.

DimensionReasoningScore

Specificity

The description names the domain ('Ouroboros') and a single generic action ('teaching ... hands-on' via 'Interactive tutorial'), matching the anchor-2 pattern of 'Processes PDF files' — the domain is named but actions are minimal or generic, and no concrete capabilities (interview, Seed building, first run) are listed.

2 / 5

Completeness

The 'what' is reasonably clear (an interactive, hands-on tutorial for Ouroboros), but the 'when' is entirely absent — no 'Use when...' clause or equivalent trigger guidance — which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

It contains some relevant keywords users might say ('tutorial', 'hands-on', 'Ouroboros', 'interactive'), but misses common natural variations and synonyms such as 'learn Ouroboros', 'get started', 'onboarding', or 'teach me', fitting the anchor 'Some relevant keywords but missing common variations or synonyms'.

3 / 5

Distinctiveness Conflict Risk

The explicit product name 'Ouroboros' gives it a clear niche and mostly distinct triggers, but the generic 'interactive tutorial ... hands-on' phrasing carries minor overlap risk with other tutorial/onboarding skills in the same family, so it fits anchor 4 rather than 5.

4 / 5

Total

12

/

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