New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Tutorial

by Q00 in Q00/ouroboros

Interactive tutorial teaching Ouroboros hands-on. An agent skill from Q00/ouroboros.

MITAuto-check passedAgent Workflows

Install Tutorial

skills CLI
$ npx skills add Q00/ouroboros --skill tutorial -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install Q00/ouroboros tutorial --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/Q00/ouroboros.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/tutorial .claude/skills/tutorial && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
tutorial
GitHub stars
6.2k
Token cost
~1.6k tokens
SKILL.md length
383 words
Files
1
Skills in repo
23
Repo updated
First seen
Licence
MIT

At a glance

Interactive tutorial teaching Ouroboros hands-on. An agent skill from Q00/ouroboros.

  • Works in 6 steps: The Hook (30 seconds) → The Interview Experience (2 minutes) → The Quick Win (1 minute) → …
  • Agent Workflows work in your project
  • SKILL.md covers Usage, Tutorial Flow, Phase 1: The Hook (30 seconds) and Phase 2: The Interview…, plus 10 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Tutorial is an agent skill from Q00/ouroboros. Interactive tutorial teaching Ouroboros hands-on

Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Agent Workflows. The repository describes itself as: Agent OS: the agent gets smarter on its own. We just hold the line: Interview-gated, staged evaluation, budgeted evolution loop. MCP server, 14 runtimes: Claude Code, Codex CLI… The licence is MIT.

When your agent uses it

  • Agent Workflows work in your project

Example prompts

  • “/tutorial”

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. The Hook (30 seconds)
  2. The Interview Experience (2 minutes)
  3. The Quick Win (1 minute)
  4. Feature Discovery (1 minute)
  5. The Real Workflow (30 seconds)
  6. Call to Action

What it can do on your machine

Read from SKILL.md and the folder at commit 0df5b98. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Tutorial loads about 1.6k tokens when it runs. Until then it costs about 14 tokens; SKILL.md has 383 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~14
When it runs · the whole SKILL.md, loaded when a task matches
~1.6k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from Q00/ouroboros at commit 0df5b98, republished under its MIT licence (© Q00). 383 words, ~1,584 tokens.

