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 163 of 566
- View details
kitcnSkillDev tools
Use for Convex/kitcn setup and feature work: cRPC, ORM, auth, React.
Ready to connect★ 447
- View details
nextjsSkillDev tools
Next.js routing with typed routes, PageProps, LayoutProps helpers, and nuqs for URL state. Use for pages, layouts, navigation, and query parameters.
Ready to connect★ 447
- View details
react-querySkillDev tools
TanStack Query ownership for kitcn cRPC queries, mutations, live Convex subscriptions, RSC preloading, cache keys, and bounded invalidation.
Ready to connect★ 447
- View details
sync-convex-authSkillDev tools
Sync `zbeyens/convex-better-auth` with upstream, then sync kitcn against upstream `convex-better-auth` changes. Use when asked to run `sync-convex-auth`, compare the fork with upstream, fast-forward or PR the fork update when safe, audit commits the fork was behind on, classify relevance to kitcn au
Ready to connect★ 447
- View details
sync-visionSkillDev tools
Incrementally audit kitcn doctrine drift since the recorded baseline, classify it, update VISION.md and local planning owners, then advance the baseline only after proof.
Ready to connect★ 447
- View details
to-milestoneSkillDev tools
Turn kitcn vision, research, and source evidence into a pivotable local milestone map and ranked PRD ladder.
Ready to connect★ 447
- View details
visionSkillDev tools
Route durable product, architecture, API, and DX decisions through the repository vision. Use before planning, prioritizing, or changing doctrine.
Ready to connect★ 447
- View details
api-callerSkillDev tools
Call any REST API dynamically. Make GET, POST, PUT, DELETE requests to any endpoint with custom headers and JSON body.
Ready to connect★ 435
- View details
foreman-tddSkillDev tools
Stack-agnostic test-driven development loop for a single Foreman issue.
Ready to connect★ 443
- View details
check-prsSkillDev tools
Scan open PRs for stale review requests and report which need action
Ready to connect★ 442
- View details
create-planSkillDev tools
Create a test-first implementation plan from a spec issue, analysis, or concept
Ready to connect★ 442
- View details
follow-up-reviewSkillDev tools
Re-review an incoming PR after the author responded — scoped to the delta since the last review, verifies prior requested changes, posts after confirmation
Ready to connect★ 442
- View details
- View details
handle-prSkillDev tools
Review an incoming PR end-to-end — strict local review, drafted GitHub review, post after confirmation
Ready to connect★ 442
- View details
health-auditSkillDev tools
Internal codebase health audit — checks docs, skills, duplication, dead code, coding-guidelines, correctness, and tests for drift and real defects. Runs all areas by default, or one named area. Writes per-area reports to .ai/health-audit-<date>/.
Ready to connect★ 442
- View details
- View details
scan-repoSkillDev tools
Weekly repo activity scan — new discussions, issues, and PRs, ordered by effort into an action list
Ready to connect★ 442
- View details
ship-issueSkillDev tools
Fully solve a small issue end-to-end — resolve, publish the PR, run two Copilot review rounds, address them, and merge when confident. Escalates to the user on anything uncertain.
Ready to connect★ 442
- View details
sync-repo-statusSkillDev tools
Regenerate REPO_STATUS.md — full snapshot of open PRs, local branches, issues, and discussions with merge-readiness and triage assessment
Ready to connect★ 442
- View details
takeover-prSkillDev tools
Take over a stale PR — supersede it with requested changes applied, crediting the original author
Ready to connect★ 442
- View details
validate-testsSkillDev tools
Codex-gate the test plan in an implementation plan before implementation starts
Ready to connect★ 442
- View details
aspire-restartSkillDev tools
Start or restart the .NET Aspire AppHost via the developer CLI. Always use this, never the developer CLI's `run` command, `aspire run`, or `aspire restart`.
Ready to connect★ 441
- View details
- View details
fix-e2e-testsSkillDev tools
Systematically fix all failing E2E tests using a phased diagnostic approach. Classifies tests as passing, flaky, or permanently failing, then fixes them one by one with progressive scope expansion.
Ready to connect★ 441
- View details
formatSkillDev tools
Auto-format code via the developer CLI - backend (.NET via JetBrains cleanupcode), frontend (oxfmt + oxlint --fix), and the developer CLI itself.
Ready to connect★ 441
- View details
pull-platformplatform-changesSkillDev tools
Pull unmerged PlatformPlatform pull requests into a downstream project by cherry-picking each one onto the platformplatform-updates branch. Renames commits to "PlatformPlatform PR N - title" per the existing convention. Drives a ralph-loop that validates each commit (build, test, format, lint, optio
Ready to connect★ 441
- View details
rebuild-branchSkillDev tools
Rebuild a stale branch by cherry-picking each commit onto a fresh branch off main, using a ralph-loop to validate each commit (build, test, format, lint, optional e2e) before moving on. Use when a branch has gone stale, has merge conflicts with main, or needs to be split out of a long-lived feature
Ready to connect★ 441
- View details
ultra-reviewSkillDev tools
Trigger only on explicit "ultra review" or "ultra-review".
Ready to connect★ 441
- View details
upgrade-packagesSkillDev tools
Upgrade all backend (.NET/NuGet), frontend (npm), and GitHub Actions dependencies to their latest versions, in that fixed order. Drives the developer CLI's update-packages command, parses its quiet dry-run output to separate trivial bumps from majors, ships trivial bumps as one bulk commit per side,
Ready to connect★ 441
- View details
014-agile-user-storySkillDev tools
Guides the creation of agile user stories. Use when the user wants to create a user story. This should trigger for requests such as Create a user story; Write a user story; I need to write a user story; Split feature requirements into user stories. Part of Plinth Toolkit
Ready to connect★ 439
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.