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
17,088 results · page 555 of 570
- View details
itu-t-recommendation-reviewerSkillDev tools
Review draft ITU-T Recommendations (and ITU-T | ISO/IEC common texts) for compliance with the ITU-T Author's Guide, presentation rules, and quality checklist before submission for consent/determination/approval. Use this skill whenever the user asks to review, check, audit, proofread, or improve a d
Ready to connect
- View details
levelupSkillDev tools
Use after a correction or review finding worth remembering, when standards may have drifted from the live ecosystem, when switching MasterMind to a new domain or stack, or when the user says "remember this", "learn from that", "so you don't repeat it", "don't make that mistake again", "level up", "u
Ready to connect
- View details
linked-skillSkillDev tools
Symlinked user skill; discovery must follow the link to find this.
Ready to connect
- View details
lofn-replySkillDev tools
Write and post public replies and comments on social platforms (Suno, Instagram, NightCafe, anywhere the audience can see) in Lofn's actual voice, at the right length, under vault/COMMENT_REPLY_STANDARD.md. Use whenever replying to comments, clearing a comment backlog, answering a listener, thanking
Ready to connect
- View details
lofn-storySkillDev tools
Run the Lofn story/narrative pipeline (steps 00–10) backed by Codex — panel-driven prose, narrative voice, world-building, scripts. Use for stories, tales, narratives, flash fiction, scripts, or "write a story with the full pipeline". Expects a Phase-0/1 orchestrator packet from the `lofn` skill; if
Ready to connect
- View details
manage-game-stateSkillDev tools
Use when structuring a PlayCanvas game's control flow — a small state machine such as ready, playing, paused, and over, pointer-lock capture, pausing on focus or pointer-lock loss, a full reset, and a stable clock and timestep — so the loop stays deterministic and recoverable.
Ready to connect
- View details
oc-reportSkillDev tools
Internal bug report generator. Produces PII-redacted, structured reports formatted as GitHub issues. Called by other skills when errors are detected — not directly by users.
Ready to connect
- View details
oc-setupSkillDev tools
First-run setup wizard for clawed-back. Use when the user says 'setup', 'start clawed-back', 'initialize', or when running for the first time. Offers three install modes: portable user, portable root, or system install.
Ready to connect
- View details
oc-sslSkillDev tools
Set up SSL/HTTPS certificates using Let's Encrypt certbot. Use when the user says 'setup ssl', 'get certificate', 'enable https', 'certbot', 'letsencrypt', or wants to secure their ClawedBack instance with HTTPS on a public domain.
Ready to connect
- View details
oc-tokenSkillDev tools
View, regenerate, or set the auth token for the web chat. Use when the user says 'change token', 'reset token', 'show token', 'set password', 'new token', or 'auth token'.
Ready to connect
- View details
oc-toolsSkillDev tools
Execute tools and commands on behalf of the user from the web chat. Use internally when the router identifies a tool request. Do NOT invoke directly.
Ready to connect
- View details
oc-updateSkillDev tools
Pull the latest ClawedBack updates from GitHub and apply them to the running installation, preserving local config, data, auth tokens, and user-installed skills. Use when the user says 'update', 'upgrade', 'pull latest', 'check for updates', or 'oc-update'.
Ready to connect
- View details
oneSkillDev tools
Stale cached copy. If this node appears, discovery walked a non-installed version.
Ready to connect
- View details
organize-codex-projectsSkillDev tools
Choose a location and internal structure for a future Codex project, including focused projects and umbrella projects with durable subprojects. Use when creating or planning a new project. Do not move, rename, or normalize existing projects.
Ready to connect
- View details
over-engineeringSkillDev tools
Apply when writing or reviewing any change, when deciding whether a refactor or a simplification is worth making, when a helper, wrapper, flag, map, abstraction or mechanism is about to be added, and when a review's quality lane asks whether a thing earns its existence. Esposter catalogue of over-en
Ready to connect
- View details
override-shader-chunksSkillDev tools
Use when a PlayCanvas StandardMaterial needs custom shading its properties cannot express — procedural or stylized looks, custom vertex displacement, per-material screen effects — before writing a standalone shader from scratch.
Ready to connect
- View details
oxlintSkillDev tools
Apply when fixing lint errors, editing .oxlintrc.json, configuring vitest lint rules, investigating slow ESLint rules, writing a custom lint rule, adding an accessibility attribute to a template, or adding regexes, interface declarations or JSON parsing. Esposter oxlint + ESLint conventions — oxlint
Ready to connect
- View details
package-scriptsSkillDev tools
Apply when running or recommending any pnpm script. Esposter pnpm script reference — apps/web scripts (lint, typecheck, test, format, dev, build), a Settled list (no root build:<app> per app, the release as one local script, a renamed export never a major), nuxt typecheck and the root lint as the on
Ready to connect
- View details
phantomSkillDev tools
Marketplace catalogue entry for a plugin that was never installed. Must never be discovered.
Ready to connect
- View details
- View details
polish-beadsSkillDev tools
Polishing pass over all open beads. Run 4–6 times. "Check your beads N times, implement once." Use after plan-to-beads and between refinement rounds.
Ready to connect
- View details
pr-prepareSkillDev tools
Prepare or open a GitHub or Gitea pull request with an explicit AI-authorship disclosure, change classification, reproducible reviewer verification steps, and optional Mermaid diagram. Use whenever the user asks to prepare, write, open, create, push, ship, or get changes ready for a PR or review. Un
Ready to connect
- View details
provider-skill-nameSkillDev tools
Use this skill for a specific cloud workflow. Mention provider, trigger phrases, expected inputs, and when not to use it.
Ready to connect
- View details
prune-dead-codeSkillDev tools
Audit a codebase for dead and otherwise safe-to-remove code, and report each finding for approval. Use when asked to find dead or unused code, deduplicate repeated constants, replace magic literals that duplicate a named constant, or remove arbitrary caps, thresholds, or timeouts.
Ready to connect
- View details
quarantineSkillDev tools
Use whenever secrets or confidential material must be kept out of git: API keys, tokens, credentials, a client's internal patterns, private project data, real names, proprietary code. Triggers: "these keys must never end up in a commit", "make sure this never gets pushed", "this is sensitive", "don'
Ready to connect
- View details
react-codeSkillDev tools
Patterns and conventions for writing and editing React code, including components and hooks. Use this skill whenever writing or reviewing React components, hooks (useEffect, useCallback, useState), event handlers, or component extraction decisions. Also trigger when debugging stale closures, infinit
Ready to connect
- View details
readme-standardsSkillDev tools
Apply when creating or updating any README.md in this monorepo, including the root one. Esposter README conventions — the anchor+emoji heading template, badges driven by each manifest's published-vs-private split, the typedoc module-page link and its slug read off the generated output, when Getting
Ready to connect
- View details
reduce-draw-callsSkillDev tools
Use when a PlayCanvas application submits too many draw calls or frame time is CPU-bound — repeated meshes, dense grids, always-on interface elements — before hand-writing mesh merging or custom renderers.
Ready to connect
- View details
reflect-codex-workflowsSkillDev tools
Compare evidence from a current or completed project with installed skills and decide whether to reuse, revise, create, or not skill the lesson. Use for workflow reflection or proposed skill upgrades. Do not edit skills without explicit authorization.
Ready to connect
- View details
releasing-popkornSkillDev tools
Use when publishing @popkorn/* packages to npm — the changesets release flow, and why scripts/publish.ts exists and must not be simplified away.
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,249 of the 54,680 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.