skills.sh.json and skills/wordpress/SKILL.md exist in this repo and in brmbh/cli, byte-for-byte identical, with nothing keeping them in sync.
diff brmbh-cli/skills.sh.json brmbh-wordpress/skills.sh.json → identical
diff brmbh-cli/skills/wordpress/SKILL.md brmbh-wordpress/skills/wordpress/SKILL.md → identical
Neither repo has CI (.github/ does not exist in either), so nothing detects the drift when one side is edited.
Which copy should go
Per the two-layer rule decided in brmbh/cli#6:
The CLI owns the pre-scaffold skill (Layer 1). The theme owns in-project skills (Layer 2). Neither is duplicated.
skills/wordpress/SKILL.md is Layer 1 — it documents how to install and drive the CLI: npx create-brmbh, npm install -g @brmbh/cli, the doctor --json envelope, brmbh create flags, Local by Flywheel troubleshooting. It targets a machine where this theme does not exist yet. skills.sh.json even declares "name": "@brmbh/cli".
So: this repo deletes both files. Layer 2 — AGENTS/*.md and the generated wrappers — stays here and is unaffected.
Why the content is guaranteed to drift
SKILL.md documents CLI command surface: flags, the doctor JSON shape, the full command reference. Every one of those changes when brmbh/cli changes. The copy in this repo has no reason to be updated at that moment, so it silently goes stale — and it is the copy people are more likely to find, since this is the more discoverable of the two repos.
Tasks
Note
SKILL.md also carries a stale pre-migration path (brmbh create <name> --from /path/to/brmbh-agentic-wp-suite). Deleting this copy removes half the problem; the surviving copy in brmbh/cli still needs it fixed — tracked at brmbh/cli#4.
Related: brmbh/cli#5, brmbh/cli#6
skills.sh.jsonandskills/wordpress/SKILL.mdexist in this repo and in brmbh/cli, byte-for-byte identical, with nothing keeping them in sync.Neither repo has CI (
.github/does not exist in either), so nothing detects the drift when one side is edited.Which copy should go
Per the two-layer rule decided in brmbh/cli#6:
skills/wordpress/SKILL.mdis Layer 1 — it documents how to install and drive the CLI:npx create-brmbh,npm install -g @brmbh/cli, thedoctor --jsonenvelope,brmbh createflags, Local by Flywheel troubleshooting. It targets a machine where this theme does not exist yet.skills.sh.jsoneven declares"name": "@brmbh/cli".So: this repo deletes both files. Layer 2 —
AGENTS/*.mdand the generated wrappers — stays here and is unaffected.Why the content is guaranteed to drift
SKILL.mddocuments CLI command surface: flags, the doctor JSON shape, the full command reference. Every one of those changes when brmbh/cli changes. The copy in this repo has no reason to be updated at that moment, so it silently goes stale — and it is the copy people are more likely to find, since this is the more discoverable of the two repos.Tasks
git rm skills.sh.json skills/wordpress/SKILL.md(andskills/if it empties)AGENTS.md, which currently documents only the in-project skills and reads as if they are the whole storyNote
SKILL.mdalso carries a stale pre-migration path (brmbh create <name> --from /path/to/brmbh-agentic-wp-suite). Deleting this copy removes half the problem; the surviving copy in brmbh/cli still needs it fixed — tracked at brmbh/cli#4.Related: brmbh/cli#5, brmbh/cli#6