verifying-completion
Skill2 starsChanged 7 months agoMITView on GitHub
Runs a mandatory completion checklist before declaring any worldbuilding task finished. Catches missing frontmatter, broken cross-references, unlinked glossary terms, and deferral language. Use after writing any content, before reporting task complete, or when user says "is this done", "verify", "check my work", or "completion check". Does NOT write content — only verifies.
In this repository19 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- auditing-canonSkill
- auditing-human-assumptionsSkill
- auditing-physicsSkill
- canon-rulesSkill
- compiling-entitiesSkill
- cross-checkingSkill
- deep-readingSkill
- deriving-social-systemsSkill
- designing-loreSkill
- designing-worldsSkill
- extracting-entitiesSkill
- integrating-researchSkill
- interrogating-designSkill
- planning-worldbuildingSkill
- researching-papersSkill
- writing-scienceSkill
- writing-styleSkill
- writing-worldbuildingSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
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 37
Does NOT write content. Does NOT audit the full repo.
≈ “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
Verifying Completion
Mandatory checklist before declaring ANY worldbuilding task complete.
Checklist
For EVERY file created or modified:
- Frontmatter — YAML with title, tags, status
- Content — No TODO, placeholder, TBD, "will flesh out", empty sections
- Cross-References — All links resolve, relative paths correct
- Glossary & Timeline — New terms in GLOSSARY.md, events in MASTER-TIMELINE.md, _index.md updated
- Canon Consistency — Obeys upstream science, naming correct, no contradictions
- Writing Standards — Academic prose in science dirs, no meta-commentary
Red Flags — DO NOT Declare Complete If:
- Any section heading has no content below it
- Any cross-reference doesn't resolve
- "placeholder" or "TODO" appears anywhere
- A new term was introduced but not added to GLOSSARY.md
Out of Scope
Does NOT write content. Does NOT audit the full repo.
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.