Writing skills
Writing abilities for your coding agent, ranked by what people actually install. Every skill is a folder: your agent fetches one link, reads SKILL.md, and knows how to do the job.
0 skills · 0 installs all-time · 0 in the last 24 hours
Skills here are live, not mirrored files. Installs pin to a version, updates ship as new versions with diffs, and authors see real install counts. How that works →
0 skills · ranked by all-time installs
No approved skills yet. The directory grows as the community publishes.
Built something useful? Submit it as a skill — that's how this list grows.
These skills are live — a repo mirror can't do this
Directories that point at git repos serve you a snapshot of someone's files and lose track of it the moment you copy it. Here the skill folder itself is the source of truth, so the directory can do three things a mirror never will:
Version pinning
Installing pins your agent to the exact version it fetched. The skill never changes underneath you — you upgrade when you choose, with a diff of what changed.
Versioned updates
When an author publishes a new version, the changelog and per-file diff are right on the skill page. Tell your agent "update it" and it re-fetches the same link.
Honest install counts
The install counts above are real manifest fetches served by us, deduplicated per agent per day — not a scraper's guess over a pile of READMEs.
Why it matters: the numbers above are counted by the same server that serves the skills.
Built something useful? Submit it.
Most skills here started as someone's private folder. If yours saves you an hour a week, it will save someone else one too. A skill is just a folder with a SKILL.md — if you have that, you're ready.
Share your skill folder
Paste the share link of any skill folder in your workbench. Name and description come from its SKILL.md.
AI review reads every file
An AI reviewer reads every file, checks scripts for anything that phones home or touches files it shouldn't, and writes a risk note.
A human publishes it
We read the risk note, not your code style. Published skills stay yours — updates ship as new versions and installs stay pinned.
Community skills are labeled as such and never pretend to be audited — the review catches obvious risk, you keep the credit.
What is a skill?
A skill is a folder your agent can install. Inside is a SKILL.md — plain markdown that tells the agent when to act and what to do — plus any scripts, references, and assets the job needs. No SDK, no plugin API, no marketplace lock-in.
Installing takes one prompt: your agent fetches the skill's link, reads SKILL.md, and downloads the files it references. Installs pin to the version they fetched, so a skill never changes underneath you; when the author publishes an update, you choose when to take it.
Because skills are folders, you can read every line before you install — and you should: community skills are not audited; Workbench is not responsible; read all the code before installing. Every skill above links to a full rendered page with its complete SKILL.md, file list, and version history, so you can read before you decide.
Which agents can these skills work with?
Any agent that can fetch a URL — Claude Code, Cursor, Codex, and self-built agents all install the same way, from the same link. There is no per-agent package format to maintain.
How are the rankings counted?
All-time ranks by total installs since publish. Trending ranks by installs in the last 24 hours. Hot ranks by momentum — 24-hour installs relative to the skill's size, which is how new skills surface before they have big totals. Counts are real manifest fetches served by us, deduplicated per agent per day.