debug
Systematic debugging workflow with root cause verification before fixing
parallel-orchestrate
Orchestrate N independent TDD subagents from a YAML task manifest with worktree isolation
pipeline
Full pipeline from design doc through plan, manifest, parallel orchestration, to branch completion
implement
Auto-started default workflow. Overridden by iterate, debug, or orchestrate when invoked.
iterate
Autonomous TDD implementation workflow with phase gates.
delegate
Fable decomposes work into a tiered task manifest; haiku/sonnet workers execute in parallel worktrees; Fable re-enters only for escalations and integration.
develop
PR-based development workflow with SE team simulation
distill
Distill session episodes into persistent memory patterns
experiment
Autonomous experiment workflow with eval gates, journal memory, and team support.
plan-to-manifest
Translate a superpowers implementation plan into a parallel orchestration YAML manifest
poll
Controlled polling for async operations at specified intervals
pr-comment
PR review comment workflow - understand the concern before fixing
remember
Save a learning to persistent memory with automatic scope inference
spawn
How to spawn subagents correctly under the router. Use when delegating work to a specialized agent.
teams-develop
Full PR-based development lifecycle using native Claude Code teams — PM coordinates specialized agents through intake, research, design, implement, review, integrate, and complete phases
verify
Run code quality checks (ruff, black, mypy, pytest)
skill-creator
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends AI Agent's capabilities with specialized knowledge, workflows, or tool integrations.
github-local-issue-pr
Use only for explicit GitHub issue or pull request work in the current repository: when the user asks to create, update, read, or link a GitHub issue/PR, or when the task starts from a GitHub issue/PR URL or number. Do not use for ordinary coding tasks unless GitHub issue/PR management is explicitly requested.
telegram-topics
Manage OpenClaw Telegram forum topics for configured Telegram group accounts. Use when asked to create/delete/list/cleanup Telegram topics, route a topic to an agent, create Telegram topics for opencode/ACP project work, or distinguish OpenClaw ops topics from coding/OpenCode topics.
context-daddy
Context management tools for Claude Code - provides intelligent codebase mapping with Python, Rust, and C++ parsing, duplicate detection, and MCP-powered symbol queries. Use this skill when working with large codebases that need automated indexing and context management.
ui-ux-design
Create production-grade frontend interfaces with strong UX and visual craft. Use when building web components, pages, dashboards, forms, landing pages, modals, or any UI. Use when user says 'build a form', 'create a dashboard', 'design a component', 'make a landing page', or asks for UI/UX work. Use even when the user just says 'make this look better' or pastes screenshots/mockups without explicitly naming a design task.
context7
Documentation lookup via Context7 REST API. Use when the user needs current library APIs, framework patterns, migration guidance, or official code examples for React, Next.js, Prisma, Express, Vue, Angular, Svelte, or other npm/PyPI packages. Use when the user says 'how do I use X library', 'what's the API for Y', or asks for official documentation. Use even when you think you know the answer — training data may not reflect recent releases.
github-navigator
GitHub operations via gh CLI. CRITICAL: Use instead of WebFetch for any `github.com` URL or GitHub repo path like `owner/repo`. Use when the user asks to inspect repositories, files, issues, pull requests, releases, Actions runs, or repository structure. Use when the user says 'show README', 'list issues', 'check PR', 'clone repo', or 'analyze this repo'. Use even when the user just pastes a github.com URL without an explicit verb.
skill-crafting
Create, fix, and validate skills for AI agents. Use when user says 'create a skill', 'build a skill', 'fix my skill', 'skill not working', 'analyze my skill', 'validate skill', 'audit my skills', 'check character budget', 'create a skill from this session', 'turn this into a skill', 'make this reusable', 'can this become a skill', 'should this be a skill', or asks for reusable patterns in the session. Use even if the user does not explicitly say 'skill' but is sketching a reusable workflow.
maven-tools
JVM dependency intelligence via Maven Tools MCP server. Use when the user asks about Maven or Gradle dependencies, safe upgrades, CVEs, license risks, release history, or project dependency health. Use when reviewing `pom.xml`, `build.gradle`, `build.gradle.kts`, or Maven coordinates. Use when the user says 'check my dependencies', 'should I upgrade X', 'what can I safely bump', or 'is this version safe'. Use even when the user just pastes a `groupId:artifactId` coordinate without a verb.
github-issue-creator
>-
github-issue-pr-operator
>-
github-pr-creator
>-
github-project-reporter
>-
project-charter-creator
>-
project-plan-creator
>-
rfi-creator
>-
rfp-creator
>-
code-simplifier
Use when asked to simplify recently changed code without changing behavior or explicitly asked to run the code-simplifier subagent.
acceptance-criteria-verification
Use after implementing features - verifies each acceptance criterion with structured testing and posts verification reports to the GitHub issue
issue-decomposition
Use when an issue is too large for a single task - breaks into linked sub-issues with full documentation, ensuring manageable work units
issue-driven-development
Use for any development work - the master 13-step coding process that orchestrates all other skills, ensuring GitHub issue tracking, proper branching, TDD, code review, and CI verification
issue-lifecycle
Use throughout all work - ensures GitHub issues are updated continuously as work happens, not batched at the end
local-service-testing
Use when code changes touch database, cache, queue, or other service-dependent components - enforces testing against real local services instead of mocks
tdd-full-coverage
Use when implementing features or fixes - test-driven development with RED-GREEN-REFACTOR cycle and full code coverage requirement
deferred-finding
Use when a review finding cannot be fixed in current PR - creates properly documented tracking issue with full context, linked to parent, following full issue-driven-development process
pre-work-research
Use before starting implementation - research repository documentation, codebase patterns, and external resources to inform the approach
project-board-enforcement
MANDATORY for all work - the project board is THE source of truth. This skill provides verification functions and gates that other skills MUST call. No work proceeds without project board compliance.
comprehensive-review
Use after implementing features - 7-criteria code review with MANDATORY artifact posting to GitHub issue; blocks PR creation until complete
inline-documentation
Use when writing code - ensure complete JSDoc, docstrings, and inline comments assuming documentation will be generated from code
type-design-analyzer
Use when asked to evaluate type design/invariants or explicitly asked to run the type-design-analyzer subagent.
features-documentation
Use when user-facing features change. Ensures features documentation is updated. Pauses work if documentation has drifted, triggering documentation-audit skill.
ipv6-first
IPv6 is THE first-class citizen. All code, tests, documentation, and configurations MUST be IPv6-first. IPv4 MAY be added only for legacy support as a second-class citizen.
branch-discipline
Use before any code changes - hard gate ensuring work never happens on main branch, with proper feature branch creation from correct base
inclusive-language
Use when writing code, documentation, or comments - always use accessible and respectful terminology
Page 1269 of 1665 · 83239 results