ahel is live on Product Hunt today. Upvote

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,980 results · page 162 of 566

  • using-the-mcp-serverSkillDev tools

    Use when parsing source, extracting code structure, or detecting a language through the tree-sitter-language-pack MCP server's tools, rather than shelling out to the ts-pack CLI. Covers the tool surface, the auto-installing launcher, and when MCP beats the CLI or SDK.

    Ready to connect★ 465

    github.com/xberg-io/tree-sitter-language-pack463 stars

    View details
  • ai-checkSkillDev tools

    Use when someone asks "does this sound AI?", "check if this is AI-written", "what gives this away as AI", "run ai-check on this", or "score this text". Also use when reviewing a draft for AI tells before publishing, or when a piece of text reads as suspiciously polished, generic, or pattern-y and th

    Ready to connect★ 460

    github.com/harshaneel/humanize464 stars

    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★ 459

    github.com/jetbrains/thinkrail464 stars

    View details
  • choosing-a-workflowSkillDev tools

    Use FIRST when any new piece of work arrives — a request, feature, change, fix, question, or idea — before starting on it or choosing an approach. Not for continuing work already routed to a workflow skill.

    Ready to connect★ 459

    github.com/jetbrains/thinkrail464 stars

    View details
  • importing-a-codebaseSkillDev tools

    Use when the repo holds real source code but no specs: the existing-codebase branch of setting-up-a-project, normally reached via that dispatcher, directly only when the situation is unmistakable. Not for empty workspaces (starting-a-new-project) or feature work in a specced project (brainstorming).

    Ready to connect★ 459

    github.com/jetbrains/thinkrail464 stars

    View details
  • setting-up-a-projectSkillDev tools

    Use whenever asked to set up, onboard, initialize, or spec a project — the front door when the workspace has no spec graph yet (brand-new or an existing codebase); also seeded by the app's Set-up-project card (/skill:setting-up-a-project). Not for feature work in an already-specced project — use the

    Ready to connect★ 459

    github.com/jetbrains/thinkrail464 stars

    View details
  • starting-a-new-projectSkillDev tools

    Use when the workspace is empty — no code yet — and the user brings a raw idea: the brand-new branch of setting-up-a-project, normally reached via that dispatcher, directly only when the situation is unmistakable. Not for features in an existing project — use brainstorming instead.

    Ready to connect★ 459

    github.com/jetbrains/thinkrail464 stars

    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★ 459

    github.com/jetbrains/thinkrail464 stars

    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★ 459

    github.com/jetbrains/thinkrail464 stars

    View details
  • new-caskSkillDev tools

    This skill should be used when the user asks to "add a cask to homebrew", "create a homebrew cask", "add an app to homebrew", "new cask for", "homebrew cask for", "package an app for homebrew", "submit to homebrew-cask", "make a cask", "contribute a cask", or wants to package a macOS application for

    Ready to connect★ 463

    github.com/malob/nix-config463 stars

    View details
  • startSkillDev tools

    Enable auto TTS for this session

    Ready to connect★ 463

    github.com/malob/nix-config463 stars

    View details
  • stopSkillDev tools

    Disable auto TTS for this session

    Ready to connect★ 463

    github.com/malob/nix-config463 stars

    View details
  • launch-shadcn-registrySkillDev tools

    Launch and promote a custom shadcn/ui registry end-to-end: validate registry.json, prepare the official shadcn-ui/ui directory PR, community directory PRs (registry.directory, shadcntemplates, birobirobiro/awesome-shadcn-ui, bytefer/awesome-shadcn-ui), and draft social posts for Reddit r/shadcn, X,

    Ready to connect★ 462

    github.com/shadcn-labs/agentcn453 stars

    View details
  • autofixSkillDev tools

    Fix one confirmed bug unattended and leave a reviewable branch — failing test first, minimal diff, CI gate, changelog fragment, PR_BODY.md. Committing, pushing, and opening the PR happen outside this skill.

    Ready to connect★ 458

    github.com/vavallee/bindery440 stars

    View details
  • collect-target-contextSkillDev tools

    Collect the baseline context bundle for the selected target.

    Ready to connect★ 456

    github.com/understudy-ai/understudy457 stars

    View details
  • explore-unfamiliar-targetSkillDev tools

    Goal-driven worker for exploring an unfamiliar target.

    Ready to connect★ 456

    github.com/understudy-ai/understudy457 stars

    View details
  • prepare-delivery-previewSkillDev tools

    Prepare the delivery preview payload from the generated assets.

    Ready to connect★ 456

    github.com/understudy-ai/understudy457 stars

    View details
  • researcherSkillDev tools

    Research current topics with multiple sources and produce a structured brief, comparison, recommendation, or fact-check. Use when the user asks for investigation, market/product landscape scans, option evaluation, due diligence, source-backed validation, or a research report. Do not use for summariz

    Ready to connect★ 456

    github.com/understudy-ai/understudy457 stars

    View details
  • synthesize-briefSkillDev tools

    Turn context findings into a summary packet and short brief.

    Ready to connect★ 456

    github.com/understudy-ai/understudy457 stars

    View details
  • target-brief-baseline-stageSkillDev tools

    Single-stage acceptance playbook for the baseline context phase.

    Ready to connect★ 456

    github.com/understudy-ai/understudy457 stars

    View details
  • target-brief-studioSkillDev tools

    Hand-written end-to-end playbook for a reusable target brief workflow.

    Ready to connect★ 456

    github.com/understudy-ai/understudy457 stars

    View details
  • bagofwordsSkillDev tools

    Query, visualize, and analyze data in a Bag of Words (BOW) workspace via the bagofwords MCP tools. Use for creating reports, running tracked queries, and building dashboards.

    Ready to connect★ 455

    github.com/bagofwords1/bagofwords453 stars

    View details
  • sandbox-feedback-loopSkillDev tools

    Build a runnable reproduce→fix→verify loop for a bug or feature in a fresh sandbox, and record it as a feedback-loop doc. Use when investigating a reported bug, validating a root cause, or proving a fix works — before and after the change.

    Ready to connect★ 455

    github.com/bagofwords1/bagofwords453 stars

    View details
  • featSkillDev tools

    Build a feature end-to-end (GitHub issue or free-text → plan → implement → PR), OR plan one read-only with `--investigate`. Add `--auto` to run unattended (never asks; build stops at a draft PR). Use anytime you need to build a feature, or to plan one ahead without writing code.

    Ready to connect★ 449

    github.com/ossappscollective/oss-weather449 stars

    View details
  • videorc-releaseSkillDev tools

    Cut and publish coordinated Videorc desktop releases for the signed and notarized macOS Beta and the signed Windows 11 x64 Alpha, including version/changelog preparation, protected Windows candidate and promotion workflows, R2 publication, updater verification, and release records. Use when the user

    Ready to connect★ 449

    github.com/theorcdev/videorc448 stars

    View details
  • 4-ultraciteSkillDev tools

    Skill: 4-ultracite

    Ready to connect★ 447

    github.com/udecode/kitcn446 stars

    View details
  • changeset-doc-syncSkillDev tools

    Read every doc in www and packages/kitcn/skills/kitcn, sync to active changeset(s), and track with checkmarks.

    Ready to connect★ 447

    github.com/udecode/kitcn446 stars

    View details
  • concaveSkillDev tools

    Skill: concave

    Ready to connect★ 447

    github.com/udecode/kitcn446 stars

    View details
  • concave-paritySkillDev tools

    Skill: concave-parity

    Ready to connect★ 447

    github.com/udecode/kitcn446 stars

    View details
  • grill-with-visionSkillDev tools

    Pressure-test a kitcn product, API, architecture, or DX direction against VISION.md and source evidence before committing to a plan or PRD.

    Ready to connect★ 447

    github.com/udecode/kitcn446 stars

    View details

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,462 of the 53,895 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.

See how to connect your AI