| name | akm-quickstart |
| description | Use when an agent needs to bootstrap akm in a fresh environment: install the CLI, initialize the stash, configure discovery, and verify the toolchain before install, search, improve, or tasks operations. |
| updated | "2026-05-23T00:00:00.000Z" |
akm Quickstart
This skill gets an agent from zero to a working akm installation so subsequent
skills can run without setup errors.
When to use
- The user asks you to use akm and
akm is not on PATH.
akm info or akm --version fails.
- The working stash does not exist yet.
Steps
1. Detect current state
command -v akm && akm --version && akm info || true
If akm is present and akm info succeeds, skip to step 4.
2. Install the CLI
Prefer the package manager already used in the environment:
bun add -g akm-cli@latest
For environments without Node, use the standalone installer from the
akm README.
3. Initialize the stash
akm setup
akm init
akm index
Expected type directories include scripts/, skills/, commands/,
agents/, knowledge/, workflows/, memories/, env/, secrets/, wikis/,
lessons/, and tasks/ when you start authoring scheduled jobs.
4. Verify the official registry is reachable
akm registry list
akm registry search akm
If the registry is empty, add the official one explicitly:
akm registry add https://raw.githubusercontent.com/itlackey/akm-registry/main/index.json --name official
5. Confirm readiness
akm info
akm help migrate 0.8.0
akm proposal list
Only proceed once akm info succeeds. On 0.8.0:
akm proposal list and akm extract --auto --dry-run should both work.
- The old
reflect / distill / proposal * / vault commands are removed
or deprecated — do not use them in new automation.