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 367 of 564
- View details
cite-reconSkillDev tools
Survey open legal questions and research gaps in the project. Use when asked "what legal questions are open", "where are our research gaps", or "list unresolved legal issues".
Ready to connect★ 71
- View details
cite-researchSkillDev tools
Legal research on a specific question — case law, statutes, regulatory guidance. Use when asked to "research this legal question", "what does case law say", or "find the relevant statute".
Ready to connect★ 71
- View details
clause-analyzeSkillDev tools
Deep clause-by-clause analysis of a contract with risk scores. Use when asked to "analyze this contract clause by clause", "score the risk in this agreement", or "what is dangerous in this contract".
Ready to connect★ 71
- View details
clause-playbookSkillDev tools
Generate negotiation playbook for a specific contract type. Use when asked to "build a negotiation playbook", "how do we negotiate this clause", or "what are our fallback positions".
Ready to connect★ 71
- View details
clause-reconSkillDev tools
Survey existing contracts for common clause patterns and risks. Use when asked "what clause patterns do our contracts use", "survey contract risk", or "find common terms across our contracts".
Ready to connect★ 71
- View details
clean-reconSkillDev tools
Audit existing data cleaning code — find missing validation, silent data loss, and quality gaps. Use when asked to "audit our data cleaning", "are we losing data silently", or "find data quality gaps".
Ready to connect★ 71
- View details
cn-law-hubSkillDev tools
For querying, retrieving, verifying, downloading, exporting, and bulk-collecting official Chinese laws, regulations, rules, treaties, and specific legal articles. Use this skill aggressively when the user asks to 查法律、查法规、查条例、查规章、查条约、查法条、查第几条、找法律依据、引用法律依据、核验现行有效、判断是否废止/已修改/尚未生效、下载法规全文、导出法规目录、批量下载法规文件
Ready to connect★ 71
- View details
compat-auditSkillDev tools
Audit a proposed API change for breaking changes — classification and impact assessment. Use when asked "is this a breaking change", "will this break clients", or "assess the impact of this API change".
Ready to connect★ 71
- View details
compat-reconSkillDev tools
Audit existing API for breaking change risks and missing compatibility controls. Use when asked to "find breaking change risks in our API", "audit our compatibility controls", or "what could break clients".
Ready to connect★ 71
- View details
context-guidanceSkillDev tools
Fixture skill used to represent an additional standard skill context surface.
Ready to connect★ 71
- View details
copy-reconSkillDev tools
Survey all user-facing strings in a codebase — map coverage and find gaps. Use when asked "what user-facing strings do we have", "map our copy coverage", or "find hardcoded strings".
Ready to connect★ 71
- View details
crestSkillDev tools
Product strategist — roadmaps, competitive analysis, OKRs, strategic narratives. Use when asked to "build a roadmap", "analyze competitors", "write a strategy memo", "prioritize features", or "set OKRs".
Ready to connect★ 71
- View details
crest-competeSkillDev tools
Competitive analysis ending in a clear positioning call — where to play, how to win. Use when asked to "analyze competitors", "competitive landscape", "how do we compare to X", "competitive positioning", "where should we play", "find our white space", or "who else does this".
Ready to connect★ 71
- View details
crest-narrativeSkillDev tools
Strategic narrative — write a standalone strategy memo that frames product direction, bets, and rationale for a planning horizon. Use when asked to "write a strategy doc", "product vision", "strategic narrative", "company strategy memo", "planning memo", or "explain our product direction".
Ready to connect★ 71
- View details
crest-reconSkillDev tools
Strategic context reconnaissance — read existing roadmaps, OKRs, competitive docs, and briefs to establish context before planning. Use when asked to "understand our strategy", "what's the current roadmap", "what OKRs do we have", "strategic context", or before starting any prioritization or roadmap
Ready to connect★ 71
- View details
crest-roadmapSkillDev tools
Build a product roadmap with sequenced bets and explicit tradeoffs. Use when asked to "build a roadmap", "prioritize the backlog strategically", "what do we build next quarter", "sequence our bets", "what should we focus on", or "product strategy for the next N months".
Ready to connect★ 71
- View details
cut-illustrateSkillDev tools
Spec or critique custom illustrations — style, composition, and brand alignment. Use when asked to "spec an illustration", "critique this illustration", or "define an illustration style".
Ready to connect★ 71
- View details
cut-reconSkillDev tools
Audit existing icons and illustrations in a codebase — find inconsistencies, unoptimized SVGs, and accessibility gaps. Use when asked to "audit our icons and illustrations", "find unoptimized SVGs", or "find inconsistent assets".
Ready to connect★ 71
- View details
dealSkillDev tools
Revenue & Sales engineer — B2B pipeline, deal strategy, pricing proposals, sales playbooks, and enterprise closing. Use when asked to "price this deal", "build a sales playbook", "close an enterprise deal", or "manage the B2B pipeline".
Ready to connect★ 71
- View details
deal-qualifySkillDev tools
MEDDPICC-based deal qualification worksheet — guide Deal through structured qualification of any opportunity and produce a filled card + recommended next action. Use when asked to "qualify this deal", "run MEDDPICC on this opportunity", "should we pursue this", or "is this deal real".
Ready to connect★ 71
- View details
deal-reconSkillDev tools
Revenue reconnaissance — audit current sales pipeline, deal patterns, ICP definition, and revenue motion to understand what's working and where the constraint is. Use when asked to "audit our sales", "where is revenue stuck", "what's our pipeline state", "before designing a playbook".
Ready to connect★ 71
- View details
decision-uiSkillDev tools
Load when Codex is about to ask the user to make a real decision among 2-3 mutually exclusive options, is preparing to ask a blocking clarifying question, or needs confirmation on a high-impact trade-off; converts choices into host-native clickable UI, with an honest text fallback when the tool is u
Ready to connect★ 71
- View details
draft-reconSkillDev tools
UI and UX reconnaissance — scan existing frontend routes, components, navigation, and flows to understand the current UX state before designing. Use when asked to "understand the current UI", "what UX patterns exist", "map the navigation", "what screens exist", or before starting any flow or wirefra
Ready to connect★ 71
- View details
echo-feedbackSkillDev tools
Feedback synthesis — cluster support tickets, NPS verbatims, app store reviews, and churn surveys by theme, separate signal from noise, and produce an actionable insight report. Use when asked to "synthesize this feedback", "analyze support tickets", "what are users complaining about", "NPS analysis
Ready to connect★ 71
- View details
echo-jobsSkillDev tools
Jobs-to-Be-Done analysis — given a product, user descriptions, transcripts, or tickets, produce a JTBD job map with switching forces analysis and opportunity ranking. Use when asked to "find the JTBD", "what jobs are users hiring us for", "job mapping", "what are users really trying to do", "JTBD fr
Ready to connect★ 71
- View details
edge-reconSkillDev tools
Audit existing CDN and edge configuration — find cache misses, missing headers, and performance gaps. Use when asked to "audit our CDN", "why is our cache hit rate low", or "find edge config gaps".
Ready to connect★ 71
- View details
end-to-end-featureSkillDev tools
Autonomously develops a complete feature from priming through planning, execution, and commit by chaining the four core PIV-loop skills. Use when you want a full hands-off feature build from a single description.
Ready to connect★ 71
- View details
eval-analyzeSkillDev tools
Analyze A/B test results — statistical significance, practical significance, and segmentation. Use when asked to "analyze our A/B test", "is this result significant", or "read these experiment results".
Ready to connect★ 71
- View details
eval-reconSkillDev tools
Audit existing experimentation infrastructure and past experiments for methodology issues. Use when asked to "audit our experiments", "is our experimentation sound", or "review past test methodology".
Ready to connect★ 71
- View details
execution-reportSkillDev tools
Generates a structured implementation report reflecting on a just-completed feature — what was done, divergences, challenges. Use right after finishing an implementation, as the input to a system review.
Ready to connect★ 71
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,789 of the 54,221 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.