القائمة
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.
التثبيت باستخدام 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 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.
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 | install-akm-stash |
| description | 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. |
| updated | "2026-05-24T00:00:00.000Z" |
This skill is for adding a stash to the user's working stash so its assets
(skills, commands, agents, knowledge, workflows, wikis, env configs, secrets, memories,
lessons) become searchable and usable via akm show, akm workflow, akm tasks,
or host-agent plugins.
Prerequisite: run skill:akm-quickstart first if akm info fails.
akm curate "<keywords>" first; if needed,
fall back to akm search "<keywords>" --source registry.akm add.akm clone <ref>.akm search "kubernetes deploy" --source registry
akm add github:owner/kubernetes-stash
akm update
akm index
akm add npm:@acme/review-stash
akm show skill:code-review
akm add git+https://github.com/owner/repo.git#v1.2.3
akm add ./path/to/stash --name local-stash
akm clone github:owner/repo//skill:deploy
akm clone npm:@acme/stash//lesson:docker-healthchecks
akm list
akm search <asset-name>
akm show <ref> --shape agent
For private GitHub repos, set GITHUB_TOKEN in the environment or a secret.
Secret values are never accepted on argv (that would leak via /proc/cmdline);
store them as a secret and inject via env:
# Store as a whole-file secret:
printf '%s' "$GITHUB_TOKEN" | akm secret set secret:github-token
# Or store in an env asset and inject when needed:
akm env run env:user -- akm add github:your-org/private-stash
akm add github:your-org/private-stash
akm add, run akm index.quality: "proposed" content as draft material until it is accepted.