Agent Package Manager

This skill handles the full lifecycle of Agent Package Manager in your repository: initializing apm.yml, installing and updating packages, managing lockfiles, compiling agent context, and browsing MCP servers. It validates manifests before making changes, uses dry runs to preview risky updates, and warns you when packages get served from stale cache. The procedures walk through dependency resolution, script execution, runtime setup, and CI packaging workflows. One heads up: it enforces security scans at install time and respects organization policies that can block transitive dependencies, so you'll want to address flagged content rather than trying to bypass the checks. Best for teams managing shared agent configurations across multiple tools and needing reproducible builds.

skills.sh installs: 481
GitHub stars: 1
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add webmaxru/ai-native-dev --skill agent-package-manager --agent claude-code

Installs into .claude/skills of the current project.

Files

Agent Package Manager

Procedures

Step 1: Assess the repository and the requested APM outcome

Inspect the repository root for apm.yml, apm.lock.yaml, .github/, .claude/, .codex/, .cursor/, .gemini/, .grok/, .opencode/, .windsurf/, .kiro/, and apm_modules/.
Execute apm --version and apm config to confirm the installed CLI and current configuration.
If apm.yml exists, read references/manifest-and-lockfile.md before changing dependencies, scripts, or compilation settings.
If the request is about package installation, updates, pruning, or removal, read references/command-workflows.md before executing APM commands.
If no apm.yml exists and the user wants APM in the repository, initialize the project with apm init or apm init --yes.
If the repository already uses another agent configuration flow and the user did not ask to migrate it, limit the change to the requested APM scope instead of replacing the existing setup.