Filed out-of-scope from the #7251 skills-optimization flight — that flight's file surface was skills/objectui/** plus its move destinations, so it could not touch content/docs/. Unassigned.
What is stale
content/docs/guide/agent-skills.md draws the skill's layout as an ASCII tree. Two of its rows name files that #7251 moved out of the published bundle into a repo-internal skill:
- line ~47 —
│ └── no-touch-zones.md, under rules/
- line ~59 —
│ └── console-development.md, under guides/
Both now live under .claude/skills/objectui-contributor/. A third row is also stale: evals/console-development.json was deleted in the same change, per the package's own invariant that an eval is renamed or removed with its guide.
content/docs/guide/ci-cd-pipeline.md (~line 578) also describes console-development.md as the file whose deliberate negative sentence is the sole scripts/skills-path-baseline.json entry. That entry is gone — the gate demanded its deletion once the guide left the scan root — so the sentence describes a baseline that is now empty.
Why no gate caught it
check-doc-links.mjs scans content/docs, but these are lines inside a fenced ASCII tree, not markdown links, so there is nothing for it to resolve. check-skills-paths.mjs reads code spans in prose under skills/ only. Nothing connects the two, which is the same blind spot #7358 is about from the other side.
The fix
Redraw the tree from the tree, and say where the contributor-only content went and why — a customer install has no apps/console/ and no packages/components/src/ui/, which is the reason those two files left. Correct the ci-cd-pipeline.md sentence to describe an empty ratchet rather than a one-entry one.
Small, but it is the page a reader consults to learn what the skill contains, so being wrong about the contents is the one thing it cannot afford.
Filed out-of-scope from the #7251 skills-optimization flight — that flight's file surface was
skills/objectui/**plus its move destinations, so it could not touchcontent/docs/. Unassigned.What is stale
content/docs/guide/agent-skills.mddraws the skill's layout as an ASCII tree. Two of its rows name files that #7251 moved out of the published bundle into a repo-internal skill:│ └── no-touch-zones.md, underrules/│ └── console-development.md, underguides/Both now live under
.claude/skills/objectui-contributor/. A third row is also stale:evals/console-development.jsonwas deleted in the same change, per the package's own invariant that an eval is renamed or removed with its guide.content/docs/guide/ci-cd-pipeline.md(~line 578) also describesconsole-development.mdas the file whose deliberate negative sentence is the solescripts/skills-path-baseline.jsonentry. That entry is gone — the gate demanded its deletion once the guide left the scan root — so the sentence describes a baseline that is now empty.Why no gate caught it
check-doc-links.mjsscanscontent/docs, but these are lines inside a fenced ASCII tree, not markdown links, so there is nothing for it to resolve.check-skills-paths.mjsreads code spans in prose underskills/only. Nothing connects the two, which is the same blind spot #7358 is about from the other side.The fix
Redraw the tree from the tree, and say where the contributor-only content went and why — a customer install has no
apps/console/and nopackages/components/src/ui/, which is the reason those two files left. Correct theci-cd-pipeline.mdsentence to describe an empty ratchet rather than a one-entry one.Small, but it is the page a reader consults to learn what the skill contains, so being wrong about the contents is the one thing it cannot afford.