Defame1297
8451169d2b
check-skill-version-bump fails a push when a skill directory changed against its merge-base with main (tests/ excluded) without a strictly higher metadata.version than main. New, renamed and deleted skills are exempt; every plugin is covered. Recorded as a dated section in ADR-0022 and documented in gates.md. Patch-bumps the 17 skills that changed on this branch without a bump, so the branch passes its own gate. Simplification audit finding 33. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
2.3 KiB
2.3 KiB
name, description, metadata
| name | description | metadata | |||||||
|---|---|---|---|---|---|---|---|---|---|
| apm-workflow | Use when authoring, installing, or publishing an apm package, its apm.yml and the dependencies it declares, or an apm marketplace — even when the user does not say "apm". Not the apm binary or an agent runtime -> `apm-install`. |
|
Gotchas
- MCP server secrets in
apm.yml(headers, env vars) must use${VAR}indirection, never literal values, so they resolve at install or runtime and are never committed. apm experimental enable registriesmust run before aregistries:block orregistry.*config takes effect anywhere — configure, install or publish. Without it, declaring one silently does nothing: no error, no warning.apm.yml'stype:selects which primitives are processed and is never checked against what.apm/holds, soapm installandapm compilecan exit 0 having shipped none of the ones you expected. Set it to cover every primitive the package ships, and confirm the deployed output, not the exit code. Mechanics:references/configure.md.
Step 1 — Dispatch
| Condition | Flow | Reference |
|---|---|---|
Author or edit apm.yml, or scaffold a new package (apm plugin init) |
configure | references/configure.md |
Resolve or fetch the dependencies apm.yml declares (apm install, apm install [PACKAGE_REF]) |
install | references/install.md |
Build a marketplace, register a package into it (local: hand-edit apm.yml; remote: apm marketplace package add), or register someone else's as a consumer (apm marketplace init/check/package add/add) |
marketplace | references/marketplace.md |
Generate per-target output, bundle, or publish (apm compile, apm pack, apm publish) |
compile | references/compile.md |
Validate integrity/policy or wire a CI gate (apm audit, apm audit --ci) |
audit | references/audit.md |
Read the reference file matching the resolved flow — it carries that flow's own traps, and names a sibling file wherever one flow genuinely depends on another's detail.
Step 2 — Execute
Follow the matched reference file's instructions. Report back which apm command(s) were run (or drafted, if the user asked for a plan rather than execution) and their outcome.