CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ouroboros-help

Full reference guide for Ouroboros commands and agents

Quality

70%

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

Quality

Content

96%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.

A lean, well-built reference: dense tables, literal commands, and a precisely specified behavioral footer with fallbacks. The only real weakness is organizational — the mandatory footer instruction is hidden behind an RFC-style header rather than being surfaced as a clear behavioral rule.

DimensionReasoningScore

Conciseness

Dense tables for Commands, Triggers, and Agents with no prose padding and no explanation of concepts Claude already knows; even the intro is three product-specific lines plus a compact diagram, and MCP/CLI terms are defined in a two-line footnote. Nothing to trim.

5 / 5

Actionability

Every command is literal and copy-pasteable (`ooo help`, `/ouroboros:ouroboros-help`), and the mandated footer has an exact format (`◆ <current state> → next: <recommended action>`) with a concrete derivation source (`ouroboros_session_status`) and a fallback. No gaps between instruction and execution.

5 / 5

Workflow Clarity

This is a single-task reference skill and its one prescribed action (the state footer) is unambiguous, with explicit branching: derive state from `ouroboros_session_status` when available, otherwise from the skill's actual outcome, and list 2-3 options when the next step is a real choice.

5 / 5

Progressive Disclosure

Well-sectioned with no dead references (no bundle files exist and none are cited), but the one mandatory behavior is buried under the jargon-y header 'RFC #1392 State Breadcrumb Footer', and 'Other files in src/ouroboros/agents/' points at plugin source rather than a bundled reference. Good structure with minor organization gaps.

4 / 5

Total

19

/

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 bare product-name-and-topic line: it names the domain but lists no concrete capabilities, provides no 'when to use' guidance, and includes no natural trigger phrases. It is distinct only by virtue of the product name and would rarely fire without the user already knowing the tool's name.

Suggestions

Add an explicit trigger clause, e.g., 'Use when the user asks what an Ouroboros command does, which command to use, or what agents are available.'

Replace the generic 'Full reference guide' with concrete capabilities, e.g., 'Lists every ooo command with its purpose and requirements (MCP/CLI/gh), natural-language trigger phrases, and the bundled agent roster.'

Include natural phrases users would actually say, such as 'ouroboros help', 'what commands does ouroboros have', or 'which agents does ouroboros use'.

DimensionReasoningScore

Specificity

'Full reference guide for Ouroboros commands and agents' names the domain but the only action is the generic 'reference guide' — no concrete capabilities are listed. It is not score 1 because a specific product domain is named, and not 3 because no concrete actions (e.g., 'lists commands with their requirements') appear.

2 / 5

Completeness

It has a vague 'what' ('full reference guide' — for what purpose is left unstated) and no 'when' guidance at all. This matches anchor 2 exactly ('vague what and no when'), and the missing 'Use when' clause caps it below 4 regardless.

2 / 5

Trigger Term Quality

The only distinctive term is the product name 'Ouroboros' plus generic words 'commands' and 'agents'; there are no natural phrases a user would actually say (e.g., 'what does ooo run do', 'ouroboros help') and no synonyms. Falls between the jargon-only anchor (1) and the generic-keywords anchor (2), noticeably below the midpoint.

2 / 5

Distinctiveness Conflict Risk

Anchoring to the specific product 'Ouroboros' avoids generic conflict, but the description does not distinguish this help skill from its many sibling /ouroboros:* skills (e.g., ooo tutorial, ooo welcome), which are also onboarding/reference-flavored. Somewhat specific but overlaps with closely related skills.

3 / 5

Total

9

/

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