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,833 results · page 276 of 562
- View details
book.update_contentSkillDev tools
Update the content of a book given the changes in the corresponding source content
Ready to connect★ 145
- View details
ca-add-depSkillDev tools
Vet a new or changed third-party dependency for license, provenance, and supply-chain risk before any install runs.
Ready to connect★ 145
- View details
ca-adrSkillDev tools
Author a numbered, dated, user-attributed Architecture Decision Record under .codearbiter/decisions/.
Ready to connect★ 145
- View details
ca-adr-statusSkillDev tools
Report the health of Architecture Decision Records — aged, unchallenged, supersession candidates, unresolved CONFIRM-NN. Read-only.
Ready to connect★ 145
- View details
ca-auditSkillDev tools
Assemble the governance record for a range — commits, overrides, ADRs, sprint auto-decisions, open questions, checkpoint findings — into one dated audit packet. Read-only.
Ready to connect★ 145
- View details
ca-btwSkillDev tools
Lightweight Q&A about the project — answer from context and return, no routing, no state change.
Ready to connect★ 145
- View details
ca-checkpointSkillDev tools
Periodic multi-reviewer sweep of the whole codebase — surfaces a triaged checkpoint report.
Ready to connect★ 145
- View details
ca-choreSkillDev tools
Sanctioned lane for non-behavioral work — docs-only edits, dependency bumps, reverts. Type-scaled gates; no TDD demanded of prose.
Ready to connect★ 145
- View details
ca-cleanupSkillDev tools
Finish an already-merged branch — classify the leftover artifacts, return to a fast-forwarded default checkout, and delete the merged local branch. Every discard confirmed per item; containment proven, never assumed.
Ready to connect★ 145
- View details
ca-commandsSkillDev tools
Show the codeArbiter command catalog — the public command list and what each routes to.
Ready to connect★ 145
- View details
ca-commitSkillDev tools
Run the full commit gate — the only sanctioned path to a git commit.
Ready to connect★ 145
- View details
ca-conflictSkillDev tools
Stop everything and surface a rule conflict — persona vs. docs vs. code. Present both sides and the conflict-hierarchy level; the user resolves. No silent reconciliation.
Ready to connect★ 145
- View details
ca-context-checkSkillDev tools
Optional manual drift audit — report stale provenance-tracked docs, then per stale doc offer re-scout, re-baseline, or defer. Not the daily loop; commit-gate auto-heal owns routine maintenance.
Ready to connect★ 145
- View details
ca-create-contextSkillDev tools
Brownfield back-fill — scout an existing codebase and populate .codearbiter/, then lock it initialized.
Ready to connect★ 145
- View details
ca-debugSkillDev tools
Investigate-then-decide root-cause analysis for a defect whose cause is unknown. No code changes — exits to /ca-fix, /ca-adr, or a no-action close.
Ready to connect★ 145
- View details
ca-decomposeSkillDev tools
Greenfield decomposition interview — a layered interview that populates .codearbiter/ and locks it initialized.
Ready to connect★ 145
- View details
ca-doctorSkillDev tools
Verify the active host install, package, command ownership, enforcement, wrapper self-test, and active-dispatch coverage gap. Read-only.
Ready to connect★ 145
- View details
ca-featureSkillDev tools
Start a feature: brainstorm a spec, get it approved, then drive it test-first through the pipeline. The one entry to implementation.
Ready to connect★ 145
- View details
ca-fixSkillDev tools
Fix a confirmed bug: a failing regression test first, then a minimal fix, then the rest of the tdd gates.
Ready to connect★ 145
- View details
ca-initSkillDev tools
Opt this repo into codeArbiter — scaffold the root-level .codearbiter/ state store.
Ready to connect★ 145
- View details
ca-new-skillSkillDev tools
Author a new codeArbiter skill: prove the gap is real, get the spec approved, then write it.
Ready to connect★ 145
- View details
ca-overrideSkillDev tools
Sanctioned, logged bypass of a gate or hard rule — one audit line, then proceed.
Ready to connect★ 145
- View details
ca-prSkillDev tools
Open a pull request the only sanctioned way — clear every BLOCK-level review finding, then stage the PR. Never a direct write to the default branch.
Ready to connect★ 145
- View details
ca-previewSkillDev tools
Zero-onboarding, read-only dry-run of the reviewer fleet against the current uncommitted diff. Predicts reviewers, runs the state-free secret scan, writes nothing.
Ready to connect★ 145
- View details
ca-pruneSkillDev tools
Trim transcript clutter to extend session lifetime — analyze, prune a copy, or toggle the after-each-turn service. Dry-run by default; gains land at resume/compaction, not the current turn.
Ready to connect★ 145
- View details
ca-reconcileSkillDev tools
SMARTS arbitration — reconcile architectural artifacts against the scaffold and prior decisions; every variance resolved by an explicit, user-attributed choice.
Ready to connect★ 145
- View details
ca-refactorSkillDev tools
Restructure code with behavioral parity proven through unmodified pre-existing tests, then refactor. No behavior change.
Ready to connect★ 145
- View details
ca-reviewSkillDev tools
Review a diff with the reviewer fleet, funneled to one triaged verdict. Targets the current working diff, a path, or an inbound GitHub PR.
Ready to connect★ 145
- View details
ca-sprintSkillDev tools
Autonomous sprint — one interactive spec gate, then plan-to-PR execution with every auto-decision SMARTS-scored and logged. Hard gates remain true stops.
Ready to connect★ 145
- View details
ca-standupSkillDev tools
Daily repo hygiene — review the day's repo state, then perform the cleanups under per-action confirmation. Fast-forward only, never destructive without a yes.
Ready to connect★ 145
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,585 of the 54,017 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.