skill
Skill0 starsChanged 29 days agoMITView on GitHub
The entry point to Skill Builder, what it can do, which skill fits a request, setup and a health check. Use when unsure where to start with building or testing skills.
- Installs packages
62 other projects use a version of this.
Adopted by
Most recently taken up by
- HelloRuru/claude-teams-gotheir own version, first seen Nov 8, 2026
- TheAlejo160/orchestratheir own version, first seen Nov 8, 2026
- blamechris/chroxytheir own version, first seen Nov 8, 2026
- nexoral/AxioDBtheir own version, first seen Nov 8, 2026
- Yeachan-Heo/oh-my-claudecodetheir own version, first seen Nov 8, 2026
- szarkans/multitheir own version, first seen Nov 2, 2026
Used with
Projects with it also use ai-slop-cleaner, ralplan and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
Jurel89Skillai-slop-cleaner
Clean AI-generated code slop with a regression-safe, deletion-first workflow and optional reviewer-only mode
Also in 5 projects that use this
ibahgatSkillralplan
Create a strict, quality-first execution plan with explicit gates and rollback-ready sequencing.
Also in 5 projects that use this
- ibahgatSkill
hud
Control omi visual HUD profile and keep status output readable in normal, compact, or hidden mode.
Also in 5 projects that use this
- Jurel89Skill
ultraqa
QA cycling loop — build/lint/test, fix, retry up to 5 cycles
Also in 3 projects that use this
LucasCooperBeySkillvisual-verdict
Structured visual QA verdict for screenshot-to-reference comparisons. Returns JSON scores driving edit iterations. Use after any UI implementation to verify visual fidelity.
Also in 3 projects that use this
Yeachan-HeoSkillultragoal
Create and execute durable repo-native multi-goal plans over Codex goal mode artifacts.
Also in 3 projects that use this
Other versions62 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 62
- Yeachan-Heo/oh-my-claude-sisyphus★ 41ksame name
- Yeachan-Heo/oh-my-claudecode★ 41ksame name
- Yeachan-Heo/oh-my-codex★ 34ksame name
- tradecatlabs/vibe-coding-cn★ 18ksame name
- tukuaiai/vibe-coding-cn★ 18ksame name
- liyue-aigc/female-portrait-director★ 1.6ksame name
- sundial-org/skills★ 151same name
- build23w/fdv.lol★ 128same name
- builders-toronto/fdv.lol★ 128same name
- redf0x1/camofox-mcp★ 124same name
52 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository19 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- skill-benchSkill
- skill-checkSkill
- skill-competeSkill
- skill-createSkill
- skill-descriptionSkill
- skill-evalSkill
- skill-factsSkill
- skill-improveSkill
- skill-learnSkill
- skill-packageSkill
- skill-planSkill
- skill-pluginSkill
- skill-publishSkill
- skill-releaseSkill
- skill-repoSkill
- skill-tidySkill
- skill-tokensSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 45 edited versions we read keep these.
2
Distinctive
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
- Distinctive: line 42
When two could fit, ask which outcome they want in one short question rather than guessing.
- Distinctive: line 58
When something doesn't work, check before guessing:
- Very specific: line 69
Keep a short log of each job in .agents/skill/runs/<skill>/run.md: what was agreed, what was checked, what passed.
“Common” is measured: kept by at least 6 in 10 of the 45 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Skill Builder
You help people build skills and plugins that work in every AI tool, and prove it with numbers rather than a look. Work out what the person wants, then follow the skill that does it. When that skill isn't installed here, read its steps below and do them yourself: every step runs on the same engine.
The engine
Counting, checking and testing are done in code, so the same skill gets the same result every time. Run it as:
npx -y @thenavidm/skill-builder@latest <command>It needs Node 22 or newer and installs nothing permanent. Where it's installed globally (npm install -g @thenavidm/skill-builder), skill-builder <command> is the same engine without the download. Add --json to any command when you need to read the result rather than show it.
What to use
| They want | Skill | Engine |
| A new skill, from a goal, this conversation, a screen recording or a brief | skill-create | check, trigger, eval |
| A whole plugin: several skills, agents, an entry skill | skill-plugin | repo, check, trigger, install |
| A repository set up to publish a plugin | skill-repo | repo new, package |
| To know why a skill doesn't fire, or fires on the wrong things | skill-description | trigger |
| A skill fixed | skill-improve | check, eval |
| A working skill tidied without changing what it does | skill-tidy | check, tokens, eval |
| A correction applied everywhere it belongs | skill-learn | eval |
| To beat a skill someone else made | skill-compete | overlap, eval |
| To see whether a skill helps at all | skill-eval | eval |
| The same tests in every AI tool they use | skill-bench | bench |
| What their skills cost on every message | skill-tokens | tokens |
| A skill or plugin checked against every tool's rules | skill-check | check |
| Sources behind every claim a skill makes | skill-facts | |
| A plan before building: which skills, which agents, which scripts | skill-plan | tokens |
| Every tool's manifest from one source | skill-package | package |
| A new version that reaches every user | skill-release | changelog, release |
| The repository on GitHub with a clear description and topics | skill-publish | repo publish |
When two could fit, ask which outcome they want in one short question rather than guessing.
Setup
The first time in a project, ask these one at a time and write the answers to .agents/skill/setup.md, which every skill reads before it starts. Skip any question the project already answers: look at its files first.
- Which AI tools they and their users use. Tests run in those.
- Where their skills live: a plugin repository, this project, or their user folder.
- A short prefix every skill name starts with, so their skills never clash with another plugin's. One lowercase word, such as
seo. - Their house rules: writing style, licence, anything that must never go in a repository.
- Whether they publish, and where.
The file is plain Markdown. Tell them they can edit it any time.
Doctor
When something doesn't work, check before guessing:
node --versionis 22 or newer.- Which AI tools answer:
claude --version,codex --version,gemini --version,agy --version. Tests can only run in tools that are installed and signed in. - Auto-update is on for this plugin, so fixes reach them. In Claude Code,
/pluginshows it; for the others, see the update guide.
Name the fix for each thing that fails, in plain words.
How to work
- Show the cost before anything that runs prompts: each test is a real request on their own account. The engine prints the number of runs first.
- Keep a short log of each job in
.agents/skill/runs/<skill>/run.md: what was agreed, what was checked, what passed. If a job stops halfway, read the log and carry on from the first unfinished step instead of starting again. - Anything that reaches a live system (GitHub, npm, a marketplace) asks first, for that one step.
- Report results as the numbers the engine gave, with what they mean. Don't round a failure into a pass.
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.