placement-protocol
Skill0 starsChanged 5 months agoNo licenceView on GitHub
The deliberate gate every named friction passes through after it is extracted and before it is installed as a skill. Resolves the four structural questions — organizing scheme, arc-phase, trigger condition, staffed-or-orphan verdict — and writes the result to the Skill Registry, the single structured source of truth for the ecosystem. Runs socratic by default (questioning the person through each placement to train structural instinct) with an autonomous escape hatch. The complement of cognitive-friction-extractor — the extractor NAMES the friction, this skill PLACES it. Invoke with /place to smelt a batch of named-but-unplaced frictions, and /map to regenerate the SVG zone projection from the registry on demand.
In this repository17 other files it gives its agents.
- carousel-engineSkill
- cognitive-friction-extractorSkill
- core-extractorSkill
- crystalliseSkill
- distillSkill
- fuse-deltaSkill
- handoffSkill
- intakeSkill
- intuition-forgeSkill
- moultSkill
- occams-razorSkill
- ossifySkill
- Prompt Engine Interface ContractSkill
- ruptureSkill
- spinal-columnSkill
- typographySkill
- ui-contractSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “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.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
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.