Skip to content
Back to skills

Install Apm Package

ASecurity

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.

  • 7 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added September 2, 2026
ai-agentspythonbashtestinggit

Works with

  • cursor
  • cli

Security analysis

A100/100

Pro scans all 5 files and shows the line behind each finding

Scanned October 3, 2026

npx -y skills add richfrem/agent-plugins-skills --skill install-apm-package --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Install Apm Package?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Install Apm Package
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/richfrem-install-apm-package/badge)](https://www.skillsdirectory.com/skills/richfrem-install-apm-package)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: install-apm-package
description: >-
  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.
allowed-tools: Bash, Read, Glob
---

# Install APM Package (`install-apm-package`)

Manages the safe deployment and materialization of APM package primitives into target client runtimes (.agents/, .claude/, .github/, etc.) with lockfile reproducibility.

## Contents

- [Critical Constraints](#critical-constraints)
- [Quick start](#quick-start)
- [Workflow](#workflow)
- [Verification](#verification)
- [References](#references)

## Critical Constraints

1. **Source Integrity**: Never edit deployed files in `.agents/`, `.github/`, or `.claude/` directly. Always edit the source package and re-install.
2. **Lockfile Enforcement**: `apm.lock.yaml` must be committed after install modifications. Use `--frozen` in CI.
3. **Validation Pre-Condition**: Always run `validate_apm_package.py` before executing installations.
4. **Project Root Discipline**: Run `apm install` from project root for converged skills (`.agents/skills/`).

## Quick start

Preview deployment targets and actions without mutating files:

```bash
apm install --dry-run --verbose
```

## Workflow

1. **Pre-Check**: Verify `apm.yml` exists and run validation helper.
2. **Select Context**: Choose project root (for standard converged skills) or package directory (for isolated testing).
3. **Execute Installation**: Run `apm install [./path-to-pkg] [--target <slug>]`.
   - Prefer minimal target lists for real use to avoid duplicate skill visibility in multi-client runtimes.
4. **Persist Lockfile**: Ensure `apm.lock.yaml` is updated and staged.

## Verification

Validate installed package integrity and lockfile compliance:

```bash
python3 scripts/validate_apm_package.py --check-lockfile
```

## References

- [acceptance-criteria.md](references/acceptance-criteria.md) — Acceptance gates and target verification criteria.
- [fallback-tree.md](references/fallback-tree.md) — Fallback resolution for installation failures and target collisions.

Files in this skill

  • SKILL.md3.1 KB
  • acceptance-criteria.md1.1 KB
  • evals/evals.json679 B
  • evals/results.tsv34 B
  • fallback-tree.md282 B

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…