Skills.
Give your AI a better way to work.
A skill is a set of written instructions that teaches an AI how to do one job the way it should be done: review a pull request, plan a migration, write the release notes.
Install one here and it travels with your account into Claude, Claude Code, Cursor and every other client you sign in with.
Category: Dev tools
17,418 results · page 120 of 581
- View details
evaluator-calibrationSkillDev tools
Calibrate a reviewer persona with few-shot rubric examples so skepticism stays consistent and doesn't drift lenient over long runs.
Ready to connect★ 755
- View details
feature-list-jsonSkillDev tools
Enumerate every end-to-end feature as strict JSON entries with passes:false, editable-passes-only discipline, and priority order. The ledger fresh-context sessions read to know what's done, what's next, and what they're forbidden to touch.
Ready to connect★ 755
- View details
flaky-hunterSkillDev tools
Diagnose and fix tests that pass sometimes and fail other times. Use when CI is red intermittently.
Ready to connect★ 755
- View details
harness-strippingSkillDev tools
Systematically remove one harness component at a time and measure impact, killing scaffolding that no longer earns its complexity.
Ready to connect★ 755
- View details
init-script-contractSkillDev tools
Author idempotent init.sh under 120s plus sibling test.sh, stop.sh, reset.sh, serve.sh with fixed names the harness relies on.
Ready to connect★ 755
- View details
input-validationSkillDev tools
Validate and constrain untrusted input at the boundary. Use on any handler that accepts external data.
Ready to connect★ 755
- View details
kill-dead-codeSkillDev tools
Find and remove unreachable/unused code safely. Use during cleanup or before a refactor.
Ready to connect★ 755
- View details
pr-from-diffSkillDev tools
Write a PR description a reviewer can approve fast. Use when opening any pull request.
Ready to connect★ 755
- View details
read-the-traceSkillDev tools
Extract the actual cause from a stack trace instead of pattern-matching the error type. Use on any crash or exception.
Ready to connect★ 755
- View details
readme-auditSkillDev tools
Check whether a README actually lets a stranger run the project. Use on any repo's README before publishing.
Ready to connect★ 755
- View details
rebase-safelySkillDev tools
Rebase, squash, or rewrite history without losing work or breaking shared branches. Use before any history rewrite.
Ready to connect★ 755
- View details
reduce-nestingSkillDev tools
Flatten deeply nested conditionals into readable, early-return code. Use on any function with 3+ levels of indentation.
Ready to connect★ 755
- View details
revert-surgicalSkillDev tools
Undo a bad change without nuking unrelated work. Use when a specific commit or change broke something.
Ready to connect★ 755
- View details
sprint-contractSkillDev tools
Negotiate a pre-code contract between generator and evaluator personas that defines what "done" means before any code is written. Turns fuzzy specs into a testable target the evaluator can hold the generator to.
Ready to connect★ 755
- View details
using-loopkitSkillDev tools
Use when starting any conversation in a loopkit-enabled project - establishes how to find and use loopkit's 49 skills, requiring skill invocation before ANY response including clarifying questions.
Ready to connect★ 755
- View details
write-failing-test-firstSkillDev tools
Before fixing any bug, write a test that reproduces it and watch it fail. Use for every bug fix.
Ready to connect★ 755
- View details
ad-auditSkillDev tools
Run this skill when the user explicitly invokes `/ad-audit` or names it ("run ad-audit", "audit against the rules"), or asks for the maximum quality gate before work reaches the team ("adversarial audit", "rules audit", "maximum gate", "verify before I post", "exhaustive review"). Heavier and more e
Ready to connect★ 749
- View details
ad-deepenSkillDev tools
Surface deepening opportunities in the codebase using the Ousterhout/Feathers vocabulary from WORKFLOW §8 (Module / Interface / Depth / Seam / Adapter / Leverage / Locality). Three-phase process — explore organically, present numbered candidates with deletion-test framing, grilling loop on the chose
Ready to connect★ 749
- View details
ad-diagnoseSkillDev tools
Disciplined diagnosis loop for hard bugs and performance regressions per WORKFLOW §15. Five phases — build a feedback loop, reproduce, hypothesise (3-5 ranked falsifiable), instrument, fix + regression-test. The feedback loop is the skill; everything else is mechanical. Triggers on "diagnose this",
Ready to connect★ 749
- View details
ad-domainSkillDev tools
Lazily create or update `CONTEXT.md` (Layer 2 — ubiquitous language per Evans 2003) at the repo root, or `CONTEXT-MAP.md` plus per-context `CONTEXT.md` for multi-context repos. Captures canonical project-specific nouns, the aliases to avoid, the relationships between them, and resolved ambiguities.
Ready to connect★ 749
- View details
ad-grill-meSkillDev tools
Interview-before-research grilling session that challenges a fuzzy ask against the existing codebase, sharpens vocabulary against `CONTEXT.md`, and resolves the decision tree branch by branch. One question at a time, codebase-first when an answer is in code, with each question carrying a recommended
Ready to connect★ 749
- View details
ad-groundSkillDev tools
Four-source pre-implementation research — official docs, validated implementation references (open-source repos, Stack Overflow / forum answers, blog posts, gists), in-repo patterns, and git history — then synthesize a happy path and gate any deviation with an irrefutable justification before code i
Ready to connect★ 749
- View details
ad-level-upSkillDev tools
Run this skill when the user explicitly invokes `/ad-level-up` or names it, or asks to evolve the project's rule-set — "add a convention", "update the rules", "new rule", "merge these rules", "we keep hitting X, make it a rule", "retire this rule" — or hands over a rule gap surfaced by `ad-audit`. C
Ready to connect★ 749
- View details
ad-nextSkillDev tools
Survey the project's state across the six-layer artifact stack and recommend prioritized next actions, modeled on `flutter doctor`. Use when the user asks "what's next", "next step", "where am I", "project status", "doctor", "what should I do", "audit my workflow". Read-only; complements `ad-drift`
Ready to connect★ 749
- View details
ad-prSkillDev tools
Open a GitHub pull request with a uniform body shape. Four phases — preflight (`gh` auth + branch pushed), scope assembly (commits + diff vs base), draft body (Summary / Test plan / Links), open + report URL. Title format = Conventional Commits, type inferred from the dominant commit type in the ran
Ready to connect★ 749
- View details
ad-spikeSkillDev tools
Scaffold a staged spike with golden fixtures per WORKFLOW.md §14, for cases where the spec is clear but the technique is uncertain across multiple plausible approaches. Four stages — discovery, golden fixture, pipeline with gates, two-layer evaluation. Use when the unknown is *how*, not *what*. Trig
Ready to connect★ 749
- View details
comfyui-coreSkillDev tools
Core ComfyUI knowledge covering workflow format, node types, pipeline patterns, and MCP tool usage
Ready to connect★ 744
- View details
comfyui-frontend-extensionsSkillDev tools
Authoring ComfyUI v2 frontend extensions with @comfyorg/extension-api, covering defineNode/defineExtension/defineWidget, shell UI (sidebar tabs, commands, hotkeys), typed events, and handles. Use when writing or editing ComfyUI web-UI extension code (custom node JS, sidebar panels, widgets).
Ready to connect★ 744
- View details
comfyui-node-registrySkillDev tools
Authoring & publishing ComfyUI custom nodes to the Comfy Registry, covering node structure, pyproject.toml spec, comfy-cli publishing, and CI
Ready to connect★ 744
- View details
flux-txt2imgSkillDev tools
Build Flux txt2img workflows with Flux.1 Dev (SRPO), Flux 2 Klein 9B, Turbo LoRAs, FluxGuidance, and DualCLIPLoader patterns
Ready to connect★ 744
What is a skill?
A skill is plain text, usually a SKILL.md file and the scripts it refers to, written for an AI rather than for a person. It carries the steps, the house rules and the examples a good answer needs, so you stop pasting the same briefing into every new chat.
55,111 of the 55,543 skills listed here can be served through ahel today, and they come from public repositories. Each one has its own page with the instructions themselves on it, so you can read what a skill will tell your AI to do before you install it.
Install one and every AI you use gets it
Installing a skill adds it to your gateway and turns it on in the same step. Claude Code surfaces it as a slash command; any client can read the full instructions with the skill_read tool.
Nothing is copied into a project folder. The instructions are served from your account, so the same skill is there in every AI you connect, and turning it off removes it from all of them at once.