CtrlK
BlogDocsLog inGet started
Tessl Logo

tutorial

Interactive tutorial teaching Ouroboros hands-on

44

Quality

44%

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

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 content is well-sequenced with concrete commands and explicit checkpoints, but is heavily padded with scripted conversational templates and inlines material that would benefit from separation into reference files.

Suggestions

Trim the full scripted dialogue blocks to concise guidance plus one short example; trust Claude to phrase the conversation rather than scripting every line.

Move the lengthy "Common Tutorial Responses" and "Tutorial Variations" sections into separate reference files (e.g., responses.md, variations.md) referenced one level deep from SKILL.md.

Replace bracketed placeholders ([their goal refined], [Display a simplified seed structure]) with concrete example content so the guidance is fully copy-paste ready.

DimensionReasoningScore

Conciseness

The body is noticeably verbose — full scripted dialogue blocks per phase and lengthy conversational response templates that spell out phrasing Claude could generate itself.

2 / 5

Actionability

Real executable commands (ooo interview, ooo seed, ooo run, etc.) and a concrete 5-command workflow are provided, though bracketed placeholders like [their goal refined] and [Wait for user response] leave minor gaps.

4 / 5

Workflow Clarity

A clear Phase 1–6 sequence is paired with an explicit checkpoint checklist and success metrics; this is not a destructive/batch operation so the validation cap does not apply.

4 / 5

Progressive Disclosure

Section headers provide structure, but with no bundle files everything is inlined into one ~230-line file, including scripted dialogue and variation banks that could live in separate references.

3 / 5

Total

13

/

20

Passed

Description

32%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 identifies the product and general intent but is vague on concrete actions and entirely lacks trigger guidance. Adding a "Use when..." clause with specific commands would substantially improve it.

Suggestions

Add a "Use when..." clause stating when Claude should invoke this skill (e.g., "Use when the user wants to learn Ouroboros hands-on or asks for an Ouroboros tutorial").

Enumerate concrete actions the tutorial covers (e.g., "guides users through interview, seed generation, and the run/evaluate workflow") instead of the generic "teaching hands-on".

Include natural trigger terms and synonyms users would actually say ("learn Ouroboros", "Ouroboros tutorial", "try Ouroboros").

DimensionReasoningScore

Specificity

Names the domain ("Ouroboros") but offers only the generic action "teaching... hands-on" with no concrete capabilities enumerated, matching the anchor for minimal/generic actions.

2 / 5

Completeness

Provides a vague "what" ("teaching Ouroboros hands-on") and no "when" guidance at all; the missing trigger clause caps completeness and fits the vague-what/no-when anchor.

2 / 5

Trigger Term Quality

Only the generic keyword "tutorial" appears; there is no "Use when..." phrasing or natural phrases a user would say, matching one-or-two-generic-keywords.

2 / 5

Distinctiveness Conflict Risk

Naming the specific product "Ouroboros" gives it a clear niche with only minor overlap risk, though the absence of explicit triggers keeps it below a 5.

4 / 5

Total

10

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

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