Software Development AI agent skills

13,359 skills in the archive. Read a skill’s instructions or open its original repository.

• Solid

  by @openclaw

  Write, port, review, or test Solid 2 UI in OpenClaw (Control UI, plugin views, Canvas hosts), including state ownership, Lit interop during the migration, native overlays, testing, performance, and lessons learned.

• Claw Score

  by @openclaw

  Audit or refresh OpenClaw maturity scorecard docs from root taxonomy, maturity scores, and QA evidence artifacts without using maintainer discrawl data or committed inventory reports.

• Technical Documentation

  by @openclaw

  Build and review high-quality technical docs as well as agent instruction files in your repository.

• Autoreview

  by @openclaw

  Structured code review when explicitly requested, preferring OpenAI/Codex before Claude.

• Release Openclaw Maintainer

  by @openclaw

  Prepare, publish, recover, or verify OpenClaw beta, stable, and extended-stable releases, including approved backports.

• Auto Qa

  by @openclaw

  Run OpenClaw-wide autonomous QA and live/stress campaigns across independent subsystem lanes, with verified fixes and a resumable evidence report.

• Openclaw Pr Maintainer

  by @openclaw

  Review, triage, repair, or land OpenClaw issues and pull requests with current-source evidence and the native maintainer workflow.

• Release Openclaw Ci

  by @openclaw

  Run, watch, debug, and summarize OpenClaw full release CI, release checks, live provider gates, install/update proofs, and release-secret preflights.

• Model Usage

  by @openclaw

  Summarize CodexBar local cost logs by model for Codex or Claude, including current or full breakdowns.

• Openclaw Live Updater

  by @openclaw

  Maintain the canonical live OpenClaw main checkout, macOS LaunchAgent-managed Gateway, local macOS app, exact-head main CI, and recurring full release validation. Use for fast-forward update heartbeats, post-update runtime…

• Openclaw Testing

  by @openclaw

  Choose proportional OpenClaw tests and checks, diagnose failures, and route environment-sensitive or release proof to its owner.

• Diagram Maker

  by @openclaw

  Create SVG/HTML or Excalidraw diagrams for concepts, architecture, flows, and whiteboards.

• Meme Maker

  by @openclaw

  Search meme templates, suggest formats, and generate local or hosted image memes.

• Openclaw Ci Limits

  by @openclaw

  Manage OpenClaw GitHub Actions and Blacksmith CI capacity, runner-registration budgets, fanout caps, main-push single-flight, shard sizing, hosted-runner offload, queue health, and safe ramp-down/ramp-up changes. Use when tuning…

• Control Ui E2e

  by @openclaw

  Use when designing, testing, fixing, or extending the OpenClaw Control UI GUI, including UI stress-test galleries with feedback inputs, Vitest + Playwright end-to-end checks, mocked Gateway flows, screenshots/videos, or…

• Clawsweeper

  by @openclaw

  Use for all ClawSweeper work: OpenClaw issue/PR sweep reports, repair jobs, cloud fix PRs, @clawsweeper maintainer mention commands, trusted ClawSweeper-reviewed autofix/automerge, GitHub Actions monitoring, permissions, gates,…

• Openclaw Debugging

  by @openclaw

  Debug OpenClaw model, provider, tool-surface, code-mode, streaming, and live/Crabbox behavior by choosing the right logs, probes, and proof path before changing code, including fetching stored sessions, transcripts, and…

• Release Openclaw Plugin Testing

  by @openclaw

  Plan and run pre-release OpenClaw plugin validation across bundled plugins, package artifacts, lifecycle commands, doctor/fix, config round-trip, gateway startup, SDK compatibility, Docker E2E, Package Acceptance, and Testbox…

• Openclaw Repair Sweep

  by @openclaw

  Run scoped OpenClaw issue/PR repair campaigns: coordinate workers, prove root causes, and land or close verified work under the requested authority.

• Openclaw Test Performance

  by @openclaw

  Benchmark, diagnose, and optimize OpenClaw test and plugin-suite runtime, import hotspots, CPU/RSS, heap growth, and slow coverage paths.

• Gitcrawl

  by @openclaw

  GitHub archive: issue/PR search, sync freshness, duplicate clusters, current GitHub handoff, and Gitcrawl repo work.

