CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ouroboros-run

Use when an Ouroboros Seed (a spec file with a goal and acceptance criteria, such as *.seed.yaml) already exists and the user wants it executed: 'run the seed', 'execute this spec', 'ooo run'. Executes it and verifies every acceptance criterion. Not for raw requests without a Seed (use interview or auto).

Quality

80%

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

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.

A densely operational, well-sequenced orchestration skill with excellent concrete tool-call specifications and thorough failure handling, but it crams an entire multi-protocol system into one 235-line file with over-dense prose. The main workflow is highly actionable; the weaknesses are readability (run-on validation sentences) and the absence of any progressive disclosure into reference files.

Suggestions

Split the secondary sub-protocols into one-level-deep reference files — e.g. references/synapse.md for intent refinement, references/conductor.md for attention handling, references/relay-events.md for the event vocabulary — leaving the core execution loop in SKILL.md.

Rewrite the step 5 sentinel-validation rules as a short fail-closed checklist (one failure mode per bullet) instead of a single ~130-word sentence; it currently obscures an otherwise clear sequence.

Give the Synapse `ouroboros_session_signal` and `ouroboros_record_conductor_decision` calls explicit argument blocks like the other tool calls, so all mutating paths are copy-paste ready rather than prose-described.

DimensionReasoningScore

Conciseness

The body contains no padding or explanations of concepts Claude already knows — every line is operational protocol it could not infer — but it is 235 lines of dense prose where significant tightening is possible: step 5's sentinel-validation rules form a single ~130-word sentence enumerating eight failure modes, and the catch-up/cursor rules are repeated across steps 4-6. It fits 'mostly efficient but could be tightened' rather than 'minor instances that could be trimmed'.

3 / 5

Actionability

The main path is fully concrete with copy-paste-ready argument blocks (e.g. `ouroboros_job_wait` with `timeout_seconds: 180`, `view: "summary"`, `wait_for: "attention_or_ac_change"`; `ouroboros_start_execute_seed` with conditional-argument rules). Minor gaps remain: the Synapse `ouroboros_session_signal` call (step 3) and `ouroboros_record_conductor_decision` logging are described in prose without argument blocks, so it is 'mostly executable with minor gaps' rather than fully copy-paste ready.

4 / 5

Workflow Clarity

A clear numbered sequence (steps 1-8) with genuinely explicit validation checkpoints and feedback loops: fail-closed contract validation, observer-failure fallback to catch-up, and 'If the evaluate job failed or timed out... show `Next: ooo evaluate <session_id>` as the manual retry'. It falls short of the top anchor because this complex process is presented as dense paragraphs (especially step 5) rather than checklists, which obscures the sequence at points; not a 3, since checkpoints are explicit and present throughout, not implicit.

4 / 5

Progressive Disclosure

The body is well-sectioned (Usage, Instructions with numbered subsections, Fallback, footer) but there are no bundle files at all — no references/, scripts/, or assets/ — and all ~235 lines are inline, including secondary sub-protocols (Synapse intent refinement, Active Conductor handling, the relay event vocabulary) that clearly belong in separate one-level-deep reference files loaded only when needed. This matches 'some structure... content that should be separate is inline'; not a 2 because the section structure is genuinely good and navigation within the file is easy.

3 / 5

Total

14

/

20

Passed

Description

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

A strong description: it defines the artifact, states what the skill does, gives exact quoted trigger phrases including the file extension, and closes with an explicit negative boundary that prevents mis-triggering against sibling interview/auto skills. The only minor gap is that 'executes and verifies' is a two-action summary of what the full skill does.

DimensionReasoningScore

Specificity

The description names the domain precisely ('an Ouroboros Seed (a spec file with a goal and acceptance criteria, such as *.seed.yaml)') and gives exactly two concrete actions — 'Executes it and verifies every acceptance criterion'. Two specific actions matches 'names domain and 1-2 concrete actions, but not comprehensive'; not a 4 since it does not list several actions, and not a 2 since the actions stated are concrete, not generic.

3 / 5

Completeness

Both halves are explicit: what — 'Executes it and verifies every acceptance criterion' (with the Seed artifact defined); when — 'Use when an Ouroboros Seed... already exists and the user wants it executed', reinforced by the quoted trigger phrases. This mirrors the top anchor's 'clearly and explicitly answers both what AND when with concrete trigger phrases'.

5 / 5

Trigger Term Quality

It quotes the literal natural phrases users would say — "'run the seed'", "'execute this spec'", "'ooo run'" — and includes the file extension '*.seed.yaml', matching the top anchor's standard of natural terms plus synonyms/extensions. Nothing a real user of this tool would say is obviously missing; not a 4, since coverage here is comprehensive for the niche rather than 'a few natural terms missing'.

5 / 5

Distinctiveness Conflict Risk

The triggers ('ooo run', *.seed.yaml) are highly distinctive, and the description explicitly disambiguates against sibling skills — 'Not for raw requests without a Seed (use interview or auto)' — which is active conflict avoidance. Clear niche with minimal conflict risk.

5 / 5

Total

18

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

Q00/ouroboros

Path

skills/run/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.