Download SKILL.mdSave it as .claude/skills/tutorial/SKILL.md (or your agent's skills folder).
name
tutorial
description
Interactive tutorial teaching Ouroboros hands-on

/ouroboros:tutorial

Interactive tutorial that teaches Ouroboros through hands-on experience.

Usage

ooo tutorial
/ouroboros:tutorial

Tutorial Flow

When this skill is invoked, guide the user through a learn-by-doing tutorial with progressive disclosure.

Phase 1: The Hook (30 seconds)

Start with enthusiasm and immediate value:

Welcome to the Ouroboros Tutorial!

In the next 5 minutes, you'll:
- Transform a vague idea into a precise specification
- See Ouroboros expose hidden assumptions you didn't know you had
- Generate a validated Seed ready for AI execution

Let's start with YOUR idea. What's something you've been wanting to build?

[Wait for user response - any project idea works]

Phase 2: The Interview Experience (2 minutes)

Once they share an idea, immediately start a simplified interview:

Great choice! Let me show you how Ouroboros thinks about this.

[Ask 3-4 targeted Socratic questions about their idea]
- "What's the primary problem this solves?"
- "Who are the main users?"
- "What's the one feature that would make this useful immediately?"

Notice something? Each question exposed an assumption you hadn't articulated.
This is the "aha moment" - requirements clarity BEFORE writing code.

Phase 3: The Quick Win (1 minute)

Generate a mini-seed to show immediate value:

Based on your answers, here's what we've uncovered:

[Display a simplified seed structure]

Goal: [their goal refined]
Constraints: [3 key constraints they mentioned]
Success Criteria: [2-3 clear metrics]

Ambiguity Score: 0.XX [show progress from vague to clear]

This seed is now ready for AI execution. No more "build me X" and hoping for the best!

Phase 4: Feature Discovery (1 minute)

Progressive disclosure of features:


Now that you've seen the core magic, here's what else Ouroboros can do:

Immediate Wins (Available Now):
- ooo unstuck    - 5 lateral thinking personas when you're blocked
- ooo seed       - Generate full specifications from interviews
- ooo evolve     - Evolutionary loop until ontology converges

Advanced Features (Setup Required):
- ooo run        - Execute with visual TUI dashboard
- ooo evaluate   - 3-stage quality verification
- ooo status     - Track project drift in real-time

Want to try any of these now? Or shall I show you the full workflow?

Phase 5: The Real Workflow (30 seconds)

Show the complete pipeline:


The Complete Ouroboros Workflow:

Idea → Interview → Seed → Route → Execute → Evaluate
  ↓        ↓         ↓       ↓        ↓         ↓
Vague    Clear    Frozen   Right    Build    Verified
      Assumptions   Spec    Model    Visibly     Quality

5 commands from idea to validated result:
1. ooo interview "your idea"        # Expose assumptions
2. ooo seed                        # Crystallize spec
3. ooo run                         # Execute with TUI
4. ooo evaluate                    # 3-stage verification
5. ooo status                      # Check drift

Ready to try your first real project?

Phase 6: Call to Action


Your First Real Project awaits!

Pick a path:

Path A: Start Fresh
  ooo interview "your actual project idea"

Path B: Learn More
  ooo help    # Full command reference

Path C: Setup Full Features
  ooo setup   # Enable TUI, evaluation, drift tracking

Which path interests you?

Tutorial Principles

  1. Immediate Value - Show something useful in the first 30 seconds
  2. Learn by Doing - Don't just explain, have them experience it
  3. Progressive Disclosure - Reveal features gradually, not all at once
  4. Quick Wins - Celebrate small milestones throughout
  5. Clear Next Steps - Always give them a specific action to take

Tutorial Checkpoints

Track progress through these checkpoints:

  • User shares an idea
  • User experiences the "aha moment" of exposed assumptions
  • User sees their first mini-seed generated
  • User understands the value proposition
  • User chooses a next step (path A, B, or C)

Common Tutorial Responses

"I don't have a project idea"
No problem! Let's use a classic example: a task management CLI.

[Continue tutorial with task management CLI example]
"This seems complicated"
It's actually simpler than it sounds. Let me show you the 3 commands you'll use 90% of the time:

1. ooo interview "idea"  # Clarify what you want
2. ooo seed             # Generate the spec
3. ooo run              # Build it

Everything else is optional power-user features.
"How is this different from just prompting Claude?"
Great question! The difference is:

Without Ouroboros:
  "Build me a task CLI" → Claude guesses → You realize it's wrong → Rewrite prompt → Repeat

With Ouroboros:
  Interview → Hidden assumptions exposed → Precise spec → Claude builds exactly what you want → First try

The interview saves you hours of iteration.

Success Metrics

A successful tutorial ends when:

  • User has experienced the interview process
  • User understands the seed specification concept
  • User knows their next step
  • User feels confident to try their real project
Show full SKILL.md (142 more words)Show less

Tutorial Variations

For Technical Users
  • Emphasize the TUI dashboard and evolutionary loop
  • Show cost optimization features (PAL Router)
  • Highlight evaluation pipeline
For Non-Technical Users
  • Focus on the interview and clarification process
  • Emphasize the "translate ideas to specs" value
  • Minimize technical jargon
For OMC Users
  • Highlight key differences (TUI, specs, cost optimization)
  • Show migration path from OMC commands
  • Compare feature sets side-by-side

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. When the next action is genuinely a choice, list 2-3 honest options in the next: clause. The breadcrumb line must be the last line of the response.

© Q00, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/tutorial of Q00/ouroboros.

Open the folder on GitHubat commit 0df5b98

Compare with similar skills

Tutorial next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Tutorial compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Tutorial this skillQ00/ouroboros6.2k—~1.6kAutomated safety check: PassMIT
MCP Server Builderanthropics/skills180k62 repos~2.3kAutomated safety check: PassApache-2.0
Hook Development for Claude Code Pluginsanthropics/claude-plugins-official37k11 repos~4.1kAutomated safety check: NotesApache-2.0
Using Superpowersfarm-fe/farm5.6k34 repos~1.4kAutomated safety check: PassMIT
Executing Plans Inlineobra/superpowers296k2 repos~5.1kAutomated safety check: PassMIT
Claude Code Agent Developmentanthropics/claude-plugins-official37k8 repos~2.8kAutomated safety check: PassApache-2.0

Similar skills

  • MCP Server Builder

    anthropics/skills

    Official

    Guides the design and implementation of Model Context Protocol servers in TypeScript or Python, from tool naming and error messages to evaluation.

    180k GitHub starsUsed in 62 repos~2.3k tokens
    Agent WorkflowsAuto-check passed

  • Hook Development for Claude Code Plugins

    anthropics/claude-plugins-official

    Official

    Explains how to write Claude Code plugin hooks, both prompt-based checks and bash commands, for events such as PreToolUse, Stop and SessionStart.

    37k GitHub starsUsed in 11 repos~4.1k tokens
    Agent WorkflowsAuto-check: notes

  • Using Superpowers

    farm-fe/farm

    A skill your agent uses when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions

    5.6k GitHub starsUsed in 34 repos~1.4k tokens
    Agent WorkflowsAuto-check passed

  • Executing Plans Inline

    obra/superpowers

    Has the agent carry out an implementation plan itself, task by task in the current session, keeping a ledger, proving each step with a test and ending with one whole-branch review.

    296k GitHub starsUsed in 2 repos~5.1k tokens
    Agent WorkflowsAuto-check passed

  • Claude Code Agent Development

    anthropics/claude-plugins-official

    Official

    Explains how to write agents for Claude Code plugins: the markdown file with YAML frontmatter, trigger descriptions, model and color settings, and system prompt design.

    37k GitHub starsUsed in 8 repos~2.8k tokens
    Agent WorkflowsAuto-check passed

  • Skill Creator

    Azure/azqr

    Official

    Create new skills, modify and improve existing skills, and measure skill performance.

    794 GitHub starsUsed in 89 repos~8.2k tokens
    Agent WorkflowsAuto-check passed

More from Q00/ouroboros

All 23 skills in this repo

  • Ouroboros Maintainer Triage

    Q00/ouroboros

    Triages and works through GitHub issues and pull requests in the Q00/ouroboros repo as a maintainer, within a stated review boundary and clear limits on what it may change.

    6.2k GitHub stars~1.7k tokensUpdated today
    Auto-check passed

  • Ouroboros PM Interview

    Q00/ouroboros

    Runs a guided product-manager interview that classifies each question automatically and produces a Product Requirements Document.

    6.2k GitHub stars~5.7k tokensUpdated today
    Auto-check passed

  • Brownfield Repo Scanner

    Q00/ouroboros

    Scans a directory for existing git repositories and worktrees, then registers and manages which ones serve as default context during interviews.

    6.2k GitHub stars~2.2k tokensUpdated today
    Auto-check passed

  • Ouroboros Three-Stage Evaluate

    Q00/ouroboros

    Scores an agent's finished work with a three-stage pipeline: free mechanical checks, an advisory semantic review, and an optional multi-model consensus vote.

    6.2k GitHub stars~2.2k tokensUpdated today
    Auto-check passed

  • Ouroboros Evolve Loop

    Q00/ouroboros

    Starts, monitors or rewinds an evolutionary development loop that refines an ontology and acceptance criteria generation by generation until it converges, using the Ouroboros MCP tools.

    6.2k GitHub stars~3.2k tokensUpdated today
    Auto-check passed

  • Ouroboros Settings Opener

    Q00/ouroboros

    Opens or drives the Ouroboros settings GUI, picking a browser, TUI or chat-based approach depending on whether the user can reach a browser window.

    6.2k GitHub stars~1.2k tokensUpdated today
    Auto-check passed

Categories

Questions about Tutorial

What does Tutorial do?

Interactive tutorial teaching Ouroboros hands-on. An agent skill from Q00/ouroboros. Tutorial is an agent skill from Q00/ouroboros.

When should I use Tutorial?

Tutorial fits situations like: agent Workflows work in your project.

How do I install Tutorial in Claude Code?

Run `npx skills add Q00/ouroboros --skill tutorial -a claude-code`. Or copy the skill folder (skills/tutorial in Q00/ouroboros) into .claude/skills/tutorial in your project. Claude Code loads it when a task matches its description.

How do I install Tutorial in Codex?

Run `npx skills add Q00/ouroboros --skill tutorial -a codex`. Or copy the skill folder (skills/tutorial in Q00/ouroboros) into .agents/skills/tutorial in your project. Codex loads it when a task matches its description.

Can I use Tutorial in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Q00/ouroboros --skill tutorial -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/tutorial, .gemini/skills/tutorial, .github/skills/tutorial and .opencode/skills/tutorial in your project.

What does Tutorial need to run?

SKILL.md names no scripts, command-line tools or credentials: Tutorial is instructions for the agent only.

Does Tutorial access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Tutorial safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Tutorial use?

Tutorial is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Tutorial use?

About 1.6k tokens (SKILL.md is roughly 6.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Tutorial?

Skills that share tags, products or a category with Tutorial: MCP Server Builder (anthropics/skills, 180k stars), Hook Development for Claude Code Plugins (anthropics/claude-plugins-official, 37k stars), Using Superpowers (farm-fe/farm, 5.6k stars) and Executing Plans Inline (obra/superpowers, 296k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Tutorial?

Q00 (a GitHub user) maintains it in Q00/ouroboros, which has 6,189 GitHub stars. The repository holds 23 skills in this directory. The repository was last updated on October 6, 2026.

Source: Q00/ouroboros on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.