meta-map
Skill1 starsChanged 45 days agoNo licenceView on GitHub
Use when a map entry is missing, wrong, over-firing or never firing; when a node is created, split or retired; when the learning agent's proposals reach the pioneer; or when deciding how kit knowledge should be found. Governs layer 2 — MAP.md, the always-loaded index from named moments to the knowledge each one calls for.
In this repository17 other files it gives its agents.
- meta-antidrift-expandSkill
- meta-antidriftSkill
- meta-bootstrapSkill
- meta-casebookSkill
- meta-contract-artifactSkill
- meta-contract-before-executionSkill
- meta-correction-logSkill
- meta-drift-eventlogSkill
- meta-extractSkill
- meta-foundationSkill
- meta-founding-contractSkill
- meta-learningSkill
- meta-ledgerSkill
- meta-manifestSkill
- meta-mechanismsSkill
- meta-skill-builderSkill
- meta-understandingSkill
The file
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.