agent-package-manager

Scaffold and validate APM agent packages with required primitives.

Updated Dec 23, 2025
One-click install
npx skills add https://github.com/vineethsoma/agent-packages --skill agent-package-manager
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-package-manager
Source: https://github.com/vineethsoma/agent-packages/tree/main/.github/skills/package-manager
Command: npx skills add https://github.com/vineethsoma/agent-packages --skill agent-package-manager

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pyyaml, and includes scripts (resource) components.

What problem does it solve?

This Skill automates the creation, validation, and maintenance of APM agent packages.

Core Features & Use Cases

  • Scaffolds new agent/skill packages with proper structure
  • Validates apm.yml, SKILL.md, and .apm primitives
  • Generates and populates required primitives (instructions/prompts/agents)
  • Use cases: starting new packages, upgrading dependencies, kebab-case enforcement

Quick Start

Create a new package skeleton and run local validation:

  • Follow prompts to provide package name and type
  • Run local validation commands to verify structure

Frequently Asked Questions about agent-package-manager

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I scaffold a new agent package with the correct directory structure?

Scaffolding an agent package generates a standard skeleton and wires up required primitives in .apm subdirectories. You provide the package name and type, and it creates the baseline files ensuring reliable installation.

How do I validate apm.yml integrity and SKILL.md presence for my agent skills?

Validating apm.yml integrity checks that frontmatter is correct, SKILL.md is present for skills, and at least one primitive exists in .apm subdirectories. This ensures your agent packages meet structural requirements.

Why does my agent package validation fail on naming conventions?

Agent package validation fails on naming when package names do not follow kebab-case enforcement. The scaffolding process applies kebab-case rules to ensure package names are formatted correctly for reliable installation.

What dependencies do I need to generate and populate agent package primitives?

Generating and populating required primitives like instructions, prompts, and agents requires the pyyaml dependency. This allows the scripts to parse and validate the apm.yml frontmatter correctly during package creation.

Can I use this scaffolding to upgrade dependencies and maintain existing agent packages?

Scaffolding supports maintaining existing agent packages by validating structure during dependency upgrades. It enforces kebab-case naming and correct frontmatter to ensure apm.yml integrity across updates.

What is the best way to ensure my APM agent packages install reliably?

Ensuring reliable installation requires validating apm.yml integrity, SKILL.md presence, and at least one primitive in .apm subdirectories. The scaffolding process enforces these structural rules during package creation.