Skip to content

Popular Coding & Development Skills

Code generation, GitHub workflows, testing, reviews, and front-end development.

626verified Agent Skills

Coding skills help agents move from suggesting snippets to completing repeatable development work. This collection covers repository operations, debugging, test generation, code review, documentation, and front-end workflows. Rankings favor skills with clear tooling requirements and public source material, so you can understand what will run before adding it to your environment.

Top Coding & Development Skills

Ranked by their position in the current overall directory snapshot.

#1876

CodeBuddy CLI For OpenClaw

CodeBuddy Code CLI installation, configuration and usage guide. CodeBuddy Code is Tencent's AI-powered CLI programming assistant supporting natural language driven development. - MANDATORY TRIGGERS: CodeBuddy, codebuddy, AI CLI, Tencent AI coding, @tencent-ai/codebuddy-code, terminal AI assistant - Use when: installing CodeBuddy CLI, configuring CodeBuddy, using CodeBuddy commands, troubleshooting CodeBuddy issues

CodingOpenClaw
#1878

Tmux Agents

Manage background coding agents in tmux sessions. Spawn Claude Code or other agents, check progress, get results.

CodingOpenClaw
#1898

Openclaw Unity Skill

Control Unity Editor via OpenClaw Unity Plugin. Use for Unity game development tasks including scene management, GameObject/Component manipulation, debugging.

CodingOpenClaw
#1912

Growth Engineer

Growth Engineer for mobile apps and agent runtimes including OpenClaw and Hermes. Correlate analytics, crashes, billing, feedback, store signals, and repo context into proposal drafts that can flow into agent chat, GitHub issues, or draft pull requests.

CodingOpenClaw
#1931

Swiftui Performance Audit

Audit and improve SwiftUI runtime performance from code review and architecture. Use for requests to diagnose slow rendering, janky scrolling, high CPU/memory usage, excessive view updates, or layout thrash in SwiftUI apps, and to provide guidance for user-run Instruments profiling when code review alone is insufficient.

CodingOpenClaw
#1937

Buildlog

Record, export, and share your AI coding sessions as replayable buildlogs

CodingOpenClaw
#1978

Pre Mortem Analyst

Imagine the project already failed, then work backward to find why. More powerful than risk assessment because it assumes failure is certain. Use when user says "pre-mortem", "premortem", "imagine this failed", "what could go wrong", "risk analysis", "before we launch", "stress test", "what would kill this", "project risks".

CodingOpenClaw
#2001

Finishing A Development Branch

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

CodingClaude Code
#2002

Brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

CodingClaude Code
#2003

Dispatching Parallel Agents

Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies

CodingClaude Code
#2004

Executing Plans

Use when you have a written implementation plan to execute in a separate session with review checkpoints

CodingClaude Code
#2006

Requesting Code Review

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

CodingClaude Code
#2007

Subagent Driven Development

Use when executing implementation plans with independent tasks in the current session

CodingClaude Code
#2008

Using Superpowers

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

CodingClaude Code
#2009

Verification Before Completion

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

CodingClaude Code
#2012

Systematic Debugging

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

CodingClaude Code
#2014

Using Git Worktrees

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

CodingClaude Code
#2015

Implement Spec

Implement a specification in code.

CodingClaude Code
#2016

Ask Matt

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

CodingClaude Code
#2018

Codebase Design

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 skill needs the deep-module vocabulary.

CodingClaude Code
#2019

Diagnosing Bugs

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

CodingClaude Code
#2021

Git Guardrails Claude Code

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 in Claude Code.

CodingClaude Code
#2024

Grilling

Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.

CodingClaude Code
#2033

Resolving Merge Conflicts

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

CodingClaude Code
#2035

Setup Matt Pocock Skills

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.

CodingClaude Code
#2036

Setup Pre Commit

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 formatting/typechecking/testing.

CodingClaude Code
#2038

Tdd

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

CodingClaude Code
#2055

Dsh Code Review

Use when reviewing a pull request in the deepseek-harness repo — orients the reviewer to this codebase's standards (AGENTS.md conventions, defensive patterns, ADRs, quality gates) and the review-specific checks that code alone can't show

CodingDeepSeek Harness
#2058

Dsh Find Simplifications

Use when working in the deepseek-harness repo to find non-obvious simplification candidates, write proposed Agent Notes or inline TODO/FIXME/XXX notes, audit or coalesce superseded Agent Notes, or fold worthwhile simplification ideas from another PR; especially for dead, duplicated, speculative, over-built, added-then-removed, or hand-rolled-where-a-dependency-exists surfaces.

CodingDeepSeek Harness
#2059

Dsh Merging Stacked Prs