• Openclaw Changelog Update

  by @openclaw

  Regenerate OpenClaw release changelog sections from git history before beta, stable, or extended-stable releases.

• Graincrawl

  by @openclaw

  Granola archive: search, sync freshness, notes, transcripts, panels, SQL counts, and Graincrawl repo work.

• Discord Clawd

  by @openclaw

  Use to talk to the Discord-backed OpenClaw agent/session; not for archive search.

• Discrawl

  by @openclaw

  Discord archive: search, sync freshness, DMs, summaries, TUI, repo/release work.

• Verify Release

  by @openclaw

  Verify regular or extended-stable OpenClaw releases against the exact publication surfaces, workflow identities, package provenance, smoke tests, and live Gateway behavior expected for that release track.

• Node Connect

  by @openclaw

  Diagnose OpenClaw Control UI browser and native Android, iOS, or macOS node connection failures across route, auth, pairing, QR/setup-code, and reconnect states.

• Browser Automation

  by @openclaw

  Use when controlling web pages with the OpenClaw browser tool, especially multi-step flows, login checks, tab management, or recovery from stale refs/timeouts.

• Deslop

  by @openclaw

  Diff-scoped AI-slop cleanup pass: strip comment slop, defensive-check slop, type-laundering, and style drift from the current branch diff before autoreview.

• Crabbox Apps

  by @openclaw

  Use when asked to open, run, test, or show an app in Crabbox, including native desktops, web previews, and computer use on a temporary machine.

• Coding Agent

  by @openclaw

  Delegate coding work to Codex, Claude Code, or OpenCode as background workers; not simple edits or read-only code lookup.

• Gh Issues

  by @openclaw

  Fetch GitHub issues, select candidates, spawn background fix agents, open PRs, and optionally process PR review comments.

• Wiki Maintainer

  by @openclaw

  Maintain the OpenClaw memory wiki vault with deterministic pages, managed blocks, and source-backed updates.

• Openclaw Refactor Docs

  by @openclaw

  Refactor an existing OpenClaw docs page with source-audited preservation, restructuring, and verification.

• Security Triage

  by @openclaw

  Triage OpenClaw security advisories, drafts, and GHSA reports with shipped-tag and trust-model proof.

• Github

  by @openclaw

  GitHub CLI for issues, PRs, CI/check logs, comments, reviews, releases, repos, and gh api queries.

• Release Openclaw Mac

  by @openclaw

  Run or recover OpenClaw macOS release signing, notarization, appcast, and asset promotion.

• Gifgrep

  by @openclaw

  Search GIF providers with CLI/TUI, download results, and extract stills/sheets.

• Tavily

  by @openclaw

  Tavily web search, content extraction, and research tools.

• Systematic Debugging

  by @obra

  Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

• Using Superpowers

  by @obra

  Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions

• Requesting Code Review

  by @obra

  Use when completing tasks, implementing major features, or before merging to verify work meets requirements

• Writing Plans

  by @obra

  Use when you have a spec or requirements for a multi-step task, before touching code

• Test Driven Development

  by @obra

  Use when implementing any feature or bugfix, before writing implementation code

• Receiving Code Review

  by @obra

  Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind…

• Verification Before Completion

  by @obra

  Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always

• Using Git Worktrees

  by @obra

  Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback

• Finishing A Development Branch

  by @obra

  Use when implementation is complete, all tests pass, and you need to decide how to integrate the work

• Chief Of Staff

  by @mattpocock

  Pursue a long-running goal in a single session by co-ordinating subagents.

• Docs Governance

  by @affaan-m

  Route broad documentation-governance requests to existing ECC skills and run an opt-in, read-only audit of mapped documentation roles, links, ADR indexes, and evidence references. Use when a user asks for documentation…

• Module Regression

  by @affaan-m

  Govern cross-module regression in large repositories with a REGRESSION.md ledger that records each module's downstream consumers and executable acceptance command. After a change, run the changed module and every affected…

• Change Impact

  by @affaan-m

  Perform evidence-backed impact analysis before changing code, data, interfaces, or governance documents, then compare the planned impact with the actual diff after implementation. Covers call paths, data and schema, API…

