How do I install the Install Apm Package skill?

Run npx skillmds@latest add richfrem/install-apm-package in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Install Apm Package safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Install Apm Package?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Install Apm Package free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Install Apm Package?

richfrem (@richfrem) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Install Apm Package by richfrem — Agent Skill

Name: Install Apm Package
Rating: 4.2 (5 reviews)
Author: richfrem

Install Apm Package

Activate when the user wants to install, deploy, test, or materialize an APM package into runtime directories such as .agents/, .github/, .claude/, .cursor/, .gemini/, .codex/, .opencode/, or .windsurf/. Use after creating or converting an APM package.

richfrem 1ca69a7 5 files · 5.1 KB Updated Sep 10, 2026

File contents

install-apm-package Skill 🚀

Overview

This skill manages the safe deployment of APM primitives into their respective runtime environments. It enforces validation and target discovery to ensure byte-identical reproducibility across environments.

🚫 Non-Negotiables

Source Integrity — Never edit files in .agents/, .github/, or .claude/ directly. Always edit the source in .apm/ and re-install.
Lockfile Persistence — apm.lock.yaml MUST be committed after any install change.
Validation First — Always run validate_apm_package.py before executing the install.
Project Root Discipline — Run apm install from the project root to ensure converged skills land in the authoritative .agents/ folder. Running inside a package directory creates local, isolated artifacts.

Decision Tree

Global Activation? -> Run apm install ./path-to-package from the project root.
Isolated Testing? -> Run apm install from within the package directory.
Target Inferred? -> (e.g., .claude/ exists) -> Run apm install.
Ambiguous Target? -> (No signals) -> apm install will exit with code 2; ask user for explicit --target (e.g., agent-skills, claude, all).
Converged Skills? -> (Standard) -> Deploys to .agents/skills/. Use --target agent-skills for explicit skill deployment.
Legacy Skills? -> (Per-client paths) -> Use --legacy-skill-paths flag.
Production/CI? -> Use --frozen flag to ensure lockfile compliance.

Workflow

Verify apm.yml existence (locally or at root).
Execute python scripts/validate_apm_package.py.
Select Execution Context:
- For project-wide use: cd <repo-root>
- For local test: cd <package-dir>
Preview with apm install [--target <slug>] --dry-run --verbose.
Run apm install [./relative-path-to-pkg] [--target <slug>] [--legacy-skill-paths].
- Use --target all,agent-skills to deploy to all harnesses AND converged skills.
Verify apm.lock.yaml update at the execution root.

Duplicate Visibility Guardrail

Before recommending all,agent-skills, check whether the user is doing:

a routing smoke test, or
an actual day-to-day runtime install.

For smoke tests, all,agent-skills is appropriate. For real use, prefer the smallest target list that matches the runtime. Installing both converged and target-specific skills may cause duplicate skill visibility in runtimes that scan multiple skill locations.

Anti-Patterns

Manual Materialization: Moving files into .github/agents/ by hand instead of using apm install.
Ignoring the Lockfile: Failing to commit apm.lock.yaml after adding a dependency.
Editing Artifacts: Modifying the generated runtime output instead of the .apm/ source.

---name: install-apm-packagedescription: Activate when the user wants to install, deploy, test, or materialize an APM package into runtime directories such as .agents/, .github/, .claude/, .cursor/, .gemini/, .codex/, .opencode/, or .windsurf/. Use after creating or converting an APM package.---# install-apm-package Skill 🚀## OverviewThis skill manages the safe deployment of APM primitives into their respective runtime environments. It enforces validation and target discovery to ensure byte-identical reproducibility across environments.## 🚫 Non-Negotiables1. **Source Integrity** — Never edit files in `.agents/`, `.github/`, or `.claude/` directly. Always edit the source in `.apm/` and re-install.2. **Lockfile Persistence** — `apm.lock.yaml` MUST be committed after any install change.3. **Validation First** — Always run `validate_apm_package.py` before executing the install.4. **Project Root Discipline** — Run `apm install` from the **project root** to ensure converged skills land in the authoritative `.agents/` folder. Running inside a package directory creates local, isolated artifacts.## Decision Tree1. **Global Activation?** -> Run `apm install ./path-to-package` from the **project root**.2. **Isolated Testing?** -> Run `apm install` from within the package directory.3. **Target Inferred?** -> (e.g., `.claude/` exists) -> Run `apm install`.4. **Ambiguous Target?** -> (No signals) -> `apm install` will exit with code 2; ask user for explicit `--target` (e.g., `agent-skills`, `claude`, `all`).3. **Converged Skills?** -> (Standard) -> Deploys to `.agents/skills/`. Use `--target agent-skills` for explicit skill deployment.4. **Legacy Skills?** -> (Per-client paths) -> Use `--legacy-skill-paths` flag.5. **Production/CI?** -> Use `--frozen` flag to ensure lockfile compliance.## Workflow1. Verify `apm.yml` existence (locally or at root).2. Execute `python scripts/validate_apm_package.py`.3. **Select Execution Context**: - For project-wide use: `cd <repo-root>` - For local test: `cd <package-dir>`4. Preview with `apm install [--target <slug>] --dry-run --verbose`.5. Run `apm install [./relative-path-to-pkg] [--target <slug>] [--legacy-skill-paths]`. - Use `--target all,agent-skills` to deploy to all harnesses AND converged skills.6. Verify `apm.lock.yaml` update at the execution root.## Duplicate Visibility GuardrailBefore recommending `all,agent-skills`, check whether the user is doing:1. a routing smoke test, or2. an actual day-to-day runtime install.For smoke tests, `all,agent-skills` is appropriate. For real use, prefer the smallest target list that matches the runtime. Installing both converged and target-specific skills may cause duplicate skill visibility in runtimes that scan multiple skill locations.## Anti-Patterns- **Manual Materialization**: Moving files into `.github/agents/` by hand instead of using `apm install`.- **Ignoring the Lockfile**: Failing to commit `apm.lock.yaml` after adding a dependency.- **Editing Artifacts**: Modifying the generated runtime output instead of the `.apm/` source.

Frequently asked questions