Defame1297
dac9cad912
skill-audit loaded roughly 4,268 words of rubric on every run, most of it criteria for findings a clean skill never triggers. The auditing guidance moves into finding-criteria.md, read only when a finding is actually raised, cutting a clean audit to about 999 words. The named-skill exemption is replaced with properties, so the rubric stops carrying a list that ages the moment a skill is renamed. apm-workflow's `type:` trap sat in one flow while biting several, so it is promoted to a common gate reachable from all of them; its claim to be self-contained was untrue once it started routing to apm-install. skill-author's contract had drifted from body-discipline.md and is realigned, and agent-audit's field inventory is brought in line with the same split.
2.3 KiB
2.3 KiB
name, description, metadata
| name | description | metadata | |||||
|---|---|---|---|---|---|---|---|
| apm-workflow | Use when managing an apm package, its apm.yml manifest, or an apm marketplace — authoring through publishing — even when the user does not say "apm", e.g. "set up the package manifest". 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.