• Mcp Dependency Review

  by @affaan-m

  Statically review MCP configuration for mutable package references before approval or CI, without executing discovered MCP servers. Use when reviewing .mcp.json, Cursor, VS Code, Claude, Windsurf, or other repo-scoped MCP config.

• Ecc Conventions

  by @affaan-m

  Development conventions and patterns for ECC. JavaScript project with conventional commits.

• Dmux Workflows

  by @affaan-m

  Multi-agent orchestration using dmux (tmux pane manager for AI agents). Patterns for parallel agent workflows across Claude Code, Codex, OpenCode, and other harnesses. Use when running multiple agent sessions in parallel or…

• Mcp Server Patterns

  by @affaan-m

  Build MCP servers with Node/TypeScript SDK — tools, resources, prompts, Zod validation, stdio vs Streamable HTTP. Use Context7 or official MCP docs for latest API. Use when building or debugging an MCP server — tools, resources,…

• Mle Workflow

  by @affaan-m

  Production machine-learning engineering workflow for data contracts, reproducible training, model evaluation, deployment, monitoring, and rollback. Use when building, reviewing, or hardening ML systems beyond one-off notebooks.

• Exa Search

  by @affaan-m

  Neural search via Exa MCP for web, code, and company research. Use when the user needs web search, code examples, company intel, people lookup, or AI-powered deep research with Exa's neural search engine.

• Bun Runtime

  by @affaan-m

  Bun as runtime, package manager, bundler, and test runner. When to choose Bun vs Node, migration notes, and Vercel support.

• Everything Claude Code

  by @affaan-m

  Development conventions and patterns for everything-claude-code. JavaScript project with conventional commits.

• Setup Matt Pocock Skills

  by @mattpocock

  Configure this repo for the engineering skills: set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.

• Teach

  by @mattpocock

  Teach the user a new skill or concept, within this workspace.

• Codebase Design

  by @mattpocock

  Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another…

• Prototype

  by @mattpocock

  Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.

• Tdd

  by @mattpocock

  Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.

• Triage

  by @mattpocock

  Move issues and external PRs through a state machine of triage roles, categorise, verify, grill if needed, and write agent-ready briefs.

• Git Guardrails Claude Code

  by @mattpocock

  Set up Claude Code hooks to block dangerous git commands (push, reset --hard, clean, branch -D, etc.) before they execute. Use when user wants to prevent destructive git operations, add git safety hooks, or block git push/reset…

• Setup Ts Deep Modules

  by @mattpocock

  Wire dependency-cruiser into a TypeScript repo so each package is a deep module, with implementation hidden in subfolders and reachable only through its entry-point files. User-invoked.

• Diagnosing Bugs

  by @mattpocock

  Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.

• Improve Codebase Architecture

  by @mattpocock

  Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.

• Ask Matt

  by @mattpocock

  Ask which skill or flow fits your situation. A router over the skills in this repo.

• Pr

  by @mattpocock

  Use when writing a PR body.

• Code Review

  by @mattpocock

  Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes: Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/spec…

