GSKILL Documentation

GSKILL is a reproducible package manager for agentic AI skills. It installs, versions, locks, verifies, and restores SKILL.md instruction bundles across AI coding agents, developer machines, and CI. Skill content is committed in the repository, so a fresh git clone yields working skills with zero gskill commands; commit skills-lock.json — the single file that records both intent and resolved reality — and prove or restore a byte-identical skill environment anywhere with gskill install --frozen-lockfile.

These pages are also published, with search, at https://glapsfun.github.io/gskill/.

This documentation follows the Diátaxis framework — four kinds of docs, each with one job.

📚 Start here

If you want to…	Go to
Install GSKILL on Linux or macOS	Installation
Learn GSKILL from scratch, step by step	Tutorial: Getting started
Do a specific task (recipes with examples)	How-to guides
Look up a command, flag, exit code, or file format	Reference
Understand how and why GSKILL works	Explanation

Tutorial

A single guided lesson from an empty directory to a committed, reproducible skill environment.

• Getting started

How-to guides

Problem-oriented recipes — one per feature. See the full index. Highlights:

• Install a local skill
• Add a skill from Git
• Reproduce exactly with --frozen-lockfile
• Verify integrity
• Customize a skill without forking it
• Gate CI on drift
• Reuse skills across projects
• Script GSKILL with --json

Reference

Authoritative, exhaustive lookup.

• Commands — generated from the CLI
• Exit codes — generated from the CLI
• Configuration
• skills.toml manifest
• skills-lock.json lockfile schema
• SKILL.md frontmatter schema
• Supported agents

Explanation

Understanding-oriented discussion.

• The reproducibility model
• The package lifecycle
• Integrity and trust
• Repo-owned storage
• Project state vs global state
• The clone cache
• Multi-agent installs

---

The two reference pages marked generated are produced by go run ./cmd/gen-reference and must not be hand-edited — they are kept in lockstep with the tool by a golden test in CI.