القائمة
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.
التثبيت باستخدام 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 install or clone an akm stash or individual asset from npm, GitHub, a git URL, or a local directory into their working stash.
| name | publish-akm-stash |
| description | 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. |
| updated | "2026-05-23T00:00:00.000Z" |
This skill walks an agent through turning a directory of assets into a searchable, installable stash.
Use conventional directories when possible:
my-stash/
README.md
LICENSE
akm.json
scripts/
skills/<name>/SKILL.md
commands/
agents/
knowledge/
workflows/
lessons/
tasks/
memories/
env/
secrets/
wikis/
description.akm.json when you want stash-level metadata.Prefer inline metadata in frontmatter and file-local comments. Treat
.stash.json as legacy compatibility content rather than the default authoring
path on 0.8.0.
Add "akm-stash" to keywords in package.json and publish.
Add the akm-stash topic and keep the repo public, documented, and licensed.
Open a PR against itlackey/akm-registry when you need a curated manual entry or metadata override.
akm registry search <your-stash>
akm add <your-ref>
akm index
akm show <ref-from-your-stash>
.env.example files instead of real secrets.quality: "proposed" content as if it were final.tasks/, verify they use the current YAML task format
(tasks/<id>.yml) with schedule: and exactly one of workflow:,
prompt:, or command: — and the akm tasks CLI, not older
experimental examples. Legacy .md task files are warned and silently
skipped by the loader.