• To Tickets

  by @mattpocock

  Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker (edges as text in one file per ticket locally, or native blocking links…

• Research

  by @mattpocock

  Investigate a question against high-trust primary sources and capture the findings as a Markdown file in the repo. Use when the user wants a topic researched, docs or API facts gathered, or reading legwork delegated to a…

• Setup Pre Commit

  by @mattpocock

  Set up Husky pre-commit hooks with lint-staged (Prettier), type checking, and tests in the current repo. Use when user wants to add pre-commit hooks, set up Husky, configure lint-staged, or add commit-time…

• Scaffold Exercises

  by @mattpocock

  Create exercise directory structures with sections, problems, solutions, and explainers that pass linting. Use when user wants to scaffold exercises, create exercise stubs, or set up a new course section.

• Migrate To Shoehorn

  by @mattpocock

  Migrate test files from `as` type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, wants to replace `as` in tests, or needs partial test data.

• To Spec

  by @mattpocock

  Turn the current conversation into a spec and publish it to the project issue tracker: no interview, just synthesis of what you've already discussed.

• Writing Beats

  by @mattpocock

  Writing, exploit; assemble raw material into a journey of beats, grounding each term before a beat leans on it.

• Claude Handoff

  by @mattpocock

  Hand the current conversation off to a fresh background agent that picks up the work immediately.

• Handoff

  by @mattpocock

  Compact the current conversation into a handoff document for another agent to pick up.

• Writing Shape

  by @mattpocock

  Writing, exploit: shape raw material into an article, paragraph by paragraph.

• Resolving Merge Conflicts

  by @mattpocock

  Use when you need to resolve an in-progress git merge/rebase conflict.

• Implement

  by @mattpocock

  Implement a piece of work based on a spec or set of tickets.

• Retro

  by @mattpocock

  Conduct a retrospective on a coding session.

• Implement Spec

  by @mattpocock

  Implement a specification in code.

• Continuous Learning

  by @affaan-m

  [OBSOLETO - usar continuous-learning-v2] Extractor de skill por hook Stop v1 heredado. v2 es un superconjunto estricto con aprendizaje basado en instintos, con alcance de proyecto y hooks confiables. No invocar v1; dirigir…

• Continuous Learning V2

  by @affaan-m

  Sistema de aprendizaje basado en instintos que observa sesiones mediante hooks, crea instintos atómicos con puntuación de confianza y los evoluciona en skills/comandos/agentes. v2.1 agrega instintos con alcance de proyecto para…

• Security Review

  by @affaan-m

  Usar este skill al agregar autenticación, manejar entradas de usuario, trabajar con secretos, crear endpoints de API o implementar funcionalidades de pago/sensibles. Proporciona lista de verificación y patrones de seguridad…

• Database Migrations

  by @affaan-m

  Buenas prácticas de migración de base de datos para cambios de esquema, migraciones de datos, rollbacks y despliegues de tiempo cero en PostgreSQL, MySQL y ORMs comunes (Prisma, Drizzle, Kysely, Django, TypeORM, golang-migrate).

• Quarkus Tdd

  by @affaan-m

  Desarrollo guiado por pruebas para Quarkus 3.x LTS usando JUnit 5, Mockito, REST Assured, pruebas Camel y JaCoCo. Usar al agregar funcionalidades, corregir bugs o refactorizar servicios orientados a eventos.

• Coding Standards

  by @affaan-m

  Convenciones de codificación base entre proyectos para nomenclatura, legibilidad, inmutabilidad y revisión de calidad de código. Usar skills de frontend o backend para patrones específicos de frameworks.

• Deployment Patterns

  by @affaan-m

  Flujos de trabajo de despliegue, patrones de pipeline CI/CD, contenedorización Docker, health checks, estrategias de rollback y listas de verificación de preparación para producción de aplicaciones web.

• Tdd Workflow

  by @affaan-m

  Usar este skill al escribir nuevas funcionalidades, corregir bugs o refactorizar código. Aplica el desarrollo guiado por pruebas con 80%+ de cobertura incluyendo pruebas unitarias, de integración y E2E.

• Springboot Patterns

  by @affaan-m

  Patrones de arquitectura Spring Boot, diseño de API REST, servicios en capas, acceso a datos, caché, procesamiento asíncrono y logging. Usar para trabajo de backend en Java con Spring Boot.

• Laravel Security

  by @affaan-m

  Buenas prácticas de seguridad en Laravel para autenticación/autorización, validación, CSRF, asignación masiva, subida de archivos, secretos, limitación de velocidad y despliegue seguro.

• Kotlin Testing

  by @affaan-m

  Patrones de pruebas Kotlin con Kotest, MockK, pruebas de coroutines, pruebas basadas en propiedades y cobertura con Kover. Sigue la metodología TDD con prácticas idiomáticas de Kotlin.

• Quarkus Verification

  by @affaan-m

  Bucle de verificación para proyectos Quarkus: build, análisis estático, pruebas con cobertura, escaneos de seguridad, compilación nativa y revisión de diff antes del lanzamiento o PR.

• Kotlin Patterns

  by @affaan-m

  Patrones idiomáticos de Kotlin, buenas prácticas y convenciones para construir aplicaciones Kotlin robustas, eficientes y mantenibles con coroutines, null safety y builders de DSL.