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: Docs & knowledge
4,535 results · page 81 of 152
- View details
suede-play-releaseSkillDocs & knowledge
Suede Labs Google Play delivery skill: ship an Android release end to end from the agent interface, without opening the Play Console. Set up credentials, upload an AAB, promote between tracks, stage or complete a rollout, push per-locale release notes, and prove against the Play Developer API what i
Ready to connect★ 135
- View details
suede-rights-passportSkillDocs & knowledge
Suede Labs skill that turns messy creator materials into a local, offline rights-and-provenance transfer package: inventoried and hashed assets, a normalized suede-intake.json manifest, credits and splits, license notes, provenance, and a missing-information report, validated by a bundled stdlib scr
Ready to connect★ 135
- View details
unslopSkillDocs & knowledge
Strip AI writing tells from Rove's user-facing prose — README, the docs/ pages that sync to docs.rove.run, landing copy, and release notes. Use when the user says "unslop", "洗一下文案", "这读起来像 AI 写的", or after drafting any user-facing page. Adapted for this repo from cursor/plugins pstack/skills/unslop.
Ready to connect★ 135
- View details
beamer-deckSkillDocs & knowledge
Create an academic presentation as a LaTeX Beamer source and reviewed PDF with an original theme. Use when the requested deliverable is a conference, seminar, or lecture deck in Beamer. Not for PowerPoint or RevealJS; use $pptx or $quarto-deck.
Ready to connect★ 134
- View details
brief-compliance-checkSkillDocs & knowledge
Check a LaTeX coursework submission against the requirements in a supplied PDF assessment brief. Use when verifying format, required sections, word limits, or deliverables before submission. Not for general prose proofreading; use $proofread.
Ready to connect★ 134
- View details
carouselSkillDocs & knowledge
How to make a multi-style multi-slide social carousel (5-10 slides × N styles) where the deliverable is the baked-text image itself — no HyperFrames compose. A domain overlay on the standard pipeline: supplies the cover-first checkpoint (one cover per style → user review → fill the rest), the dual-r
Ready to connect★ 134
- View details
compile-knowledgeSkillDocs & knowledge
Lets your agent save important findings as linked markdown notes so it remembers lessons across future sessions.
Ready to connect★ 134
- View details
dev-issuesSkillDocs & knowledge
Turn a free-form brain-dump into a clean, ordered set of `notes/issues/*.md` work items. The user tags `/dev-issues` and writes a long stream of everything in their head — features, refactors, bugs, half-formed ideas, product direction. This skill decomposes that stream into discrete, well-shaped, i
Ready to connect★ 134
- View details
dev-loopSkillDocs & knowledge
Run an autonomous, issue-driven development loop over Ralphy itself — the same cadence as a focused maintainer session: pick the open `notes/issues/`, order them by dependency, then for each issue dispatch a scoped sub-agent, review its diff, run the real gates, and commit + push to main before movi
Ready to connect★ 134
- View details
dev-releaseSkillDocs & knowledge
Cut a Ralphy CLI release across GitHub Releases, Homebrew, and npm. Use when the user asks to release, tag, publish, or prepare release notes for the CLI. Public documentation and the marketing site live in sibling repositories and are synchronized separately when their content is affected.
Ready to connect★ 134
- View details
dev-tasksSkillDocs & knowledge
Manage Ralphy's `notes/` capture inbox (`ideas/`, `issues/`, `decisions/`) — the only dev tracker for Ralphy itself; there is no separate roadmap board. Two jobs: (1) CAPTURE — turn a tagged thought into a correctly-shaped, correctly-placed note (an idea, an issue, or a decision); (2) COLLISION-CHEC
Ready to connect★ 134
- View details
diataxis-docsSkillDocs & knowledge
Design, classify, write, audit, or restructure technical documentation with the Diátaxis framework. Use for tutorials, how-to guides, reference material, explanations, documentation maps, README routing, documentation audits, or requests to separate mixed-purpose docs. Do not apply it automatically
Ready to connect★ 134
- View details
docs-consistencySkillDocs & knowledge
Review user-facing documentation for accuracy, consistency, and completeness across private, public, nested repos, and the user manual. Use when docs feel stale, after major changes, or before sharing. (Replaces `repo-doc-audit`)
Ready to connect★ 134
- View details
docs-diataxisSkillDocs & knowledge
Entry point for writing or improving software documentation using the Diátaxis framework. Use this first whenever you are about to write, restructure, or assess docs (README sections, guides, API docs, conceptual articles). It identifies which of the four documentation modes fits the task, then rout
Ready to connect★ 134
- View details
docs-explanationSkillDocs & knowledge
Write Diátaxis explanation, ie understanding-oriented documentation that discusses a subject to deepen the reader's grasp of it, covering context, reasons, design decisions, history, and alternatives. Use when the reader wants to understand why and how something is, not to perform a task (how-to gui
Ready to connect★ 134
- View details
docs-improvingSkillDocs & knowledge
Audit, restructure, or incrementally improve an existing body of documentation using Diátaxis. Use when the task is to assess docs, untangle mixed-up content, or raise quality across a project rather than write a single new piece. Covers the iterative workflow and how to judge documentation quality.
Ready to connect★ 134
- View details
docs-referenceSkillDocs & knowledge
Write Diátaxis reference material, ie information-oriented documentation that neutrally describes a product's machinery (APIs, functions, classes, commands, options, config) for users to consult while working. Use when the reader needs accurate facts to look up, not steps to follow (how-to guide) or
Ready to connect★ 134
- View details
docs-rust-conventionsSkillDocs & knowledge
Rust documentation conventions (RFC 1574). Apply when writing doc comments on public Rust items. Covers summary sentences, section headings, type references, and examples.
Ready to connect★ 134
- View details
docs-rust-sweepSkillDocs & knowledge
Comprehensive public-api quality pass over the core crates, reducing pub visibility and documenting every public item to a deny(missing_docs) standard. Use for crate-wide documentation or visibility sweeps.
Ready to connect★ 134
- View details
docs-tutorialsSkillDocs & knowledge
Write a Diátaxis tutorial, ie learning-oriented documentation that teaches a beginner a skill through a guided, hands-on lesson. Use when the goal is to take someone new and give them a successful first experience, not to solve a specific problem (that is a how-to guide) or to explain concepts (that
Ready to connect★ 134
- View details
evidence-firstSkillDocs & knowledge
Shape human-facing engineering communication—including chat updates and final answers, reports, reviews, handoffs, debugging or benchmark summaries, PR and issue prose, READMEs, and technical documentation—around clear claims, measured support, explicit gaps, and scoped decisions. Use whenever Codex
Ready to connect★ 134
- View details
fax-sendSkillDocs & knowledge
Send outbound faxes through a guarded provider adapter and route inbound fax-to-email attachments into downstream document workflows.
Ready to connect★ 134
- View details
hermes3000-writingSkillDocs & knowledge
Use Hermes3000 to plan, draft, revise, save, check consistency, and export long-form manuscripts through the Hermes3000 AI writing portal API. Use for novels, fiction series, nonfiction books, whitepapers, long reads, chapter outlines, character/world-building, style guides, consistency memory, and
Ready to connect★ 134
- View details
hubspotSkillDocs & knowledge
Read HubSpot contacts, companies, and deals; update deal stages and lifecycle stages; log notes and tasks through gateway-managed bearer tokens.
Ready to connect★ 134
- View details
human-distillSkillDocs & knowledge
Distill a real person into a hireable coworker agent from their source material — chat exports, emails, meeting transcripts, documents, interviews, and live mirroring. Use when the operator wants to clone a colleague, build a coworker from someone's writing, onboard a digital twin, or asks to 'disti
Ready to connect★ 134
- View details
hybridclaw-helpSkillDocs & knowledge
HybridClaw help. Primary skill for product questions about setup, configuration, commands, runtime behavior, and release notes.
Ready to connect★ 134
- View details
intakeSkillDocs & knowledge
Intake protocol — the craft of turning a vague brief into an approved production plan. Runs phases 1-7 of the agent production contract: 3-5 clarifying questions sized to the user's skill band, content-mode classification, format/template match, memory recall, the reference gate, the style lock, and
Ready to connect★ 134
- View details
knowledge-lintSkillDocs & knowledge
Lint an existing project knowledge base for contradictions, uncited claims, missing connections, stale articles, and orphaned concepts. Use when checking the integrity of already compiled knowledge before relying on or expanding it. Not for compiling raw sources; use $compile-knowledge.
Ready to connect★ 134
- View details
latexSkillDocs & knowledge
Compile one specified LaTeX document, resolve build errors, audit citations, and report build quality. Use when a .tex source must be built or a concrete compilation failure repaired. Not for corpus-wide build checks, visual polish after a clean build, or creating a project; use $latex-health-check,
Ready to connect★ 134
- View details
latex-polishSkillDocs & knowledge
Inspect a cleanly compiling LaTeX document for source pathologies and rendered visual defects by linting and viewing selected PDF pages. Use when compilation succeeds but title pages, floats, tables, figures, or layout still need publication-quality review. Not for basic compilation health; use $lat
Ready to connect★ 134
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,764 of the 55,196 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.