omd:migrate
Skill588 starsChanged 35 days agoMITView on GitHub
Legacy deep-reference writer safety gate. Use for old brand migration requests only to prevent retired section/frontmatter writes until the Core v2 catalog migration pipeline is authoritative.
In this repository89 other files it gives its agents.
- AGENTS.mdAGENTS.md
- web/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- web/CLAUDE.mdCLAUDE.md
- ego-browserSkill
- google-analyticsSkill
- omd:add-referenceSkill
- omd:batch-launchSkill
- omd-component-harvestSkill
- omd:designSkill
- omd-lab-01-designmd-impactSkill
- omdSkill
- omd-token-backfillSkill
- claude-designSkill
- hangulSkill
- omd:add-referenceSkill
- omd:aphroditeSkill
- omd:applySkill
- omd:asset-fetchSkill
- omd:autopilotSkill
- omd:batch-launchSkill
- omd:cjk-type-shaderSkill
- omd:codex-imageSkill
- omd-component-harvestSkill
- omd:designer-reviewSkill
- omd:experiment-gallerySkill
- omd:feelSkill
- omd:final-qaSkill
- omd:harnessSkill
- omd:humanizeSkill
- omd:initSkill
- omd:issueSkill
- omd:kr-writerSkill
- omd-lab-01-designmd-impactSkill
- omd-lab-02-design-harnessSkill
- omd:landingSkill
- omd:learnSkill
- omd:locale-adapterSkill
- omd:mediaSkill
- omd:migrateSkill
- omd:orchestratorSkill
- omd:reference-captureSkill
- omd:release-hygieneSkill
- omd:rememberSkill
- omd:restraintSkill
- omd:setupSkill
- omd:shader-heroSkill
- omd:showcaseSkill
- omdSkill
- omd:slop-auditSkill
- omd:syncSkill
- omd:tasteSkill
- omd-token-backfillSkill
- omd:updateSkill
- claude-designSkill
- hangulSkill
- omd-3d-heroSkill
- omd-aphroditeSkill
- omd-applySkill
- omd-asset-fetchSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 23
Do not mutate web/references/<id>/DESIGN.md, its frontmatter, numbered sections, verification footer, or mirrors.
- Very specific: line 29
Do not adopt or overwrite its staged result.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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
omd:migrate — catalog write safety gate
Scope, narrowed by owner decision 2026-09-16. This gate blocks writes that
create a new legacy reference or a new Core catalog package. It does not
block refreshing evidence on an existing reference — verification_v2,
.verification.md, tokens.components state values, ## Proof — because that
produces no Core package and adds no migration debt; the file stays legacy and
stays in the same queue. Creating a reference, adding a brand, restoring a legacy
YAML marker, emitting retired section output, placeholder sentinels, or hand-editing
generated counts and mirrors all remain refused. Full rationale and the two expiry
conditions: .claude/skills/omd-add-reference/SKILL.md.
CORE_V2_CATALOG_WRITE_BLOCKED
Do not mutate web/references/<id>/DESIGN.md, its frontmatter, numbered
sections, verification footer, or mirrors. Those files remain readable during
the migration window, but creating more legacy bytes would violate the Core v2
dual-read/single-write contract.
For a provider-free assessment, use the Core migration auditor in check mode.
Do not adopt or overwrite its staged result. A migration candidate keeps the
source DESIGN.md canonical until a graph-backed catalog writer, migrated
consumers, evidence binding, and dropped_segments=0 acceptance ship together.
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.

