skills
AGENTS.md7 starsChanged 5 days agoMITView on GitHub
A public collection of agent skills, published on skills.sh. Each skill is a directory skills/<name>/ in the one skills plugin, with SKILL.md and optional references/, scripts/, examples/. The branch, PR, publish, and test workflow lives in CONTRIBUTING.md; read it before changing anything in this repository. The description in each SKILL.md is the authoritative trigger; this table is a map. With skills (all skills, or pick with -s): With skl-x, the same arguments plus a summary table, or symlinks from a…
Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.
Of the AGENTS.md files we read, the 31,774 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository29 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- branch-finishSkill
- commit-allSkill
- cross-reviewSkill
- dashfixSkill
- debuggingSkill
- echartsSkill
- frontend-craftingSkill
- gh-switchSkill
- git-worktree-isolationSkill
- inline-plan-devSkill
- maintaining-agent-contextSkill
- negafixSkill
- parallel-agentsSkill
- plan-craftingSkill
- prose-craftingSkill
- review-requestSkill
- review-resolutionSkill
- scope-checkSkill
- scope-triageSkill
- secret-hygieneSkill
- skill-craftingSkill
- subagent-plan-devSkill
- tddSkill
- typescriptSkill
- verification-gateSkill
- vitestSkill
- webapp-debuggerSkill
- web-debugSkill
The file
We split this AGENTS.md into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 75
All skills ship in the skills plugin.
≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
AGENTS.md
A public collection of agent skills, published on
skills.sh. Each skill is a directory
skills/<name>/ in the one skills plugin, with SKILL.md and optional
references/, scripts/, examples/. The branch, PR, publish, and test workflow lives in
CONTRIBUTING.md; read it before changing anything in this repository.
Skills
| Skill | Use when |
scope-triage | a request needs design decisions before code |
plan-crafting | an approved design needs a multi-step implementation plan |
git-worktree-isolation | deciding whether work needs an isolated workspace or worktree |
inline-plan-dev | executing a plan in the current session |
subagent-plan-dev | executing a plan through coordinated subagents |
parallel-agents | several units of work might run concurrently through agents |
tdd | implementing testable behavior changes, test first |
debugging | investigating bugs, failures, flaky or unexpected behavior |
review-request | an implementation needs an independent review against its requirements and diff |
cross-review | a plan or implementation needs review by other agent CLIs (by default the opposite of Codex and Claude Code, plus Antigravity) |
review-resolution | review findings or PR comments need validation before any fix |
verification-gate | work is about to be called done, fixed, or mergeable |
branch-finish | verified work is ready to merge, push, open a PR, or discard |
scope-check | a saved Markdown file needs an HTML preview and README index entry |
prose-crafting | drafting or editing English or Ukrainian prose |
dashfix | writing prose or auditing typographic dashes |
negafix | writing prose or auditing "it's not just X, it's Y" constructions |
skill-crafting | designing, creating, evaluating, or retiring agent skills |
echarts | building or debugging Apache ECharts charts |
frontend-crafting | building or reviewing user-facing interfaces |
web-debug | testing or debugging a local web app with Playwright |
vitest | configuring, writing, or debugging Vitest tests |
typescript | compiler errors, tsconfig, typing, and module resolution problems |
maintaining-agent-context | creating or auditing AGENTS.md, CLAUDE.md, and other agent instructions |
secret-hygiene | using credentials from env files or config with real services |
gh-switch | a project-scoped gh command is about to run on github.com, or a GitLab API call in a project with a GitLab remote |
commit-all | the user asks to commit all current changes without a message |
webapp-debugger | slash-only: testing or debugging a local web app with agent-browser |
The description in each SKILL.md is the authoritative trigger; this table is a map.
Install
With skills (all skills, or pick with -s):
npx skills add sentimony/skills -a codex claude-code -y
npx skills add sentimony/skills -s tdd cross-review -a codex claude-code -yWith skl-x, the same arguments plus a summary table, or symlinks from a local clone so edits apply without reinstalling:
npx -y skl-x add sentimony/skills -s tdd cross-review -a codex claude-code -y
npx -y skl-x sln <clone>/skills -a codex claude-code -yAs a Claude Code plugin from sentimony/marketplace:
claude plugin marketplace add sentimony/marketplace
claude plugin install skills@sentimonyAs a Codex plugin:
codex plugin marketplace add sentimony/marketplace
codex plugin add skills@sentimonyAll skills ship in the skills plugin; this repository hosts no marketplace. After a release,
sentimony/marketplace bumps the skills entry ref to the new vX.Y.Z tag. Plugin skills are
namespaced by their plugin: /skills:scope-triage.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

