AgentKit
DocsKitsCLI ReferenceDesktop App
BetaYou are reading docs for the beta channel (3.0.0-beta.41). Features may change before the next stable release.Switch to stable →

ak skills kit

ak skills kit init

Create a personal kit manifest that extends exactly one kit version and declares no overlay or fork.

Use ak skills kit init to create the personal kit local/<name> under AGENTKIT_HOME/kits/personal/<name>. The new personal-kit.yaml extends one kit version and declares no overlay or fork. Add overlays and forks by editing the manifest, then preview with ak skills kit inspect. The command never projects or applies.

Usage

ak skills kit init <name> --extends <kit>@<version> [flags]

Options

FlagDefaultDescription
--extends <kit>@<version>requiredKit version to extend. It must resolve offline from --kits-dir.
--kits-dir <dir>$AGENTKIT_KITS_DIR or ./kitsFoundation kits directory.
--dry-runfalsePrint the manifest and write nothing.

Shared flags are described in CLI conventions.

Requirements

Without --dry-run the skill store must be on, after ak update --ssot or with AGENTKIT_SKILL_STORE=1; with it off the command exits 2. The command only touches AGENTKIT_HOME and follows its global scope from any directory. --dry-run works offline for every user.

What it writes

Under the kit lifecycle lock and after store recovery, the command writes AGENTKIT_HOME/kits/personal/<name>/personal-kit.yaml (mode 0644) in one journaled transaction that requires it to be absent. An existing directory of that name is refused, whatever it holds, and nothing is overwritten.

Output

The text output is one line: created (or would create on a dry run), the kit, the version it extends, its skill count and the manifest path.

JSON uses kind=skills.kit.init with these fields under data:

dryRun, personalKit, kit, version, path, manifest, skills

manifest is the YAML text of the new manifest and skills the number of skills the kit composes.

Exit behavior

ExitMeaning
0The manifest was written, or the dry run finished.
1Command failure, such as a path too long or a recovery that is required.
2The skill store disabled, invalid flags or arguments, or a malformed manifest.
4Another AgentKit operation holds the kit lifecycle lock.
5The kit version or a skill it ships was not found.
6A directory of that name already exists.
7Revoked foundation.