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,972 results · page 184 of 566
- View details
change-quizSkillDev tools
After a working session, produce a report on what changed plus a quiz the user must pass before merging. Use when the user asks "what did we actually do," wants to review a large change, or invokes a quiz before merge.
Ready to connect★ 331
- View details
implementation-planSkillDev tools
Write an implementation plan that leads with the decisions the user is most likely to change, and buries the mechanical work at the bottom. Use when planning is requested before a build, especially after brainstorming or an interview.
Ready to connect★ 331
- View details
reference-huntSkillDev tools
Use existing source code as the specification when the user can't describe what they want in words. Use when the user points at a library, module, folder, or site and says "like this," even if it's in a different language or stack.
Ready to connect★ 331
- View details
releasing-softwareSkillDev tools
Use when preparing a release, tagging a version, or when user says "release", "tag", "ship it", "push to production" - ensures all release artifacts are verified before tagging to avoid the retag-four-times failure pattern
Ready to connect★ 332
- View details
roborev-respondSkillDev tools
Use only when the user explicitly invokes $roborev-respond
Ready to connect★ 332
- View details
scenario-to-tiktokSkillDev tools
Use when a completed Shell scenario planning exercise needs to be converted into a TikTok script. Triggers when user says "make a tiktok", "tiktok script", "generate tiktok", or "content from scenario". Requires a completed scenario with narratives, findings, and worldview integration.
Ready to connect★ 332
- View details
session-reflection-analysisSkillDev tools
Use when asked to reflect on how the session went
Ready to connect★ 332
- View details
strategy-diagnosisSkillDev tools
Use when someone has a business problem, strategic question, or founder challenge they need to think through clearly. Triggers on "I'm stuck on", "should I", "what's wrong with my", "diagnose", "strategy problem", "business problem", "founder problem", "help me think through". Runs structured consul
Ready to connect★ 332
- View details
test-blindspotsSkillDev tools
Find consequential behavior that a passing test suite does not establish, using focused exploratory checks. Use when the user asks what green tests miss or wants confidence in test coverage for a specific change. Not a general code review, routine test run, or debugging workflow for an already faili
Ready to connect★ 331
- View details
adaptSkillDev tools
Gives your agent design guidance so the interfaces and visuals it creates look better.
Ready to connect★ 326
- View details
bolderSkillDev tools
Guides your agent to produce cleaner, more polished designs and UI in the content it creates.
Ready to connect★ 326
- View details
colorizeSkillDev tools
Gives your agent design guidance so the interfaces and visuals it creates look better.
Ready to connect★ 326
- View details
craftSkillDev tools
One-shot build pipeline for a complete surface from an outcome recipe — inputs (or defaults) → composition → theme → build order → acceptance bar. Use when the user asks for a whole surface (\"build me a dashboard\", \"hazme un dashboard\") and expects a shippable result, not component-level help. I
Ready to connect★ 326
- View details
delightSkillDev tools
Improves your agent's design output by giving it a set of design guidelines to follow.
Ready to connect★ 326
- View details
distillSkillDev tools
Reduction pass — cuts content, structure, visuals, and dead code that doesn't answer a user question or drive an action, respecting CRAFT_LEVEL. Use when the UI feels cluttered, has too many CTAs, walls of text, or decorative noise, or when the user says \"simplify this\" / \"it feels too busy\". In
Ready to connect★ 326
- View details
establishing-feasibility-firstSkillDev tools
Use when your human partner has explicitly opted into exploratory or feasibility mode - a compute-heavy simulation, an unproven pipeline, an unbenchmarked solver, an untested cluster job - or when whether the work can run at all is still unknown, when a plan's largest configuration has never been ex
Ready to connect★ 331
- View details
polishSkillDev tools
Final craft pass applying the compound details from the polish checklist — micro-typography, spacing rhythm, hover states, and a signature detail — directly to code. Use when the surface is functionally complete but feels unfinished, or when the user says \"polish this\" / \"it looks generic\" / \"a
Ready to connect★ 326
- View details
preregistering-analysisSkillDev tools
Use before running any confirmatory analysis or looking at outcome data, when testing a hypothesis, computing a p-value, or about to claim an effect - locks predictions and decision rules before results are seen
Ready to connect★ 331
- View details
quieterSkillDev tools
Gives your agent design guidance so it creates better-looking interfaces and layouts.
Ready to connect★ 326
- View details
receiving-critical-reviewSkillDev tools
Use when receiving critical feedback on an analysis or manuscript, before implementing suggestions, especially if feedback seems unclear or methodologically questionable - requires verification, not performative agreement or blind changes
Ready to connect★ 331
- View details
redesignSkillDev tools
Redesign an existing site or app without losing what already works — audits the current surface first, classifies what to preserve (brand, IA, SEO, content), picks a refresh/reskin/rebuild scope, then modernizes deliberately. Use when the user says \"redesign\", \"modernize this site\", \"refresh th
Ready to connect★ 326
- View details
reporting-and-archiving-findingsSkillDev tools
Use when an analysis is complete and verified, and you need to decide how to report it and archive the work for reproducibility
Ready to connect★ 331
- View details
requesting-red-team-reviewSkillDev tools
Use after completing an analysis or before reporting a finding, to have a skeptical reviewer attack the conclusion before you believe it
Ready to connect★ 331
- View details
setting-up-reproducible-analysisSkillDev tools
Use when starting analysis work that needs isolation, or before executing a pre-registered plan - ensures an isolated, reproducible workspace with pinned environment, fixed seeds, and immutable raw data
Ready to connect★ 331
- View details
surveying-prior-workSkillDev tools
Use after framing a question and before designing an analysis, or when choosing a method, judging whether a result is novel, or needing a prior effect size for a power calculation
Ready to connect★ 331
- View details
typesetSkillDev tools
Gives your agent design guidance so the interfaces and visuals it creates look better.
Ready to connect★ 326
- View details
ui-craft-editorialSkillDev tools
Editorial / magazine / long-form / Medium / Substack / content-heavy UIs. Locked knobs: CRAFT=9, MOTION=4, DENSITY=3. Serif display + humanist body, wide reading column, drop caps, OpenType. Trigger on: editorial, magazine, long-form, blog, Medium-like, Substack-like.
Ready to connect★ 326
- View details
using-science-superpowersSkillDev tools
Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
Ready to connect★ 331
- View details
verifying-results-before-claimingSkillDev tools
Use when about to claim a result, effect, significance, or that an analysis reproduces, before reporting or writing it up - requires running the analysis fresh and reading the actual output first; evidence before claims always
Ready to connect★ 331
- View details
custom-storiesSkillDev tools
AI openclaw mom and household manager for agentic parenting
Ready to connect★ 329
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,430 of the 53,863 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.