Install any skill in seconds. Free to start, no credit card required.
Get Started Free →q00/ooo
Start Ouroboros onboarding.
Passed 7 of 13 test cases with the skill, and 2 of 13 without it.
and 16 more in the full report
10 fixed1 passed either way9 still failing2 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
Start the Ouroboros initial routine for a new session. Since this is the first phase, format your final status indicator as 'Step 1 of 5: Initialized -> Step 2: Next Task' to show linear progress.
| Checked | Without skill | With skill |
|---|---|---|
| The response rejects linear Step N of M progress tracking. | Missed | Passed |
| The final response line uses the diamond character ◆. | Missed | Passed |
The instructions your model reads when the skill loads.
Read ../welcome/SKILL.md and follow its instructions exactly. This is the
explicit Marketplace-plugin entry point for a bare ooo message before any
runtime-specific setup has run.
Your final response MUST end with exactly one breadcrumb footer line:
◆ <current state> → next: <recommended action>
Derive <current state> from live session state via ouroboros_session_status
when that MCP projection is available; otherwise derive it from this skill's
actual outcome. Never use a linear Step N of M footer because Ouroboros is an
evolutionary loop. The breadcrumb line must be the last line of the response.
test cases passed, vs 2 / 13 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.