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 366 of 564
- View details
- View details
ui-previewSkillDev tools
Preview and screenshot local dev servers and storybooks. Use when asked to view UI components, take screenshots of storybooks, or inspect the web/server apps.
Ready to connect★ 72
- View details
advai-infoSkillDev tools
Inspects advai installation, runtime, and update guidance with `advai info` and `advai update`. Invoke when user asks how advai is installed, where it runs from, or how to upgrade it.
Ready to connect★ 70
- View details
apex-planSkillDev tools
Plan and scope a project — discovery, challenge assumptions, present XS-XXL depth options with token and cost estimates. Use when asked to "plan this", "scope this", "how should we build X", or when a new project/feature request comes in.
Ready to connect★ 71
- View details
apex-reconSkillDev tools
Engineering lead reconnaissance — inventory the project before planning. Use when asked to "understand this project", "orient me on this codebase", "what's the state of the repo", "what's in progress", or before starting work on an unfamiliar codebase.
Ready to connect★ 71
- View details
apex-reviewSkillDev tools
Cross-cutting review of recent work — catches gaps between specialists. Use when asked to "review what we built", "check the work", "pre-launch review", or after completing a significant chunk of work.
Ready to connect★ 71
- View details
apex-statusSkillDev tools
CTO-level project status from git and codebase state. Use when asked "where are we", "project status", "what's done", or at the start of a work session.
Ready to connect★ 71
- View details
apex-takeoverSkillDev tools
System takeover — take ownership of an existing codebase or inherited system. Use when "we acquired this", "previous team left", "take over this system", "inherited this codebase".
Ready to connect★ 71
- View details
ask-viySkillDev tools
Master index for this recruiting toolkit. Ask it when you don't know what to do next, which workflow to use, or how a feature works.
Ready to connect★ 70
- View details
atlas-mapSkillDev tools
Map the system architecture — read the codebase, identify services and connections, output a C4-level architecture map as Mermaid diagrams with component descriptions. Use when asked to "map the architecture", "system diagram", "how does this work", or "architecture overview".
Ready to connect★ 71
- View details
audit-controlsSkillDev tools
Internal legal controls review — approval workflows, contract lifecycle, access to sensitive docs. Use when asked to "audit our controls", "review approval workflows", or "who can access sensitive contracts".
Ready to connect★ 71
- View details
audit-legalSkillDev tools
Full legal compliance audit — contracts, policies, regulatory, IP, corporate hygiene. Use when asked to "run a legal audit", "are we legally compliant", or "full compliance review".
Ready to connect★ 71
- View details
audit-reconSkillDev tools
Survey legal artifacts for audit readiness. Use when asked "are we audit ready", "what legal artifacts exist", or "survey our legal docs".
Ready to connect★ 71
- View details
axe-auditSkillDev tools
Run a WCAG accessibility audit against a component, page, or full product. Use when asked to "run an accessibility audit", "is this WCAG compliant", or "check a11y on this page".
Ready to connect★ 71
- View details
axe-fixSkillDev tools
Write accessibility fixes for specific WCAG failures — ARIA, focus management, keyboard patterns. Use when asked to "fix this accessibility issue", "add ARIA labels", or "make this keyboard navigable".
Ready to connect★ 71
- View details
axe-reconSkillDev tools
Survey a codebase for accessibility debt — missing ARIA, broken keyboard patterns, and contrast issues. Use when asked "how accessible is our codebase", "find accessibility debt", or "where are our a11y gaps".
Ready to connect★ 71
- View details
bench-compareSkillDev tools
Compare API performance across versions — regression detection and root cause analysis. Use when asked "did performance regress", "compare API latency across versions", or "why is this slower".
Ready to connect★ 71
- View details
bench-reconSkillDev tools
Audit existing performance testing — find missing benchmarks, stale baselines, and CI gaps. Use when asked "do we have benchmarks", "audit our performance testing", or "are our baselines stale".
Ready to connect★ 71
- View details
bind-gapSkillDev tools
Run a compliance gap analysis against SOC2, GDPR, HIPAA, or ISO 27001. Use when asked "are we SOC2 ready", "run a GDPR gap analysis", or "what is missing for ISO 27001".
Ready to connect★ 71
- View details
bind-reconSkillDev tools
Survey existing compliance artifacts — policies, audits, certifications. Use when asked "what compliance docs do we have", "survey our policies", or "inventory our compliance artifacts".
Ready to connect★ 71
- View details
blue-hardenSkillDev tools
Write a hardening playbook for a system or service — CIS benchmark mapping and implementation steps. Use when asked to "harden this server", "apply the CIS benchmark", or "write a hardening playbook".
Ready to connect★ 71
- View details
brief-reconSkillDev tools
Survey the project's existing contracts and policy docs. Use when asked "what contracts do we have", "survey our policy docs", or "inventory our agreements".
Ready to connect★ 71
- View details
brief-reviewSkillDev tools
Review and redline a contract — flag risk, missing clauses, one-sided terms. Use when asked to "review this contract", "redline this agreement", or "is this contract risky".
Ready to connect★ 71
- View details
buzzSkillDev tools
PR & Community engineer — press pitches, social media, open source community, DevRel, and coordinated launch moments. Use when asked to "write a press release", "plan a launch", "build a community", "draft a HN or Twitter post", or "get media coverage".
Ready to connect★ 71
- View details
buzz-hnSkillDev tools
Hacker News post crafter — given a product, feature, or story produces a ready-to-post HN submission (title ≤80 chars, no marketing), honest body text with technical depth, no outbound links, predicted reception analysis, and comment-response templates for likely pushback. Use when asked to "write a
Ready to connect★ 71
- View details
buzz-reconSkillDev tools
PR and community reconnaissance — audit current press coverage, social presence, community health, and competitor PR. Use when asked to "audit our PR", "what's our community state", "how do we compare in press", or before planning a launch or community initiative.
Ready to connect★ 71
- View details
buzz-socialSkillDev tools
Social media strategy and post drafting — HN posts, Twitter/X threads, LinkedIn posts, Reddit comments, and developer community content. Use when asked to "write a HN post", "draft social posts", "help us post on Twitter", or "create a social launch plan".
Ready to connect★ 71
- View details
change-reconSkillDev tools
Audit existing changelog and deprecation practices — find missing entries, undocumented breaks, and stale deprecations. Use when asked to "audit our changelog", "find undocumented breaking changes", or "check for stale deprecations".
Ready to connect★ 71
- View details
chaos-reconSkillDev tools
Audit existing resilience — identify untested failure modes and chaos engineering gaps. Use when asked "how resilient are we", "what failure modes are untested", or "find our chaos engineering gaps".
Ready to connect★ 71
- View details
cite-compareSkillDev tools
Jurisdiction comparison for a legal requirement or contract clause. Use when asked "how does this differ by jurisdiction", "compare GDPR and CCPA on this", or "run a state law comparison".
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.