ai-debug
Finds the root cause of broken behaviour and names it at file:line, then writes the check that fails for that reason before changing anything. Also resolves mer
38,472 Skills
Search uses this published catalog; rankings and counts are snapshots.
Finds the root cause of broken behaviour and names it at file:line, then writes the check that fails for that reason before changing anything. Also resolves mer
Answers questions about this repository by reading it, anchored to file:line, and tours an unfamiliar area for somebody who has just arrived. Trigger for "where
Use when the user wants to build in an autonomous loop — "loop this feature", "run these overnight", "write the goal for this" — pinning the loop contract: what
Reports a reproducible fault to a team or an upstream project — for ai-engineering itself or for any service the client is building — as a governed payload: clo
Saves a finding that took real time to reach — a non-obvious behaviour, an integration trap, a workaround and the reason it is needed — as committed markdown, s
Work out what you're actually building by answering one question at a time, and turn every answer into a check — so you finish with a written standard for what
Use when the work depends on versioned or external behaviour — adding a package, writing setup or config, integrating an SDK or a paid API, debugging a framewor
Finds evidence from outside this repository and reports it with numbered citations, or marks a claim [unsourced] and leaves it marked. Uses only the tools the c
Test system behavior under extreme load to find breaking points, capacity limits, and failure modes. Covers stress, spike, and breakpoint testing with k6 (prima
Batches features and runs them. Tell it which features to batch and it writes features/QUEUE.md; pass it to /goal and it works that queue overnight, one feature at a time, building and verifying each one and opening a pull request when it passes. Use when the user says "batch the
Writes the /goal condition that loops one feature. Sets the feature up first by running new-feature if it doesn't have a spec yet, then produces the goal command to paste into Claude Code or Codex. Use when the user says "write the goal for this", "loop this feature", "make this
Sets a feature up end to end — makes the feature folder, asks whether to interview first, gets the mock built and approved, then writes the spec. Produces a feature that is ready to build, with no loop attached. Use when the user says "new feature", "set up a feature", "make the
GitHub backup for OpenClaw workspace. Use when user says "同步", "备份", "backup", "sync", "push to github", or asks about backup status/history/failures. Manages git-based full backup of ~/.openclaw to GitHub.
Use at the start of any multi-step task and during exploration — before reading files, searching, or re-checking completed work, especially when tempted to read whole files, re-verify known facts, or run independent lookups one at a time.
Use before ending any turn that used tools or produced a deliverable — when tempted to ask "Want me to…?", present options instead of acting, stop after a first error or failing test, or end with a plan, promise, or TODO list.
Catalog captured:2026-11-21