extracting-entities
Skill2 starsChanged 7 months agoMITView on GitHub
Extracts individual entities from a large source document and creates separate .md files for each one. Use when a source contains multiple distinct entities that should each have their own file, or when user says "extract", "pull out entities", "split this file", or "create files from this source". Does NOT compile scattered info about one entity — use /compiling-entities for that.
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
- 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 19
Read the ENTIRE source file
- Distinctive: line 27
Never write files until extraction plan is approved
- Distinctive: line 32
Does NOT compile scattered info about one entity (use /compiling-entities).
- Distinctive: line 33
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
Extracting Entities
Pull distinct entities from a source document into individual files.
Process
- Read the ENTIRE source file
- Identify every distinct entity needing its own file
- Present extraction plan for approval before writing
- Extract with YAML frontmatter (status: draft), cross-references
Rules
- One entity per file
- Never write files until extraction plan is approved
- Preserve source content faithfully — do not summarize
Out of Scope
Does NOT compile scattered info about one entity (use /compiling-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.