<skill_name>
Skill0 starsChanged 55 days agoMITView on GitHub
One job, written clearly enough for an agent to execute. Typed inputs + a deterministic verification step + a rollback reference. This file may edit itself when a better approach is found ("update this file when you learn something").
1 other project uses a version of this.
Adopted by
Most recently taken up by
- jaydubya818/ClaudeClaw-Mission-Controltheir own version, first seen Nov 8, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- jaydubya818/ClaudeClaw-Mission-Control★ 0same name
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 repository2 other files it gives its agents.
- templates/AGENTS.mdAGENTS.md
- create-ai-agentSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
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
- Distinctive: line 26
If verification fails → return to model with the failure, or route to human-in-the-loop.
- Very specific: line 29
Before any state change, checkpoint via .checkpoint/.
- Distinctive: line 33
After a run, if a better approach is found, update this file.
- Distinctive: line 34
Do NOT apply unverified changes to this skill.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill 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
Skill: <skill_name>
Job (one sentence)
<WHAT_THIS_EMPLOYEE_DOES>
When to use
<TRIGGER / TASK_TYPE_FROM_RESOLVER>
Inputs (typed — Pydantic at the door)
field_a(type):<meaning>field_b(type):<meaning>
Procedure
- <deterministic step — in code/tool where possible>
- <model step — taste/judgment only>
- <call tool / write artifact>
- Verify (deterministic gate): <how we know it worked — tests, types, ontology check>
- If verification fails → return to model with the failure, or route to human-in-the-loop.
Rollback / Save Button
- Before any state change, checkpoint via
.checkpoint/. - Accept only if the metric/check improved; otherwise revert.
Self-improvement
- After a run, if a better approach is found, update this file.
- Do NOT apply unverified changes to this skill.
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.