skill-author
Skill0 starsChanged 4 months agoMITView on GitHub
Creates a new Claude Skill to fable-mythos standard - a tight SKILL.md plus eval cases and an example. Use when the user wants to turn a repeated workflow, a giant pasted prompt, or a recurring task into a reusable skill.
24 other projects use a version of this.
Adopted by
Most recently taken up by
- tailcallhq/skillstheir own version, first seen Nov 16, 2026
- himkt/cafleettheir own version, first seen Nov 12, 2026
- DylXBT/claude-orchestrator-skillstheir own version, first seen Nov 8, 2026
- pankaj-mahaur/Agent-Daemontheir own version, first seen Nov 6, 2026
- educlopez/mallardtheir own version, first seen Nov 1, 2026
- mandasTeam/skill-authortheir own version, first seen Nov 1, 2026
Other versions24 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 24
- generative-computing/mellea★ 1.9ksame name
- aqm857886159/Nomi★ 550same name
- DylXBT/claude-orchestrator-skills★ 114same name
- robium-ai/robium★ 93same name
- himkt/cafleet★ 56same name
- Lethe044/agentskill-kit★ 50same name
- manusco/resonance★ 38same name
- Zhonghao1995/agentic-swmm-workflow★ 31same name
- felvieira/claude-skills-fv★ 28same name
- peter-tu-zynkr/zynkr-skill-builder★ 21same name
14 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 repository5 other files it gives its agents.
- agent-task-compilerSkill
- linkedin-signal-postsSkill
- skill-repair-loopSkill
- video-prompt-directorSkill
- voice-capsuleSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 19 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 18
One skill, one job: If the workflow splits into two jobs, split the skill or build the more repeated half.
- Distinctive: line 21
Self-check: before delivering: description triggerable?
“Common” is measured: kept by at least 6 in 10 of the 19 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 Author
Mission
Turn a repeated workflow into a skill package a cheaper model can execute. Prompts are temporary; skills compound — but only if they're small, testable, and honest about failure.
Step zero
Confirm the workflow is actually repeated. A one-off task gets an answer, not a skill — building a skill for something done once is how prompt libraries fill with corpses.
Workflow
- Description first. It does the triggering: name the task, the artifacts involved, and 3–4 phrasings a user would actually type. A skill that never fires is dead regardless of quality.
- Body under 60 lines: mission (2 lines) · workflow (≤7 numbered steps, each operational — a step that can't fail isn't a step) · rule precedence (explicit user requests beat style rules; say it) · output format (≤5 sections).
- Bulk goes to reference files. Voice, long examples, templates →
examples.mdin the skill folder, loaded on demand. If the user pasted a 2,000-word prompt, compress the logic into the skill and move the rest — never transcribe. - One skill, one job. If the workflow splits into two jobs, split the skill or build the more repeated half.
- Write ≥4 evals (JSONL: id, type, input, expected, failure_to_prevent): at least one messy real-world input and one adversarial (the user asks for something the skill should resist).
- Write 1 example showing input → ideal output, annotated.
- Self-check before delivering: description triggerable? · every workflow step falsifiable? · body ≤60 lines? · adversarial eval present? · no "you are a world-class expert" preamble? · nothing the executor model can't follow?
Boundaries
Refuse skills engineered for dishonesty — auto-10/10 self-graders, fake-engagement generators, sycophancy by design. An evaluator that can't fail the work isn't a skill, it's a rubber stamp.
Output format
SKILL.md (complete)
evals/<name>.jsonl (complete)
examples/<name>-example.md (complete)
Handoff note
Where each file goes in the repo + the reminder: the skill gets good through the repair loop on the executor model, not through this authoring 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.

