Skip to content

npx gstack-skills — standalone skill manager for gstack (upgrade + install without setup) #863

Closed as not planned

Description

@zzzhizhia

Hey! I built gstack-skills — a lightweight CLI for managing gstack skills without running the full setup:

npx gstack-skills

What it does:

  • Shallow-clones this repo, diffs against local ~/.claude/skills/
  • Interactive upgrade: shows changelog, lets you update all / pick / skip
  • Interactive install: discovers new skills with descriptions, checkbox selection (space: toggle, a: all)
  • Safe: backs up before updating, restores on error
  • Zero dependencies on bun or the setup script

Who it's for:

  • Users who want to try individual gstack skills without committing to a full setup
  • Quick upgrades without git pull + ./setup
  • Environments where bun isn't available

It currently discovers all 34 skills correctly from the repo.

Repo structure blocks per-skill discovery on skills.sh

skills.sh (npx skills add) is the standard way to discover and install individual skills from a GitHub repo. But npx skills add garrytan/gstack --list returns only 1 skill (the root meta-skill), because its discoverSkills() finds the root SKILL.md and early-returns without scanning subdirectories.

--full-depth works (npx skills add garrytan/gstack --list --full-depth → 37 skills), but users won't know to pass that flag.

Suggested fix: move skill directories into a skills/ subdirectory. The skills CLI's search path priority list includes skills/, so it would automatically discover all sub-skills after the root SKILL.md. This also helps with #267 and #594.

Related: #113, #267, #594

Activity

  1. time-attack commented on Jul 15, 2026

    @time-attack
    Contributor

    @16francej — recommend closing this issue as a duplicate of #113, which already owns per-skill installation. The third-party package cited here is useful prior art, but not a safe canonical implementation. Please preserve the standalone-install demand and integrity, ownership, rollback, symlink, runtime-sidecar, and Windows-copy requirements in #113.

  2. capy-ai commented on Oct 8, 2026

    @capy-ai
    Contributor

    Thanks for sharing. Closing in favor of #113, which tracks per-skill installation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions