Agent Package Manager

This handles the full lifecycle of Agent Package Manager in your repository: initialization, installing and updating packages from GitHub or local paths, managing lockfiles, compiling agent context into instruction files, and packaging bundles for CI or team distribution. It's built around verification workflows like dry-run previews and explicit dependency resolution checks before making changes. The procedures are opinionated about keeping manifests clean, treating lockfiles as truth, and not forcing compilation when your toolchain doesn't need it. Use this when you're setting up APM or troubleshooting why packages won't update or why self-referencing dependencies fail. It won't write individual skills by hand or touch npm, pip, or other package managers.

skills.sh installs: 145
GitHub stars: 31
last updated: Jun 3, 2026

View on GitHub

Install

$ npx -y skills add webmaxru/agent-skills --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/, .cursor/, .opencode/, 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.