Skip to content

> skills.catalog

AgentOps Skills

Every skill works alone. Compose them into flows when you want more structure.

The 12 factors describe the rules. The skills below enforce them in your runtime.

Core skills

/quickstart

One-line read on what to do next.

Use it when: First time in a repo. Or any time you’re lost.

/councilFactor: Validate Externally (V)

Independent judges review your plan or PR.

Use it when: Multi-model consensus before you commit.

/researchFactor: Research Before You Build (IV)

Codebase context plus prior learnings.

Use it when: Unfamiliar territory. Or where past decisions matter.

/pre-mortemFactor: Validate Externally (V)

Pressure-test the plan before code.

Use it when: Load-bearing change. Run before /implement.

/implementFactor: Lock Progress Forward (VI)

One scoped task. Built. Validated.

Use it when: You know what to build. Gates, not vibes.

/rpi

Research → plan → pre-mortem → build → vibe → post-mortem.

Use it when: The full lifecycle, end to end.

/vibeFactor: Validate Externally (V)

Code-quality review before merge.

Use it when: Every merge. Auto-fires at the end of /rpi.

/evolveFactor: Compound Knowledge (VIII)

Chase a goal autonomously, with regression gates.

Use it when: You have GOALS.md. Fix the worst fitness gap.

/dreamFactor: Extract Learnings (VII) · Compound Knowledge (VIII)

Bounded corpus compounding. Never mutates source.

Use it when: Prepare learnings for the next run without touching product code.

Full catalog

Grouped by role. Every entry is a slash command in your agent chat.

Validation

/council/vibe/pre-mortem/post-mortem

Flows

/research/plan/implement/crank/swarm/rpi/evolve

Bookkeeping

/retro/forge/flywheel/compile

Session

/handoff/recover/status/trace/provenance/dream

Product

/product/goals/release/readme/doc

Utility

/brainstorm/bug-hunt/complexity/scaffold/push

Full reference lives in the AgentOps repo.

The ao CLI

The repo-native operator surface behind the skills. Handles retrieval, health checks, compounding, goals, and terminal workflows. Always-on orchestration belongs to a a dedicated out-of-session substrate; AgentOps owns the loop and the corpus.

ao quick-startSet up AgentOps in a repo.
ao doctorHealth check.
ao demoValue path in 5 minutes.
ao search "query"Search sessions and local knowledge.
ao lookup --query "topic"Retrieve curated learnings.
ao context assembleBuild a task briefing.
ao rpi phased "fix auth startup"Run the phased lifecycle.
ao evolve --max-cycles 1One autonomous improvement cycle.
ao maturity --scanCheck corpus hygiene.
ao vibe-checkFlywheel + repo health.

The CLI is optional but recommended. Install instructions on the Install page.

The .agents/ directory

AgentOps writes all bookkeeping to a local .agents/ directory in your repo: learnings, findings, handoffs, pre-mortems, plans, and per-run execution packets. It is plain text: grep it, diff it, review it, commit it, or ignore it. No telemetry, no cloud service, no lock-in.

This is how Factor VII: Extract Learnings and Factor VIII: Compound Knowledge are implemented in practice. The rule lives in the factor; the runtime artifact lives in the repo.