| 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" |
Publish an akm Stash
This skill walks an agent through turning a directory of assets into a
searchable, installable stash.
1. Lay out the 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/
2. Write search-friendly metadata
- Give every skill, command, agent, workflow, and lesson a trigger-sentence
description.
- Add a root
akm.json when you want stash-level metadata.
- For benchmark or fixture content, teach how to do the work, not the exact
answer to a single verifier.
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.
3. Pick a publish path
npm package
Add "akm-stash" to keywords in package.json and publish.
GitHub topic
Add the akm-stash topic and keep the repo public, documented, and licensed.
Manual registry entry or override
Open a PR against itlackey/akm-registry
when you need a curated manual entry or metadata override.
4. Verify listing and installability
akm registry search <your-stash>
akm add <your-ref>
akm index
akm show <ref-from-your-stash>
5. Release hygiene
- Tag releases so users can pin a known-good version.
- Keep README copy oriented to agents, not marketing.
- Ship
.env.example files instead of real secrets.
- Review proposal-generated changes before release; do not publish draft
quality: "proposed" content as if it were final.
- If you ship
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.
