Which one should you use?
Use GitHub when you want the files now — clone, open SKILL.md, or grab a pack that is not listed on skills.sh yet. Use skills.sh when you want the public directory and the install-once CLI. Use the shop companions when you want copy/download without cloning. None of those replace each other; they point at the same iruhdam1/skills pack.
skills.sh vs GitHub, side by side.
| Option | Source of truth | How you install | When a skill appears | What you can read | Best for |
|---|---|---|---|---|---|
| GitHub | The git repo | Clone, zip, or raw file | When the commit is pushed | Every pack folder and SKILL.md | Reading, cloning, agents that want the repo |
| skills.sh | Listing + install telemetry over that repo | npx skills add (and hub UIs that use it) | When the listing crawls / counts catch up | Listed packs and install counts — not a second git history | Discovering the pack and running the CLI add |
| Shop /skills | Companions generated from the shop | Copy or download on /skills/<pack> | When the shop page is published | Preview + download on the companion | One-file setup without cloning |
When GitHub is enough.
Clone github.com/iruhdam1/skills, open a pack’s SKILL.md, or fetch a pack-only skill that is not on skills.sh yet. Agents that want the repo as context should use GitHub.
When skills.sh helps.
Open skills.sh/iruhdam1/skills to discover the pack, run the CLI add, and see install counts. Do not “fix” a missing badge — that is telemetry lag, not a failed push.
When to use the shop page.
Copy or download on /skills without cloning. Companions include ghost-wireframe, website-launch-checklist-prompt, and responsive-preview, plus the pack-only pages on the same hub.
Install the pack.
npx skills@latest add iruhdam1/skills once. Or use the GitHub repo. Or start on /skills.