AgentPM™

export#

Generate a starter skill scaffold from an installed AgentPM tool.

Overview#

agentpm export --skill resolves an installed tool and writes a scaffolded skill directory with progressive disclosure:

skills/<tool-name>/
  SKILL.md
  references/
    tool-contract.md
    examples.md
  scripts/
    run.sh

This is a scaffold, not a polished final skill. It is meant to give you a strong starting point while keeping the packaged AgentPM tool as the execution source of truth.

Not a first-class artifact yet

Skill export is currently a scaffold/export surface. Skills may become first-class AgentPM artifacts later, but agentpm export --skill currently generates a starting point for human workflow authorship rather than a final packaged artifact.

Command synopsis#

agentpm export --skill <PACKAGE_REF> [--output <PATH>] [--force]

Arguments#

  • --skill <PACKAGE_REF>. Tool spec to export as a starter skill scaffold.
  • --output <PATH>. Override the default output directory.
  • --force. Overwrite an existing output directory.

Examples#

Generate the default scaffold#

agentpm export --skill @zack/echo-json

Write the scaffold somewhere else#

agentpm export --skill @zack/echo-json --output ./generated-skills/echo-json

Overwrite an existing scaffold#

agentpm export --skill @zack/echo-json --force

Behavior#

  • The command resolves the installed tool using the shared AgentPM resolver.
  • The generated SKILL.md stays concise and links out to deeper reference files.
  • references/tool-contract.md contains manifest-derived contract details.
  • references/examples.md contains generated starter examples.
  • scripts/run.sh delegates execution back to agentpm run.
  • The default output path uses only the tool name (skills/<tool-name>). If you have packages like @zack/echo-json and @acme/echo-json, use --output to avoid collisions.

Troubleshooting#

  • Tool not found. Ensure the tool is installed and available under .agentpm/tools/<namespace>/<name>/<version>.
  • Output directory already exists. Re-run with --force if you want to replace the existing scaffold.
  • Scaffold is too generic. That is expected. Add your own workflow-specific guidance and examples after generation.
←CLIserve
→CLIwhoami