Use when landing a stack of dependent GitHub PRs (A ← B ← C, where each bases on the one below) onto master, merging a PR whose base is another open PR's branch, or whenever a request mentions "stacked PRs", "PR stack", "dependent PRs", or merging several related PRs in sequence. Requires every same-repository dependency chain to use GitHub's official stacked-PR feature before landing so GitHub owns stack-wide rules, CI, ordering, retargeting, and merge state.

CodingDeepSeek Harness
#2067

Algorithmic Art

Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.

CodingClaude Code
#2069

Skill Creator

Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.

CodingClaude Code
#2077

Frontend Design

Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.

CodingClaude Code
#2078

Internal Comms

A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).

CodingClaude Code
#2148

Superself

Use when a project keeps its state in Superself (a `<!-- superself:begin` block in AGENTS.md or CLAUDE.md, or `self setup` resolves the directory to a registered project): read `self context` at session start, attach work to a work unit, report with evidence, and record confirmed decisions so the next session picks up where this one left off.

CodingClaude Code
#2149

Accessibility Compliance

Implement WCAG 2.2 compliant interfaces with mobile accessibility, inclusive design patterns, and assistive technology support. Use when auditing accessibility, implementing ARIA patterns, building for screen readers, or ensuring inclusive user experiences.

CodingClaude Code
#2150

Ai Debt Detector

Use after generating code, after accepting AI suggestions, or when reviewing AI-written modules. Also use when code works but feels brittle, when error handling seems thin, when orphaned resources or missing cleanup are suspected, or when the agent claims done but hidden debt may exist. Catches the specific failure patterns AI agents produce that humans would not.

CodingClaude Code
#2154

Api Design Principles

Master REST and GraphQL API design principles to build intuitive, scalable, and maintainable APIs that delight developers. Use when designing new APIs, reviewing API specifications, or establishing API design standards.

CodingClaude Code
#2156

Async Python Patterns

Master Python asyncio, concurrent programming, and async/await patterns for high-performance applications. Use when building async APIs, concurrent systems, or I/O-bound applications requiring non-blocking operations.

CodingClaude Code
#2163

Bazel Build Optimization

Optimize Bazel builds for large-scale monorepos. Use when configuring Bazel, implementing remote execution, or optimizing build performance for enterprise codebases.

CodingClaude Code
#2164

Before You Build

Pre-build product and feature risk review for founders, product managers, and AI-assisted builders. Use this skill when the user is about to build a landing page, MVP, SaaS product, internal tool, agent workflow, or major feature and needs to check demand, positioning, monetization, retention, trust, distribution, and adoption risk before implementation starts.

CodingClaude Code
#2165

Billing Automation

Build automated billing systems for recurring payments, invoicing, subscription lifecycle, and dunning management. Use when implementing subscription billing, automating invoicing, or managing recurring payment systems.

CodingClaude Code
#2166

Binary Analysis Patterns

Master binary analysis patterns including disassembly, decompilation, control flow analysis, and code pattern recognition. Use when analyzing executables, understanding compiled code, or performing static analysis on binaries.

CodingClaude Code
#2167

Block No Verify Hook

Configure a PreToolUse hook to prevent AI agents from skipping git pre-commit hooks with --no-verify and other bypass flags. Use when setting up Claude Code projects that enforce commit quality gates.

CodingClaude Code
#2170

Checkpoint Promotion

Gate fine-tuned checkpoints with drift budgets, paired comparison, and forgetting checks before promotion. Use after a training run produces a checkpoint, when deciding whether a tuned model ships, or when a promoted model needs re-gating against updated goldens.

CodingClaude Code
#2172

Competitive Landscape

Analyze competition, identify differentiation opportunities, and develop winning market positioning strategies using Porter's Five Forces, Blue Ocean Strategy, and positioning maps. Use this skill when evaluating competitors, assessing market positioning, identifying sustainable competitive advantages, or preparing competitive strategy analysis for a startup or investor pitch.

CodingClaude Code
#2175

Cqrs Implementation

Implement Command Query Responsibility Segregation for scalable architectures. Use when separating read and write models, optimizing query performance, or building event-sourced systems.

CodingClaude Code
#2176

Data Quality Frameworks

Implement data quality validation with Great Expectations, dbt tests, and data contracts. Use when building data quality pipelines, implementing validation rules, or establishing data contracts.

CodingClaude Code

Coding Skills FAQ

What is a coding agent skill?

It is a reusable instruction package that teaches an AI agent a focused coding & development workflow, often including commands, checks, and supporting resources.

Which coding skill should I try first?

Start with a narrow task you already understand. The current category leader is Github, but requirements and access scope matter more than rank alone.

Does a popular skill mean it is safe?

No. Popularity reflects adoption and interest, not a security guarantee. Read SKILL.md, review commands and dependencies, and test with minimal permissions.