Found while vendoring these SDK skills verbatim (pinned at 3cb2086a607bbdf7d7eb2ec72e06ecd6a30a1415) into a downstream content catalog that preserves upstream relative paths byte-for-byte.
Every skills-legacy/<sdk>/SKILL.md opens with a breadcrumb linking ../../SKILL_TREE.md, which — climbing two levels from skills-legacy/<sdk>/ — resolves to the repository root. But scripts/build-skill-tree.sh writes the generated tree to src/SKILL_TREE.md, and there is no root-level copy in the repo at the pinned ref. The breadcrumb link resolves nowhere in-repo.
Consumers that vendor these skills verbatim (rather than the whole repo checkout) inherit a dead link with no way to fix it locally without diverging from upstream. Wanted to flag it in case the breadcrumb was meant to point at ../../src/SKILL_TREE.md, or the build script was meant to also emit a root-level copy.
Found while vendoring these SDK skills verbatim (pinned at
3cb2086a607bbdf7d7eb2ec72e06ecd6a30a1415) into a downstream content catalog that preserves upstream relative paths byte-for-byte.Every
skills-legacy/<sdk>/SKILL.mdopens with a breadcrumb linking../../SKILL_TREE.md, which — climbing two levels fromskills-legacy/<sdk>/— resolves to the repository root. Butscripts/build-skill-tree.shwrites the generated tree tosrc/SKILL_TREE.md, and there is no root-level copy in the repo at the pinned ref. The breadcrumb link resolves nowhere in-repo.Consumers that vendor these skills verbatim (rather than the whole repo checkout) inherit a dead link with no way to fix it locally without diverging from upstream. Wanted to flag it in case the breadcrumb was meant to point at
../../src/SKILL_TREE.md, or the build script was meant to also emit a root-level copy.