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 336 of 564
- View details
baseline-reproSkillDev tools
Internal Harness instruction source for baseline-repro. Route through visible Harness aliases instead of invoking directly.
Ready to connect★ 86
- View details
baselinker-webhooksSkillDev tools
Receive BaseLinker (Base.com) webhooks. Use when building a BaseLinker order or warehouse callback receiver, because BaseLinker is not a normal webhook source: deliveries arrive as HTTP HEAD requests with NO body, the entire payload is in the query string (observed params: order_id, state), there is
Ready to connect★ 86
- View details
best-choiceSkillDev tools
When multiple solutions exist, pick the best one. Explain why in one sentence.
Ready to connect★ 86
- View details
bigcommerce-webhooksSkillDev tools
Receive and verify BigCommerce webhooks. Use when setting up BigCommerce webhook handlers, debugging Standard Webhooks signature verification, or handling store events like store/order/created, store/order/statusUpdated, store/product/updated, or store/cart/abandoned.
Ready to connect★ 86
- View details
bitbucket-webhooksSkillDev tools
Receive and verify Bitbucket Cloud webhooks. Use when setting up Bitbucket webhook handlers, debugging X-Hub-Signature verification, or handling repository and pull request events like repo:push, pullrequest:created, pullrequest:updated, pullrequest:fulfilled, or pullrequest:rejected.
Ready to connect★ 86
- View details
blind-spotSkillDev tools
Structural gap analysis -- find what the sprint has not considered.
Ready to connect★ 86
- View details
bridge-xyz-webhooksSkillDev tools
Receive and verify Bridge (bridge.xyz) webhooks. Use when setting up Bridge webhook handlers, debugging RSA signature verification of the X-Webhook-Signature header, or handling stablecoin/fiat events like customer.updated, kyc_link.updated, transfer.updated, and virtual_account.activity.
Ready to connect★ 86
- View details
briefSkillDev tools
Generate a compiled decision brief from the current sprint's claims.
Ready to connect★ 86
- View details
build-featureSkillDev tools
Build one feature at a time. Complete each fully before moving to next. Auto-triggers quality check.
Ready to connect★ 86
- View details
build-uiSkillDev tools
Build user-facing interface. Clean, functional, mobile-friendly by default.
Ready to connect★ 86
- View details
calibrateSkillDev tools
Score past predictions against actual outcomes. Closes the feedback loop.
Ready to connect★ 86
- View details
campaignSkillDev tools
Orchestrate durable autonomous research iterations inside an accepted Campaign Contract.
Ready to connect★ 86
- View details
celebrateSkillDev tools
Celebrate real milestones only. One line, one emoji. Credit belongs to user, not AI.
Ready to connect★ 86
- View details
changeSkillDev tools
Classify a mature-codebase delta and execute only the owning route.
Ready to connect★ 86
- View details
change-intakeSkillDev tools
Internal Harness instruction source for change-intake. Route through visible Harness aliases instead of invoking directly.
Ready to connect★ 86
- View details
chargebee-webhooksSkillDev tools
Receive and verify Chargebee webhooks. Use when setting up Chargebee webhook handlers, debugging Basic Auth verification, or handling subscription billing events.
Ready to connect★ 86
- View details
classic-to-default-syncSkillDev tools
Inspect a given commit's web/classic changes and sync all features/fixes to web/default. Use when the user provides a commit ID and wants to audit whether web/default already has the same features as web/classic, port missing features, improve suboptimal implementations, fix bugs, and remove redunda
Ready to connect★ 86
- View details
clerk-webhooksSkillDev tools
Receive and verify Clerk webhooks. Use when setting up Clerk webhook handlers, debugging signature verification, or handling user events like user.created, user.updated, session.created, or organization.created.
Ready to connect★ 86
- View details
clio-webhooksSkillDev tools
Receive and verify Clio (Clio Manage) webhooks. Use when setting up Clio webhook handlers, debugging X-Hook-Signature verification, completing the X-Hook-Secret handshake, or handling legal practice events like matter.created, contact.updated, activity.created, or bill events.
Ready to connect★ 86
- View details
commercelayer-webhooksSkillDev tools
Receive and verify Commerce Layer webhooks. Use when setting up Commerce Layer webhook handlers, debugging X-CommerceLayer-Signature verification, or handling commerce events like orders.place, orders.approve, orders.pay, or shipments.ship.
Ready to connect★ 86
- View details
compliance-precheckSkillDev tools
Use this skill at the very start of every OpenSpec change (Step 0) for a medical-data SaaS / data platform repository. It classifies the data tier (L1-L4) the change will touch, enumerates the minimal required fields, and produces a signed COMPLIANCE_TAG.md plus a MODEL_ALLOWLIST.json that the mcp-m
Ready to connect★ 86
- View details
data-prepSkillDev tools
Internal Harness instruction source for data-prep. Route through visible Harness aliases instead of invoking directly.
Ready to connect★ 86
- View details
deepgram-webhooksSkillDev tools
Receive and verify Deepgram webhooks (callbacks). Use when setting up Deepgram webhook handlers, processing transcription callbacks, or handling asynchronous transcription results.
Ready to connect★ 86
- View details
docusign-webhooksSkillDev tools
Receive and verify DocuSign Connect webhooks. Use when setting up DocuSign webhook handlers, debugging HMAC signature verification of the X-DocuSign-Signature-1 header, or handling eSignature events like envelope-sent, envelope-completed, and recipient-completed.
Ready to connect★ 86
- View details
efficiency-compareSkillDev tools
At milestones, compare achievement vs human programmer time and cost. Keep it realistic.
Ready to connect★ 86
- View details
elevenlabs-webhooksSkillDev tools
Receive and verify ElevenLabs webhooks. Use when setting up ElevenLabs webhook handlers, debugging signature verification, or handling call transcription events.
Ready to connect★ 86
- View details
enode-webhooksSkillDev tools
Receive and verify Enode webhooks. Use when setting up Enode webhook handlers, debugging signature verification, or handling EV and energy events like user:vehicle:updated, user:charger:updated, or user:battery:updated.
Ready to connect★ 86
- View details
env-setupSkillDev tools
Internal Harness instruction source for env-setup. Route through visible Harness aliases instead of invoking directly.
Ready to connect★ 86
- View details
faundit-webhooksSkillDev tools
Receive and verify Faundit webhooks. Use when setting up Faundit lost-and-found / returns webhook handlers, debugging signature verification, or handling the item-status and request-status events (statuses like delivered, finished, expired).
Ready to connect★ 86
- View details
favro-webhooksSkillDev tools
Receive and verify Favro webhooks. Use when setting up Favro webhook handlers, debugging X-Favro-Webhook signature verification, accepting the setup ping, or handling card events (card.created, card.committed, card.moved, card.updated, card.deleted) and comment events (comment.created, comment.updat
Ready to connect★ 86
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.