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: Files & storage
4,278 results · page 42 of 143
- View details
validate-albumSkillFiles & storage
Validates album directory structure, file locations, and content integrity. Use before release or whenever the user wants to check an album's structural health.
Ready to connect★ 483
- View details
verify-sourcesSkillFiles & storage
Captures human source verification for tracks, timestamps it, and updates track files. Use when sources need human review before generation.
Ready to connect★ 483
- View details
active-genome-indexSkillFiles & storage
Register, parse, and digitize private genome source files into a local Active Genome Index and supporting evidence stores. Use when the session explicitly supplies a VCF/gVCF, BAM, genome.computer .genome/1.0 bundle, 23andMe raw genotype export, AncestryDNA raw genotype export, MyHeritage raw genoty
Ready to connect★ 482
- View details
dart-use-doc-examplesSkillFiles & storage
How to inject external code examples into Dartdoc using the {@example} directive, and how to filter those files using #hide, #region, and #endregion tags.
Ready to connect★ 479
- View details
debug-broken-uiSkillFiles & storage
Find out why something in a running web app does not work, when the console is empty and the code looks correct. Reads the click, the request, the store and the console together and returns the file:line to open. Use when a button does nothing, a form will not submit, data will not load, a page rend
Ready to connect★ 479
- View details
fix-what-i-pointed-atSkillFiles & storage
Pick up the bugs a human flagged by pointing at them in the running app, each arriving with the element, the note they typed, and the source file and line. Use when the user says they marked or flagged something, when starting a session on an app someone has been clicking through, when a designer or
Ready to connect★ 479
- View details
reticleSkillFiles & storage
Install, instrument and verify this running web app from the inside (DOM, network, routing, console and framework state) instead of screenshots or guessing. Drives one real flow end to end and returns a verdict with the file:line to fix. Use when the user asks to set up or install Reticle, when a us
Ready to connect★ 479
- View details
verify-ui-changeSkillFiles & storage
Check that a change to a web app actually works in the running app before calling it done. Drives the real page and returns a pass/fail verdict with the request that fired, the state that moved, and the file:line to fix. Use after editing a component, a form, a route, or an API call; when you have s
Ready to connect★ 479
- View details
bug-reporting-excellenceSkillFiles & storage
Write high-quality bug reports that get fixed quickly. Use when reporting bugs, training teams on bug reporting, or establishing bug report standards.
Ready to connect★ 475
- View details
coverage-drop-investigatorSkillFiles & storage
Use when test coverage has dropped and you need to find which changes caused it and what tests to add. Traces coverage regressions to specific commits and files.
Ready to connect★ 475
- View details
freeze-testsSkillFiles & storage
Use when refactoring production code and you want to ensure test files are not modified. Activate with /freeze-tests to block all edits to test files for safe refactoring.
Ready to connect★ 475
- View details
no-skipSkillFiles & storage
Use when you want to prevent .skip(), .only(), xit(), and xdescribe() from being committed to test files. Activate with /no-skip for session-scoped test skip prevention.
Ready to connect★ 475
- View details
qe-bug-reporting-excellenceSkillFiles & storage
Write high-quality bug reports that get fixed quickly. Use when reporting bugs, training teams on bug reporting, or establishing bug report standards.
Ready to connect★ 475
- View details
xp-practicesSkillFiles & storage
Apply XP practices including pair programming, ensemble programming, continuous integration, and sustainable pace. Use when implementing agile development practices, improving team collaboration, or adopting technical excellence practices.
Ready to connect★ 475
- View details
toxySkillFiles & storage
Use this skill whenever the user wants to extract text or data from documents using Toxy (the .NET text extraction library). Trigger when the user mentions reading, parsing, or extracting content from files like docx, xlsx, xls, pdf, csv, txt, epub, html, eml, vcf using C# or .NET. Also trigger when
Ready to connect★ 462
- View details
reviewing-changesSkillFiles & storage
Use when a review package asks you to review a plan step's change set (todo.startReview): you are the REVIEWER, not the author. How to judge an agent-written diff, file findings with add_review_comment, and settle with exactly one review_verdict.
Ready to connect★ 459
- View details
mastra-file-agentsSkillFiles & storage
Migrate Mastra code-based agents (agents built with new Agent(...) and registered in a Mastra({ agents }) map) to the file-based convention: one directory per agent under src/mastra/agents. Use when the user wants to convert or refactor Mastra agents to the per-directory convention, mentions Mastra
Ready to connect★ 458
- View details
coding-agentSkillFiles & storage
Delegate coding tasks to Codex, Claude Code, or Pi agents via background process. Use when: (1) building/creating new features or apps, (2) reviewing PRs (spawn in temp dir), (3) refactoring large codebases, (4) iterative coding that needs file exploration. NOT for: simple one-liner fixes (just edit
Ready to connect★ 456
- View details
commitsSkillFiles & storage
Use when picking a branch name, staging files, or writing a commit message — covers branch conventions, the project's Conventional Commits format with the scope vocabulary observed in history, and the documentation-update gate that fires before every commit (`docs/*`, `README.md`, godoc, Helm values
Ready to connect★ 456
- View details
ngx-page-object-modelSkillFiles & storage
MUST invoke before creating or editing any Angular component's tests (spec file). Enforces the Page Object Model pattern – tests drive components through the rendered DOM (their public contract) rather than reaching into component internals.
Ready to connect★ 450
- View details
architecture-cleanupSkillFiles & storage
Find and execute bounded architecture cleanup across public exports, package ownership, Convex bundle graphs, plugins, CLI/scaffolds, generated files, docs, and agent navigation.
Ready to connect★ 447
- View details
changeset-resolveSkillFiles & storage
Repair an unreleased `.changeset/*.md` file so it matches the real branch delta against `main`. Use when a changeset was edited iteratively during debugging, when bullets may reflect turn-by-turn history instead of `main...HEAD`, when "removed/gone/renamed" claims need proof, or when you need to aud
Ready to connect★ 447
- View details
component-colocationSkillFiles & storage
Use after migrating/refactoring features (especially tables/data grids) when reviewing component structure - enforces merging over-split components, colocating files where used, removing unused code, following vertical slice architecture. Prevents premature abstraction and over-engineering.
Ready to connect★ 447
- View details
jotai-xSkillFiles & storage
Use when working with Jotai X stores (createAtomStore), accessing state in components or callbacks, persisting state to cookies or localStorage
Ready to connect★ 447
- View details
foreman-to-issuesSkillFiles & storage
Break an approved PRD into small, dependency-ordered, vertically-sliced implementation issues written as local files in the Foreman feature directory. Each issue ships a runnable acceptance check and a declared file footprint. No GitHub, no live quizzing of the user — emits files matching Foreman's
Ready to connect★ 443
- View details
foreman-to-prdSkillFiles & storage
PRD template and authoring rules for Foreman. Synthesizes a PRD from the approved plan and the grilled decisions and writes it as a local file in the Foreman feature directory. Does not interview the user and does not publish to any external issue tracker.
Ready to connect★ 443
- View details
rebrandSkillFiles & storage
Apply a downstream brand to a PlatformPlatform fork. Edits one config file, drops in eight supplied logo assets, renames the solution and CLI to the new brand, and rotates UserSecretsId across every csproj. Skips all other source files. Use once per downstream fork after cloning, or to re-flip a bra
Ready to connect★ 441
- View details
013-agile-featureSkillFiles & storage
Guides the creation of detailed agile feature documentation from an existing epic. Use when the user wants to split an epic into feature files, derive features with scope and acceptance criteria, or plan feature documentation for stakeholders or engineering. This should trigger for requests such as
Ready to connect★ 439
- View details
110-java-maven-best-practicesSkillFiles & storage
Use when you need to review, improve, or troubleshoot a Maven pom.xml file — including dependency management with BOMs, plugin configuration, version centralization, multi-module project structure, build profiles, or any situation where you want to align your Maven setup with industry best practices
Ready to connect★ 439
- View details
113-java-maven-documentationSkillFiles & storage
Use when you need to create a DEVELOPER.md file for a Maven project — combining a fixed base template with dynamic sections derived from allowlisted Maven POM structure, including a Plugin Goals Reference, Maven Profiles table, and Submodules table for multi-module projects. This should trigger for
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.
52,524 of the 52,958 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.