skill-factory
Skill4 starsChanged 6 months agoApache-2.0View on GitHub
Create a new re_gent skill from a plain-language description, writing a valid SKILL.md. Use when the user wants a new skill, or to build one that style-factory proposed.
14 other projects use a version of this.
Adopted by
Most recently taken up by
- jac2206/agentic-skillstheir own version, first seen Nov 15, 2026
- Szotasz/marveentheir own version, first seen Nov 14, 2026
- hamgarian/loot-skilltheir own version, first seen Oct 25, 2026
- kannaka-labs/Kannaktopustheir own version, first seen Oct 13, 2026
- superXdev/skillstheir own version, first seen Sep 15, 2026
- akijain2000/skill-factorytheir own version, first seen Sep 5, 2026
Other versions14 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 14
- nyldn/claude-octopus★ 4.4ksame name
- Szotasz/marveen★ 136same name
- ITSpecialist111/Copilot-Cowork-Skills★ 48same name
- immacualate/claude-forge★ 5same name
- akijain2000/skill-factory★ 4same name
- echoleesong/claude-skills-plugin★ 4same name
- jac2206/agentic-skills★ 4same name
- shivamd1810/claude-skill-factory★ 4same name
- hamgarian/loot-skill★ 2same name
- kingjly/skill-factory★ 2same name
4 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 repository14 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- blameSkill
- logSkill
- showSkill
- blameSkill
- bug-blameSkill
- context-primerSkill
- file-couplingSkill
- logSkill
- regent-skillsSkill
- rewindSkill
- showSkill
- style-factorySkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 2 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 13 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 15
Before writing, be able to answer in one sentence each:
- Distinctive: line 25
If the request is vague, ask one question.
- Very specific: line 30
Use Glob to list .claude/skills/*/SKILL.md (or the active host's matching skills directory), then read any neighbour that looks close.
- Very specific: line 57
Prefer real commands you have verified exist: Check with rgt <cmd> --help before referencing a flag.
“Common” is measured: kept by at least 6 in 10 of the 13 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
Turn a description into a working skill file.
A skill is a prompt plus a tool grant. The intelligence is the agent's, the data is re_gent's, and the skill is the wiring between them — so writing one is mostly deciding what to ask for and what it is allowed to run.
1. Settle the shape
Before writing, be able to answer in one sentence each:
- Trigger — when should an agent reach for this? This becomes
description, and it is the single most important line in the file: it is what the agent matches against. Name the situation, not the mechanism. - Input — a path, a step hash, a symptom, nothing? This becomes
argument-hint. - Data — which
rgtcommands supply the facts. - Output — what the user should be holding at the end.
If the request is vague, ask one question. A skill built on a guess triggers at the wrong moment and is worse than no skill.
2. Check it is not already there
Use Glob to list .claude/skills/*/SKILL.md (or the active host's matching
skills directory), then read any neighbour that looks close.
Extending an existing skill beats adding a near-duplicate — two skills with overlapping descriptions make the agent pick badly.
3. Write it
.claude/skills/<kebab-case-name>/SKILL.md:
---
description: <what it does + when to use it, one sentence>
allowed-tools: Bash(rgt <command> *)
argument-hint: "<arg>"
---
<Instructions to the agent.>Rules that matter:
- Grant the narrowest tools that work.
Bash(rgt log *)— never bareBash. A skill that only reads should never be able to write. - Write instructions, not prose. The reader is an agent about to act.
- Say what to do with the data, not just how to fetch it. The gathering is the easy half; the analysis is the skill.
- Prefer real commands you have verified exist. Check with
rgt <cmd> --helpbefore referencing a flag. A skill that cites a flag that does not exist fails at the moment it is trusted. - Name sibling skills the agent should chain to, so skills compose.
4. Verify before claiming it works
rgt <each command in allowed-tools> --helpConfirm every command and flag exists. Then state plainly what you could not test — a skill's real behaviour only shows when an agent runs it against real history.
Report
Path written, the description line verbatim (so the user can judge when it will
trigger), the commands it may run, and one example invocation.
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.

