Skip to content

feat(skills): vendor skills-CLI packages via lockfile - #113

Open
mikeastock-bot wants to merge 1 commit into
mainfrom
feat/skills-cli-lock-vendor
Open

feat(skills): vendor skills-CLI packages via lockfile#113
mikeastock-bot wants to merge 1 commit into
mainfrom
feat/skills-cli-lock-vendor

Conversation

@mikeastock-bot

Copy link
Copy Markdown
Collaborator

Summary

  • Bridge npx skills into this repo’s install pipeline: packages are locked in skills-lock.json, staged under gitignored .agents/skills/, and vendored as copies into skills/ for the existing multi-agent build/install flow.
  • Add Make targets (skill-add, skill-vendor, skill-update, skill-sync) and scripts/skill_lock.py.
  • Vendor github/gh-stack as the first locked skill; document the workflow in README and AGENTS.md; cover the bridge with tests.

Usage

make skill-add SOURCE=github/gh-stack
make skill-add SOURCE=owner/repo SKILL=name
make skill-update
make skill-sync   # restore from lockfile, then vendor
make install      # distributes skills/ to agent home dirs as usual

Test plan

  • ./tests/test-skill-lock.sh (19 assertions)
  • make skill-add SOURCE=github/gh-stack SKILL=gh-stack vendors into skills/gh-stack/
  • python3 scripts/build.py build includes gh-stack for amp/claude/pi
  • make install-skills installs gh-stack into agent skill dirs
  • make skill-sync re-fetches from lockfile when staging is empty

Bridge npx skills into this repo's install pipeline: lock packages in
skills-lock.json, stage under .agents/, and vendor copies into skills/
so make install stays multi-agent and offline. Add gh-stack as the first
locked skill with Makefile helpers and tests.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants