Overview
GravionLabs/skills is a library of reusable skills in the agentskills.io SKILL.md format, installed with npx skills. One skill source loads unchanged on Claude Code, OpenCode and GitHub Copilot. Workflows are skills. The skill deliver chains them from issue to merged PR, see delivery.
This documentation is also published as a site at https://gravionlabs.github.io/skills/.
What a group gives you
A group is a set of skills for one domain, listed in .claude-plugin/marketplace.json. Installing it copies (or links) the skills into your repository, where the agent picks them up by their description or when you name them. /skills-manage resolves the groups for a project; npx skills add GravionLabs/skills --skill <name> installs single skills.
| Group | What it covers |
|---|---|
shared | implementation (tests per change), detect-techstack, code-review (blocking findings and notes), diagnose (bug diagnosis), check-prerequisites, lessons (approved project lessons per role), adr (ADR with the next free number, see governance) |
delivery | deliver, planner, grill-me, retro, skills-manage |
github | github-issue ([Objective] → Epic → Feature → PBI hierarchy with native sub-issues), github-pull-request, github-release, github-milestone (milestones M<nnn>, renamed M<nnn> (x.y.z) on close: current and all with their progress, create, close after the release tag) |
dotnet | dotnet-implementation, dotnet-test, dotnet-create-solution, dotnet-mcp-server-generator, dotnet-aspire (AppHost for local orchestration) |
ts | ts-implementation, ts-test, ts-create-project, ts-mcp-server-generator, ts-pnpm-workflow, setup-biome-husky, setup-prettier-eslint-husky |
py | py-implementation, py-test, py-create-project |
rust | rust-implementation, rust-test |
go | go-implementation, go-test |
ng | ng-implementation, ng-test, ng-create-project, ng-ag-grid |
statusline | context-statusline: status line and subagent status line |
skill-tooling | skill-write, skill-audit, skill-slim (contributor tooling, not in the all preset) |
Presets of /skills-manage: core (shared, github, delivery, statusline, for the global install) and all (every group except skill-tooling). The full list with descriptions is generated into skill-list.md.
How the skills fit together
detect-techstack names the language skills, implementation and code-review dispatch to them, and planner and deliver sit on top; github-issue is the entry point for issue work. The diagram is on skill composition, the issue hierarchy and labels on the issue model.
Skills delegate by name instead of repeating each other. One skill owns a workflow; the others call it.
Where to go next
- Quick start: install the skills and run a first prompt
- Skills: how skills load on each platform and how they are structured
- Skill composition and issue model: how the skills call each other, and the Objective, Epic, Feature, PBI and Bug hierarchy with its labels
- Skill frontmatter convention: the restricted frontmatter that keeps skills portable
- Stack setups, work an issue by hand and fix a bug: end-to-end examples with the installed skills
- Learn from runs:
retro, lessons and the flow diagram - ADRs and specs: how the
governancekey tiesadr,planner,implementation,code-review,deliverand CI together - Skill companion directories:
scripts/,references/,templates/,assets/ - Plan an issue, work an issue by hand and delivery: one issue per session, and delivery through
/deliver - herdr with the skills: pane tokens, sidebar layout and the herdr plugins for
/deliver - Prerequisites: tools the skill scripts depend on
- LSP configuration: language servers for Copilot CLI
- CONTRIBUTING.md and AGENTS.md: adding or changing skills
Guiding principles
- One
SKILL.md≤ 100 lines; long material lives inreferences/, procedures inscripts/. - Rules the model does not already know: repo conventions, tool contracts, repeatable procedures. No generic tutorials.
- Compose, don't duplicate.
- The agent proposes, the developer approves.