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
16,980 results · page 146 of 566
- View details
subduction-policySkillDev tools
Reference for `SubductionPolicy` (the four hooks `authorizeConnect`, `authorizeFetch`, `authorizePut`, `filterAuthorizedFetch` passed via `Subduction.hydrate(..., policy)` or `new Repo({ subductionPolicy })`). Use when designing client-side access control over Subduction-replicated data, choosing wh
Ready to connect★ 520
- View details
trunk-quarantineSkillDev tools
Use Trunk's CI Autopilot MCP server to investigate a failing CI run, find/diagnose a flaky test, and quarantine it. Use when a CI run is red and might be flaky, or when asked to quarantine/investigate a specific test.
Ready to connect★ 520
- View details
analyzing-ci-flakinessSkillDev tools
Analyzes recent CI failures on pull requests to identify flaky tests, using retry outcomes (failed attempt → green re-run) and cross-PR recurrence as evidence, and maintains a local longitudinal ledger so flakiness can be tracked over time. TRIGGER when: the user wants to find flaky tests, correlate
Ready to connect★ 518
- View details
creating-changelog-entriesSkillDev tools
Use when you've fixed a bug, added a feature, or made any user-facing change in a project that uses Towncrier and need to record it for the changelog — before committing or opening a PR, or whenever asked to add a changelog entry, towncrier fragment, or news fragment.
Ready to connect★ 518
- View details
grilling-ideasSkillDev tools
Stress-tests a fuzzy or vague feature idea before any PRD, spec, or ticket is written. TRIGGER when: the user has a fuzzy feature idea — one or two paragraphs, vague on users / scope / success — and wants to harden it, or says "grill / stress-test / pressure-test this idea." DO NOT TRIGGER when: the
Ready to connect★ 518
- View details
migrate-feature-pageSkillDev tools
Migrate Infrahub docs feature pages from the legacy topic+guide pair into a cleaner structure (single merged page, hub+spokes, or tutorial extraction). Supports both single-feature migrations (one feature like Profiles or Webhooks) and section-wide migrations (a whole section like Branches & Change
Ready to connect★ 518
- View details
opsmill-dev-analyzing-bugsSkillDev tools
Performs root-cause analysis of a bug — from a GitHub issue, an issue URL, or a free-text description — before any reproduction or fix is written. TRIGGER when: triaging or diagnosing a bug, investigating why something misbehaves, an issue number/URL handed over for analysis, needing the root cause
Ready to connect★ 518
- View details
opsmill-dev-fixing-bugsSkillDev tools
Implements and validates the fix for a bug once a failing reproduction test exists. TRIGGER when: a bug has a failing reproduction test and you are ready to make it pass, implementing the root-cause fix, the final step of the bug-fixing pipeline. DO NOT TRIGGER when: no reproduction test exists yet
Ready to connect★ 518
- View details
opsmill-dev-test-driving-bugsSkillDev tools
Writes a single failing test that reproduces a bug after its root-cause analysis is complete, before any fix is written. TRIGGER when: a bug has a completed root-cause analysis and you need the failing reproduction test, writing a test that proves a bug exists, the second step of the bug-fixing pipe
Ready to connect★ 518
- View details
speckit-critique-runSkillDev tools
Perform a dual-lens critical review of the specification and plan from
Ready to connect★ 518
- View details
speckit-opsmill-extractSkillDev tools
Extract knowledge, guidelines, and ADRs from one or more completed spec
Ready to connect★ 518
- View details
speckit-opsmill-implementSkillDev tools
Run the speckit implementation phase chunk-by-chunk in clean-context
Ready to connect★ 518
- View details
speckit-opsmill-prepSkillDev tools
Run the speckit preparation phases end-to-end — specify, plan, critique,
Ready to connect★ 518
- View details
speckit-opsmill-retrospectSkillDev tools
Run a session retrospective that surfaces context-management gaps and
Ready to connect★ 518
- View details
speckit-review-codeSkillDev tools
General code quality review — project guideline compliance, bug detection,
Ready to connect★ 518
- View details
speckit-review-errorsSkillDev tools
Error handling review — silent failure detection, catch block analysis,
Ready to connect★ 518
- View details
speckit-review-simplifySkillDev tools
Code simplification suggestions — clarity, unnecessary complexity, redundant
Ready to connect★ 518
- View details
speckit-review-testsSkillDev tools
Test coverage quality analysis — behavioral coverage, critical gap identification,
Ready to connect★ 518
- View details
figmirrorSkillDev tools
FigMirror mirrors the visual style of a top-conference paper figure (NeurIPS / ICML / ICLR / Nature family) onto the user's own data. Takes dirty data plus a reference figure screenshot (cropped or uncropped), preprocesses the reference crop, runs a Drawer/Reviewer loop, and outputs a camera-ready P
Ready to connect★ 510
- View details
- View details
- View details
- View details
- View details
- View details
- View details
- View details
- View details
- View details
- View details
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.
53,462 of the 53,895 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.