メニュー
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.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Guide an agent through verifying and completing an akm upgrade — reading migration notes, running config and storage migrations, updating stash assets that reference deprecated commands, and confirming the system is healthy. Use after `akm upgrade` or after manually installing a new akm version.
Consolidate, prune, and reorganize akm memories with explicit staged review gates. Use when the user says "dream", "/dream", "auto dream", "consolidate memories", "clean up my memories", "prune stale memories", or "my memory files are a mess". For routine consolidation without staged review, prefer `akm improve memory` + `akm extract --auto` directly.
Produce well-formatted markdown health reports for the akm improve pipeline, interpret metrics, troubleshoot issues, and tune pipeline behavior. Use when the user asks for a health report, wants to understand improve metrics, diagnose slow/silent/failing runs, or tune consolidation and distillation.
Given a user goal, search all configured stash sources and registries, compare overlapping assets, run a security review on candidates, select the best, and clone them into a new reviewable directory the user can add as a stash or import piecemeal. Use when the user says 'build me a stash for X', 'find the best assets for Y', 'curate a toolkit for Z', or 'assemble assets to help me with...'
Use when the user wants to install or clone an akm stash or individual asset from npm, GitHub, a git URL, or a local directory into their working stash.
Use when the user wants to publish a new akm stash so it appears in the official registry and remains useful to agents using akm-cli v0.8.0.
| 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" |
This skill gets an agent from zero to a working akm installation so subsequent skills can run without setup errors.
akm is not on PATH.akm info or akm --version fails.command -v akm && akm --version && akm info || true
If akm is present and akm info succeeds, skip to step 4.
Prefer the package manager already used in the environment:
bun add -g akm-cli@latest
# or: npm install -g akm-cli
# or: pnpm add -g akm-cli
For environments without Node, use the standalone installer from the akm README.
akm setup
# or, for a non-interactive flow:
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.
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
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.reflect / distill / proposal * / vault commands are removed
or deprecated — do not use them in new automation.