Defame1297
60be7b3232
Only 12 of 39 skills carried metadata.version, and adoption tracked which plugin a skill lived in rather than any stated rule: core, gitea and lint were consistent adopters, bin and kyberforge were consistent non-adopters, git was split with one outlier. There was no documented convention, and skill-author's own bump logic was already written as if presence were conditional. metadata.version is now required on every skill. The 19 skills here that never carried one (bin, kyberforge, gitea-files) are seeded at 1.0.0, not 0.1.0 -- that value stays reserved for a skill's actual creation point under skill-author's existing convention. The skill-frontmatter pre-commit hook now fails a SKILL.md missing the field, the same class of failure as a missing name/description. Full rationale in the new ADR. The git-plugin skills that also need this field follow in the next commit, bundled with issue #113's rtk normalization since both touch the same files. Refs: #127 ADR: 0022 Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01EeH8SCbcrCAQrtymkNuhKP
apm-install
Installs and configures the apm (Agent Package Manager) CLI and the agent runtimes it manages.
What it does
Covers the two provisioning steps for working with apm: installing the apm binary itself (quick-install script, pinned version, air-gapped mirror, or pip/pipx), and installing/managing an agent runtime apm drives (apm runtime setup copilot|codex|gemini|llm, listing installed runtimes, checking which one apm run defaults to).
Usage
/apm-install
Once apm and a runtime are in place, use apm-workflow for authoring apm.yml, scaffolding packages/marketplaces, compiling, packing, publishing, and auditing.
Files
| File | Purpose |
|---|---|
SKILL.md |
Skill instructions for agents |
references/sources.md |
Provenance chain — research sources that informed this skill |