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
17,188 results · page 165 of 573
- View details
guidance-trackerSkillDev tools
Track management guidance accuracy over time for a given company
Ready to connect★ 487
- View details
industrySkillDev tools
Cross-company industry comparison across multiple tickers
Ready to connect★ 487
- View details
- View details
precedent-transactionsSkillDev tools
Precedent M&A transactions analysis with deal multiples and acquisition history
Ready to connect★ 487
- View details
- View details
working-capitalSkillDev tools
Cash conversion cycle, earnings quality, and working capital deep-dive
Ready to connect★ 487
- View details
defineSkillDev tools
Use when a new feature request, bug report, or work request needs requirements defined before implementation
Ready to connect★ 484
- View details
refactorSkillDev tools
Use when code quality needs improvement after implementation, without changing behavior
Ready to connect★ 484
- View details
asking-user-questionsSkillDev tools
Use when composing an ask_user_question round inside a workflow, or when a workflow skill names it at a question step. Shared norms for the tool — not a workflow, nothing to execute.
Ready to connect★ 483
- View details
choosing-a-workflowSkillDev tools
Use at the start of new project onboarding, PR lifecycle work including PR checks, or changes that require choosing product scope, user-visible behavior, or architecture. Not for continuing work already routed to a workflow, non-PR questions, checks, explanations, or localized fully specified work.
Ready to connect★ 483
- View details
importing-a-codebaseSkillDev tools
Use when asked to create the initial spec graph for an existing codebase that has source code but no specs. Normally reached via setting-up-a-project.
Ready to connect★ 483
- View details
setting-up-a-projectSkillDev tools
Use when asked to set up, onboard, initialize, or spec a project with no spec graph, or when invoked by the app's Set-up-project card. Not for ordinary work in an already-specced project.
Ready to connect★ 483
- View details
spec-graphSkillDev tools
Use when locating, reading, creating, updating, or validating project specs, or when work is governed by or may alter a documented boundary, contract, invariant, behavior, or architecture decision.
Ready to connect★ 483
- View details
starting-a-new-projectSkillDev tools
Use when the workspace is empty, has no code, and the user brings a raw project idea. Normally reached via setting-up-a-project; not for an existing project.
Ready to connect★ 483
- View details
writing-specsSkillDev tools
Use when a workflow step drafts or revises a spec artifact — a goal-and-requirements, an architecture, or a module SPEC — or when a workflow skill names it at such a step. The shared quality bar for specs — not a workflow, nothing to execute.
Ready to connect★ 483
- View details
writing-workflow-skillsSkillDev tools
Use when adding a new workflow skill to pi-thinkrail-workflow, changing an existing workflow skill's role, trigger, handoff, or structure, or checking a workflow skill against the workflow system's rules. Not for authoring general-purpose skills outside this package.
Ready to connect★ 483
- View details
initSkillDev tools
Explicit V3 bootstrap for repositories that do not already have valid llmdoc knowledge.
Ready to connect★ 482
- View details
pruneSkillDev tools
Explicit V3 convergence pass that removes duplicated, fragmented, or low-value reconstructable llmdoc content.
Ready to connect★ 482
- View details
upgradeSkillDev tools
Explicit V2 to V3 migration surface. Never suggest this command implicitly.
Ready to connect★ 482
- View details
analytical-groundingSkillDev tools
Retrieve canonical pathway members, cell-type marker records, and genomic interval feature overlaps from declared analytical sources.
Ready to connect★ 481
- View details
ancestrySkillDev tools
Use local ancestry reference-panel tools for 1000 Genomes GRCh37/GRCh38 PCA projection, marker overlap QC, and qualitative reference-neighbor context.
Ready to connect★ 481
- View details
clinvarSkillDev tools
Build and inspect ClinVar exact-match evidence and candidate inventories. Use for clinical labels, VUS/conflict, carrier context, and drug-response rows.
Ready to connect★ 481
- View details
drug-targetsSkillDev tools
Causal drug-target and mechanism gene prioritization from public source records, drugs, drug classes, mechanisms, and candidate gene lists.
Ready to connect★ 481
- View details
functional-genomicsSkillDev tools
Candidate gene evidence from perturbation, dependency, resistance, sensitivity, viability, or assay-context records.
Ready to connect★ 481
- View details
genomiSkillDev tools
Use this skill for genetics, genome source, variant, gene, phenotype, disease, screen, pharmacogenomics, and Genomi install/setup maintenance questions.
Ready to connect★ 481
- View details
genomi-decodeSkillDev tools
Activate this skill for "/genomi decode", "decode my genome", "decode my DNA", "show me the dashboard", "the Genomi dashboard", "one-shot rundown", or any all-at-once request that asks Genomi to compose every capability's findings into a single artifact. This is the whole-genome dashboard kicker — i
Ready to connect★ 481
- View details
genomi-gnomadSkillDev tools
Fetch reusable public population allele frequencies from gnomAD for a specific variant. Use when the user asks about allele frequency, MAF, population stratification, gnomAD numbers, or rarity of a specific allele.
Ready to connect★ 481
- View details
gwas-catalogSkillDev tools
Compare candidate rsIDs against GWAS Catalog phenotype associations. Use association evidence with source and ancestry limitations.
Ready to connect★ 481
- View details
journal-source-researchSkillDev tools
Journal sub-skill for focused public/source evidence review and reviewed finding write-back before interpretation or answer synthesis.
Ready to connect★ 481
- View details
nutrigenomicsSkillDev tools
Curated single-marker evidence for declared nutrient-metabolism, food-tolerance, and taste-perception domains. Refuses diet prescriptions, supplement dosing, weight-loss prediction, methylation-cycle prescriptions, microbiome-mediated effects, and other out-of-scope nutrigenomic claims.
Ready to connect★ 481
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.
54,855 of the 55,286 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.