compiling-entities
Skill2 starsChanged 7 months agoMITView on GitHub
Compiles a comprehensive entry for a named entity by scanning ALL files, gathering every mention, and assembling a structured profile. Use when building out a full entry for any character, species, location, or concept, or when user says "compile", "flesh out", "full entry for", or "everything about [entity]". Does NOT extract multiple entities from one source — use /extracting-entities.
In this repository19 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- auditing-canonSkill
- auditing-human-assumptionsSkill
- auditing-physicsSkill
- canon-rulesSkill
- cross-checkingSkill
- deep-readingSkill
- deriving-social-systemsSkill
- designing-loreSkill
- designing-worldsSkill
- extracting-entitiesSkill
- integrating-researchSkill
- interrogating-designSkill
- planning-worldbuildingSkill
- researching-papersSkill
- verifying-completionSkill
- writing-scienceSkill
- writing-styleSkill
- writing-worldbuildingSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
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 20
Search GLOSSARY.md, then grep all .md files for the entity name
- Distinctive: line 21
Read FULL content of every file mentioning the entity
- Distinctive: line 28
Does NOT extract multiple entities from one source (use /extracting-entities).
- Distinctive: line 29
Does NOT write original content (use /writing-worldbuilding).
≈ “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
Compiling Entities
Assemble all information about a named entity from across the entire repo.
Process
- Search GLOSSARY.md, then grep all .md files for the entity name
- Read FULL content of every file mentioning the entity
- Compile into structured profile with sources cited
- Flag contradictions between sources
- Present for author review — do NOT write without approval
Out of Scope
Does NOT extract multiple entities from one source (use /extracting-entities). Does NOT write original content (use /writing-worldbuilding).
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.

