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,976 results · page 499 of 566
- View details
requirements-analysisSkillDev tools
Analyze and refine product requirements. Use when clarifying scope, identifying gaps, or validating requirements. Covers requirement types and analysis techniques.
Ready to connect
- View details
research-publication-pipelineSkillDev tools
Use when selecting, starting, or resuming an evidence-gated research route for a top computer-science venue or Nature-family journal; source-grounded paper reading, AI-for-biology data feasibility, scoop checks, venue fit, baseline headroom, frozen protocols, controlled iterations, claim locking, ne
Ready to connect
- View details
review-gitcode-prSkillDev tools
Review a GitCode pull request from a PR number or URL when `oh-gc` must fetch PR metadata, diff, and comments, local repository code must be inspected for context, and the output should be concrete findings or a GitCode submission draft. Use for GitCode PR review or comment-submission requests that
Ready to connect
- View details
review-others-manuscriptsSkillDev tools
Use when acting as an invited referee on someone else's submission, including writing a referee report, drafting reviewer comments, assessing a revision round against the authors' response letter, running an editorial prescreen for scope and policy, or judging whether a stated claim is carried by th
Ready to connect
- View details
run-cold-review-panelSkillDev tools
Use when a manuscript you wrote is nearly finished and needs a hostile read before it is submitted, including a mock review, a simulated reviewer panel, a pre-submission review, red-team the paper, asking whether this would get rejected, or checking which reviewer objection the paper cannot survive.
Ready to connect
- View details
rust-call-graphSkillDev tools
Visualize Rust function call graphs using LSP. Triggers on: /call-graph, call hierarchy, who calls, what calls, 调用图, 调用关系, 谁调用了, 调用了谁
Ready to connect
- View details
rust-deps-visualizerSkillDev tools
Visualize Rust project dependencies as ASCII art. Triggers on: /deps-viz, dependency graph, show dependencies, visualize deps, 依赖图, 依赖可视化, 显示依赖
Ready to connect
- View details
rust-symbol-analyzerSkillDev tools
Analyze Rust project structure using LSP symbols. Triggers on: /symbols, project structure, list structs, list traits, list functions, 符号分析, 项目结构, 列出所有, 有哪些struct
Ready to connect
- View details
scott-adamsSkillDev tools
Use when the user wants to simplify prose, prune extra words, craft high-curiosity opening hooks, write punchy short sentences, and structure ideas for maximum human brain comprehension based on Scott Adams' famous business writing method.
Ready to connect
- View details
scrutinizeSkillDev tools
Outsider-perspective end-to-end review of a plan, PR, or code change. First questions intent and whether a simpler/more elegant approach would achieve the same goal, then traces the actual code path (not just the diff) to verify the change does what it claims. Output is concise, actionable, and ever
Ready to connect
- View details
shiftSkillDev tools
Restate the problem in a distant domain's terms. Use when a problem circles inside its own vocabulary.
Ready to connect
- View details
shrekSkillDev tools
Write deadpan, dry, grumpy-but-warm prose in the voice of Shrek. Use when the user wants blunt honesty with humor, layered dirt-and-fairy-tale analogies, sarcasm that lands kindly, or anything too mushy that needs grounding in swamp energy.
Ready to connect
- View details
skill-distillerSkillDev tools
Fetches top-rated skills from skills.sh, analyzes them, and synthesizes one token-efficient skill combining the best elements. Use when the user asks to "distill skills for X", "find and combine skills for X", "synthesize skills", "merge skills", "make a skill for X from skills.sh", "update distille
Ready to connect
- View details
skill-folder-nameSkillDev tools
One sentence stating what this skill produces and per which standard or character. Use when the user [concrete trigger situations, the actual phrases they'd type, and the contexts where this beats default prose].
Ready to connect
- View details
skilloptSkillDev tools
Prepare or run Whetstone SkillOpt optimization when asked to optimize a process skill using SkillOpt.
Ready to connect
- View details
- View details
source-command-lint-fixSkillDev tools
Run Biome lint and format across the project, auto-fixing issues.
Ready to connect
- View details
source-command-typecheckSkillDev tools
Run TypeScript type checking across the monorepo.
Ready to connect
- View details
spark-best-practicesSkillDev tools
Apache Spark 4.0.2 best practices for PySpark and Scala distributed data processing
Ready to connect
- View details
springboot-best-practicesSkillDev tools
Spring Boot 4.0 patterns for enterprise Java 25 applications
Ready to connect
- View details
structured-dev-cycleSkillDev tools
6-stage structured development cycle with stage-based tool restrictions
Ready to connect
- View details
- View details
survey-and-audit-noveltySkillDev tools
Use when deciding whether a research direction is still open, including a literature survey that has to end in a decision, a novelty audit, a prior art check, a scoop check against recent work, asking whether anyone has already done this, or checking that the variables an idea needs actually co-exis
Ready to connect
- View details
sync-from-reposSkillDev tools
Compare Whetstone with reference repositories when asked to sync cross-repository improvements.
Ready to connect
- View details
tailnet-execSkillDev tools
Send a command into the namespace of one tailnet rather than to the host network. Use when asked to reach a peer, to run a command against a tailnet address, or to run a tailscale command for one tailnet.
Ready to connect
- View details
targetSkillDev tools
Define how unsupervised work is judged before it runs. Use when work will run without a human watching, optimizing toward something.
Ready to connect
- View details
technical-changelogSkillDev tools
Generate a diff-grounded, one-page technical changelog for a Glassbox release — from the actual code changes between the last production tag and HEAD (the next, still-unreleased version). Asks for the next version number, since package.json holds the last release.
Ready to connect
- View details
ted-lassoSkillDev tools
Write warm, high-EQ, folksy-optimistic content in the voice of Ted Lasso. Use when the user asks for an encouraging, kind, or optimistic tone; a motivational pep talk; reframing a negative or difficult topic constructively; or anything where cynical, sarcastic, or corporate-neutral writing would be
Ready to connect
- View details
tenant-decisionsSkillDev tools
Use when the user asks why the tenant is configured a certain way, or wants to record the reason behind a configuration decision.
Ready to connect
- View details
tenant-pulseSkillDev tools
Use when the user asks how healthy or secure the tenant is, says posture, risk, score, "how are we doing", or wants a scored Microsoft 365 tenant snapshot.
Ready to connect
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,082 of the 54,514 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.