Summary
Six references across four files point to a skill named hz-vrc-check, but skills/hz-vrc-check/ does not exist in this repository. Two of the references are markdown links to ../hz-vrc-check/SKILL.md, which 404. One reference lists hz-vrc-check in a "skill inventory" used by another skill (hz-quest-verify-first) for routing decisions.
Net effect: any agent that follows hz-store-submit is instructed to "invoke hz-vrc-check for a detailed walkthrough" of VRC compliance — which it cannot do, because the skill is not packaged.
Evidence
$ ls skills/ | grep -i vrc
$ # (no output — directory not present)
$ grep -rn "hz-vrc-check" . | grep -v .git/
skills/hz-store-submit/SKILL.md:23:This skill references the [hz-vrc-check](../hz-vrc-check/SKILL.md) skill for detailed VRC validation. If hz-vrc-check is installed, invoke it for thorough compliance testing before proceeding to submission.
skills/hz-store-submit/SKILL.md:96:Run through the VRC checklist. If the `hz-vrc-check` skill is installed, invoke it for a detailed walkthrough. Key VRC categories:
skills/hz-store-submit/SKILL.md:202:- [VRC Compliance (hz-vrc-check skill)](../hz-vrc-check/SKILL.md) -- Detailed VRC validation checklist
skills/hz-store-submit/references/submission-checklist.md:25:- [ ] Completed VRC checklist (use hz-vrc-check skill for full walkthrough)
skills/hz-quest-verify-first/SKILL.md:292:- `hz-vrc-check` — store-publishing and VRC compliance validation
skills/hz-android-2d-porting/references/compatibility-requirements.md:268:2. **Store assets**: Prepare all required assets before starting submission (see `hz-vrc-check` for full specs):
Impact
- Broken markdown links (2):
skills/hz-store-submit/SKILL.md lines 23 and 202 link to a missing SKILL.md. They render as broken links on GitHub.
- Misleading agent routing (1):
skills/hz-quest-verify-first/SKILL.md:292 lists hz-vrc-check in the skill inventory used by hz-quest-verify-first to decide which skills to invoke for which task — so an agent following hz-quest-verify-first will believe a store-VRC-validation skill is available when it is not.
- Dead cross-skill workflow:
hz-store-submit defers VRC detail work to hz-vrc-check, so the store-submission flow has no actual VRC checklist beyond the high-level categories listed inline.
Suggested fix
Two options:
- Add the missing skill — create
skills/hz-vrc-check/SKILL.md with the VRC checklist content the other skills are already routing to.
- Remove the references — strip the 6 references and inline a minimal VRC checklist into
hz-store-submit (or wherever needed), so users/agents are not pointed at a non-existent skill.
Option 1 is preferable because the other skills (hz-store-submit, hz-quest-verify-first, hz-android-2d-porting) are clearly designed around it existing.
Summary
Six references across four files point to a skill named
hz-vrc-check, butskills/hz-vrc-check/does not exist in this repository. Two of the references are markdown links to../hz-vrc-check/SKILL.md, which 404. One reference listshz-vrc-checkin a "skill inventory" used by another skill (hz-quest-verify-first) for routing decisions.Net effect: any agent that follows
hz-store-submitis instructed to "invokehz-vrc-checkfor a detailed walkthrough" of VRC compliance — which it cannot do, because the skill is not packaged.Evidence
Impact
skills/hz-store-submit/SKILL.mdlines 23 and 202 link to a missingSKILL.md. They render as broken links on GitHub.skills/hz-quest-verify-first/SKILL.md:292listshz-vrc-checkin the skill inventory used byhz-quest-verify-firstto decide which skills to invoke for which task — so an agent followinghz-quest-verify-firstwill believe a store-VRC-validation skill is available when it is not.hz-store-submitdefers VRC detail work tohz-vrc-check, so the store-submission flow has no actual VRC checklist beyond the high-level categories listed inline.Suggested fix
Two options:
skills/hz-vrc-check/SKILL.mdwith the VRC checklist content the other skills are already routing to.hz-store-submit(or wherever needed), so users/agents are not pointed at a non-existent skill.Option 1 is preferable because the other skills (
hz-store-submit,hz-quest-verify-first,hz-android-2d-porting) are clearly designed around it existing.