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,902 results · page 448 of 564
- View details
team-onboardingSkillDev tools
Use when a new member joins the team and their competencies are being assessed.
Ready to connect★ 50
- View details
tier3-probesSkillDev tools
Use when validating the viability of Tier 3 tools before adopting them in the workspace.
Ready to connect★ 50
- View details
understand-anythingSkillDev tools
Use when you need to analyze a codebase with Understand-Anything to generate structural and domain knowledge graphs.
Ready to connect★ 50
- View details
verification-latticeSkillDev tools
Use when multi-layer verification beyond standard code review is needed.
Ready to connect★ 50
- View details
weekly-reportSkillDev tools
Usar cuando se genera el informe semanal de estado del proyecto.
Ready to connect★ 50
- View details
- View details
adversarial-test-sweepSkillDev tools
Run a bounded adversarial sweep of an existing test suite. Use to harden a suite or subsystem against malformed inputs, boundaries, invalid state, races, dependency/resource failures, weak or redundant tests, flakes, and missing durable regressions. Skip ordinary test additions, load, chaos, and pen
Ready to connect
- View details
ai-development-guideSkillDev tools
Applies root-cause analysis, impact inspection, and completeness checks without expanding approved scope. Use when fixing bugs, refactoring, reviewing quality, or resolving unexpected implementation evidence.
Ready to connect
- View details
assets-ext-regressionSkillDev tools
Run CIP-26 and CIP-68 wire-shape regression tests for the assets-ext extension against the cf-token-metadata-registry V2 API on mainnet. Use when a user wants to verify yaci-store's API output is byte-equivalent to CF, after a code change to assets-ext, or when investigating reported metadata diverg
Ready to connect
- View details
better-chezmoiSkillDev tools
Use for safe chezmoi setup and migration, daily dotfile sync, templates, secrets, scripts, drift/recovery, or official-doc research.
Ready to connect
- View details
bug-fixingSkillDev tools
Fix bugs with a test-first workflow. Use when the user reports a bug, asks to fix a defect, or describes unexpected behavior. Triggers on: bug, fix, defect, broken, regression, not working, unexpected behavior.
Ready to connect
- View details
changelog-helperSkillDev tools
Write changelog copy from merged pull requests and issue metadata.
Ready to connect
- View details
client-report-from-commitsSkillDev tools
Turn git commits and diffs since an exact date into a copy-pastable, non-technical client report grouped by feature. Use for client updates, weekly progress, stakeholder recaps, or high-level git-history summaries. Do NOT use when the date is ambiguous.
Ready to connect
- View details
coding-rulesSkillDev tools
Applies repository-aware rules for maintainable implementation, contracts, errors, and refactoring. Use when writing or modifying code.
Ready to connect
- View details
- View details
existing-helperSkillDev tools
Explain this fixture repository's established installable-skill layout. Use only for repository-layout orientation.
Ready to connect
- View details
fable-validate-fableplanSkillDev tools
Use when the user asks to validate a GitHub issue with Fable 5.1 and always plan it with Fable 5.1, stopping once the plan is posted — "fable-validate-fableplan", "fable validate and fable plan #N", "validate and plan #N with fable, don't build it". Runs fable-validate, auto-applies its update-issue
Ready to connect
- View details
fable-validate-fableplan-loopSkillDev tools
Use when the user asks to validate a GitHub issue with Fable 5.1, always plan it with Fable 5.1, and autonomously drive it to a reviewed PR in one shot — "fable-validate-fableplan-loop", "fable validate, fable plan, and work on #N", "fully automate #N with fable validation and an unconditional fable
Ready to connect
- View details
fable-validate-loopSkillDev tools
Use when the user asks to validate a GitHub issue with Fable 5.1 and then autonomously drive it to a reviewed PR in one shot — "fable-validate-loop", "fable validate and work on #N", "fully automate issue #N with fable". Runs fable-validate, auto-applies its update-issue edits when the verdict calls
Ready to connect
- View details
fableplan-loopSkillDev tools
Use when the user wants a GitHub issue planned by Fable 5.1 and then autonomously driven to a reviewed PR in one shot, without validation — "fableplan-loop", "fableplan #N and loop until approved", "plan #N with fable then drive it to a reviewed PR". Runs the fableplan planning phase (Fable 5.1 prod
Ready to connect
- View details
fableplan-work-on-issueSkillDev tools
Use when the user wants a GitHub issue planned by Fable 5.1 and then implemented in one shot, without validation or a review loop — "fableplan-work-on-issue", "fableplan and work on #N", "plan #N with fable then implement it". Runs the fableplan planning phase (Fable 5.1 produces and posts an implem
Ready to connect
- View details
fix-pr-reviewSkillDev tools
Use when the user asks to fix, address, or respond to a PR review — "fix the PR review", "/fix-pr-review". Optional PR number/URL (defaults to the current branch's PR); optional `codex` argument selects Codex.
Ready to connect
- View details
fix-pr-review-loopSkillDev tools
Use when the user asks to fix a PR review and drive it to approval autonomously — "fix the PR review and loop until approved", "fix-pr-review-loop", "keep addressing review comments until this PR is approved". Takes an optional PR number/URL (defaults to the current branch's PR). Repeatedly calls fi
Ready to connect
- View details
generate-api-clientSkillDev tools
Regenerate the frontend TypeScript API client from backend OpenAPI spec. Use after changing backend controller signatures or related data types. Triggers on: generateTypeScript, API regeneration, controller signature changed, OpenAPI lint failure, generated API code.
Ready to connect
- View details
github-issue-formatSkillDev tools
Required format for creating or editing any GitHub issue — [C<score>] title convention, complexity rationale line, complete-body rule, mandatory Plain simple English section, attribution footer. Load BEFORE creating or editing a GitHub issue.
Ready to connect
- View details
heuristic-to-deterministicSkillDev tools
Convert repeated heuristics into deterministic behavior: validator scripts, normalizer tools, generators, fixtures, manifests, CI jobs, and hook-ready checks. Use to codify learnings and prevent future guessing. Do NOT use for pure brainstorming or one-off edits.
Ready to connect
- View details
integration-e2e-testingSkillDev tools
Applies integration and E2E implementation, mock-boundary, and review rules. Use when: writing integration or E2E tests or reviewing their quality.
Ready to connect
- View details
linkedin-speakSkillDev tools
Parodies text as LinkedIn-speak or reverses corporate-influencer fluff into blunt English. Use for LinkedIn-speak and corporate-cringe rewrites; skip real translation and serious editing.
Ready to connect
- View details
linux-phone-portingSkillDev tools
Use for every hardware bring-up or debug session that ports mainline Linux to a phone (Android handset). Requires an already-unlocked bootloader; locked devices are out of scope.
Ready to connect
- View details
maintainable-codeSkillDev tools
Guide maintainable code with clear names, decomposition, safe defaults, side-effect guardrails, compatibility, comments, and quality gates. Use for production code, refactors, reviews, plans, CI, scripts, config, tests, or technical debt. Skip disposable work.
Ready to connect
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,788 of the 54,220 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.