Summary
skill.sh's SKILLS associative array uses folder-derived keys for several skills, while README.md's "Install name" column (which matches each skill's name: frontmatter in its SKILL.md) documents different values for the same skills. Example mismatches:
| Skill |
skill.sh key |
README "Install name" |
| taste-skill |
taste-skill |
design-taste-frontend |
| taste-skill-v1 |
taste-skill-v1 |
design-taste-frontend-v1 |
| image-to-code-skill |
image-to-code-skill |
image-to-code |
| redesign-skill |
redesign-skill |
redesign-existing-projects |
| soft-skill |
soft-skill |
high-end-visual-design |
| output-skill |
output-skill |
full-output-enforcement |
| minimalist-skill |
minimalist-skill |
minimalist-ui |
| brutalist-skill |
brutalist-skill |
industrial-brutalist-ui |
| stitch-skill |
stitch-skill |
stitch-design-taste |
(gpt-taste, imagegen-frontend-web, imagegen-frontend-mobile, and brandkit are consistent between the two.)
Why flag it
A user who runs source ./skill.sh <name> using the README's documented install name (e.g. design-taste-frontend) won't find a match, since the script's keys are folder names instead.
Question for maintainer
Is this intentional (i.e. skill.sh is meant to use folder names as a separate local-dev convenience, distinct from the npx skills add --skill install names), or should the keys be aligned with the README's install-name column? Happy to open a PR once the intended behavior is confirmed.
Disclosure: filed with AI assistance (Claude Code), after a repo-wide scan turned up no other issues to report.
Summary
skill.sh'sSKILLSassociative array uses folder-derived keys for several skills, whileREADME.md's "Install name" column (which matches each skill'sname:frontmatter in itsSKILL.md) documents different values for the same skills. Example mismatches:skill.shkeytaste-skilldesign-taste-frontendtaste-skill-v1design-taste-frontend-v1image-to-code-skillimage-to-coderedesign-skillredesign-existing-projectssoft-skillhigh-end-visual-designoutput-skillfull-output-enforcementminimalist-skillminimalist-uibrutalist-skillindustrial-brutalist-uistitch-skillstitch-design-taste(
gpt-taste,imagegen-frontend-web,imagegen-frontend-mobile, andbrandkitare consistent between the two.)Why flag it
A user who runs
source ./skill.sh <name>using the README's documented install name (e.g.design-taste-frontend) won't find a match, since the script's keys are folder names instead.Question for maintainer
Is this intentional (i.e.
skill.shis meant to use folder names as a separate local-dev convenience, distinct from thenpx skills add --skillinstall names), or should the keys be aligned with the README's install-name column? Happy to open a PR once the intended behavior is confirmed.Disclosure: filed with AI assistance (Claude Code), after a repo-wide scan turned up no other issues to report.