github.com/Q00/ouroboros
| Skill | Added | Review |
|---|---|---|
auto skills/auto/SKILL.md Use when the work spans several files or replaces a framework, language, auth, storage, or API layer (rewrites and migrations included), and the user wants it to end up working and tested. Asks only what is missing, writes a spec with acceptance criteria, then runs and verifies it in the background. Not for questions, small edits, or an existing Seed (use run). | 62 Impact — No eval scenarios have been run Securityby Passed No findings from the security scan Version: 592c667 | |
brownfield skills/brownfield/SKILL.md Scan and manage brownfield repository/worktree defaults for interviews | 61 Impact — No eval scenarios have been run Securityby Passed No findings from the security scan Version: 592c667 | |
cancel skills/cancel/SKILL.md Cancel stuck or orphaned executions | 64 Impact — No eval scenarios have been run Securityby Passed No findings from the security scan Version: 592c667 | |
ouroboros-config skills/config/SKILL.md Open or drive the Ouroboros settings GUI (browser, TUI, or conversational fallback) | 64 Impact — No eval scenarios have been run Securityby Passed No findings from the security scan Version: 592c667 | |
evaluate skills/evaluate/SKILL.md Use when the user wants proof that finished work meets its acceptance criteria, not just that tests pass: 'verify it is actually done', 'check it against the spec', 'evaluate the run'. Runs mechanical checks, a semantic review per criterion, and multi-model consensus when uncertain. With execution.auto_evolve on (the default), a rejected result with a Seed continues into a Ralph fix loop; pass auto_evolve: false to verify only. | 70 Impact — No eval scenarios have been run Securityby Passed No findings from the security scan Version: 592c667 | |
evolve skills/evolve/SKILL.md Start or monitor an evolutionary development loop | 62 Impact — No eval scenarios have been run Securityby Passed No findings from the security scan Version: 592c667 | |
ouroboros-help skills/help/SKILL.md Full reference guide for Ouroboros commands and agents | 56 Impact — No eval scenarios have been run Securityby Passed No findings from the security scan Version: 592c667 | |
idk skills/idk/SKILL.md Calibrate interview explanations from the user's stated understanding | 60 Impact — No eval scenarios have been run Securityby Passed No findings from the security scan Version: 592c667 | |
interview skills/interview/SKILL.md Use when the user wants to build or change something but the request is vague or open-ended: 'help me figure out what to build', 'I'm not sure what it should do', 'add X' with no details, or no clear definition of done. Runs a short Socratic interview that turns the idea into goals, constraints, and acceptance criteria before any code is written. Not for simple questions, small clear edits, or an existing Seed. | 66 Impact — No eval scenarios have been run Securityby Low Low-risk findings worth noting Version: 592c667 | |
ooo skills/ooo/SKILL.md Start Ouroboros onboarding. Use when the user sends bare `ooo`, asks to start Ouroboros, or is using Ouroboros for the first time. | 67 Impact — No eval scenarios have been run Securityby Passed No findings from the security scan Version: 592c667 | |
pm skills/pm/SKILL.md Use when the user wants product requirements rather than code: 'write a PRD', 'product requirements', 'spec this feature for the team', 'ooo pm'. Runs a PM-focused interview with automatic question classification and produces a PRD/PM document. Not for implementation requests. | 64 Impact — No eval scenarios have been run Securityby Passed No findings from the security scan Version: 592c667 | |
publish skills/publish/SKILL.md Publish Seed specification as GitHub Issues for team-based project management | 60 Impact — No eval scenarios have been run Securityby Passed No findings from the security scan Version: 592c667 | |
qa skills/qa/SKILL.md General-purpose QA verdict for any artifact type | 48 Impact — No eval scenarios have been run Securityby Passed No findings from the security scan Version: 592c667 | |
ralph skills/ralph/SKILL.md MCP-owned Ralph loop around background evolve_step jobs | 52 Impact — No eval scenarios have been run Securityby Passed No findings from the security scan Version: 592c667 | |
resume-session skills/resume-session/SKILL.md List in-flight Ouroboros sessions and show the commands needed to re-attach after MCP disconnect | 65 Impact — No eval scenarios have been run Securityby Passed No findings from the security scan Version: 592c667 | |
ouroboros-run skills/run/SKILL.md 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). | 64 Impact — No eval scenarios have been run Securityby Passed No findings from the security scan Version: 592c667 | |
seed skills/seed/SKILL.md Use when goal, constraints, and success criteria are already settled and the user wants them frozen into a formal spec an agent can execute and verify: 'turn this into a spec', 'write it up as a Seed', or right after an interview. Returns an immutable Seed with acceptance criteria. Not for vague requests (use interview first). | 70 Impact — No eval scenarios have been run Securityby Passed No findings from the security scan Version: 592c667 | |
setup skills/setup/SKILL.md Guided onboarding wizard for Ouroboros setup | 62 Impact — No eval scenarios have been run Securityby Passed No findings from the security scan Version: 592c667 | |
ouroboros-status skills/status/SKILL.md Check session status and measure goal drift | 57 Impact — No eval scenarios have been run Securityby Passed No findings from the security scan Version: 592c667 | |
threat-model .claude/skills/threat-model/SKILL.md Build a threat model for a target codebase. Three modes: "interview" walks an application owner through the four-question framework and produces a threat model from their answers; "bootstrap" derives a threat model from the code plus past vulnerabilities (CVEs, git history, pentest reports) when no owner is available; "bootstrap-then-interview" chains the two when both owner and codebase are present. All write THREAT_MODEL.md in a shared schema. Use when asked to "threat model", "build a threat model", "map the attack surface", or "what should we be worried about in this codebase". | — |