Quick start
Install the skills, check where they landed, and run a first prompt.
Requirements: Node.js 22+ (for npx), PowerShell 7+ (pwsh) for the skill scripts, gh for the GitHub and delivery skills. Check them with check-prerequisites (prerequisites).
Install
Install the installer skill once per machine:
bashnpx skills add GravionLabs/skills --skill skills-manage -g -yIn your agent, let it detect the stack and propose the groups (dry run first, it asks before installing):
text/skills-manage # this project: detects ts, py, dotnet, rust, go, angular /skills-manage core -g # user-wide: shared, github, delivery, statuslineWithout the agent:
pwsh ~/.claude/skills/skills-manage/scripts/Install-Skills.ps1 -DryRun.Or install single skills directly:
bashnpx skills add GravionLabs/skills --list # what is there npx skills add GravionLabs/skills --skill deliver --skill planner -a claude-code -a opencode npx skills add GravionLabs/skills#v1.0.0 --skill ts-implementation # pinned to a release
Updates: /skills-manage update (add -g for the global install), or directly npx skills check (exit 1 when one is available) and npx skills update. The skills CLI sends anonymous telemetry; DISABLE_TELEMETRY=1 turns it off.
Where things land
| Platform | Project | Global (-g) |
|---|---|---|
| Claude Code | .claude/skills/<name>/ | ~/.claude/skills/ |
| OpenCode | .agents/skills/<name>/ | ~/.config/opencode/skills/ |
| GitHub Copilot | .agents/skills/<name>/ | ~/.copilot/skills/ |
Commit skills-lock.json, .agents/skills/ and .claude/skills/ so a fresh clone has the skills. On Windows skills-manage copies instead of linking (symlinks need Developer Mode).
First prompts
Plan issue #42.
/deliver 42Plan issue #42. makes planner split the issue one level down; /deliver 42 implements, reviews and merges the open PBIs of issue 42 (delivery). More examples: stack setups.
To ship a milestone (cut release/next, deliver, release PR, ruleset): release a milestone.
Something stuck (a pause, a skipped PBI, a red check)? See troubleshooting.