Pull skills into agents

Materialize the effective skill set into folders your agents already read.

Prerequisites

• Quickstart completed (login, .pm-skills.json)
• At least one active skill resolving for the project (pm-skills list)

Pull

pm-skills pull --dry-run   # show the write plan
pm-skills pull

What happens:

1. Resolve — GET /skills/resolve for the bound project.
2. Detect agents — unless agents is set in .pm-skills.json or you pass --agent.
3. Write — SKILL.md + bundle files with provenance metadata.
4. Prune — remove previously managed skills that left the resolved set (never touches unmarked local skills).
5. Lockfile — update pm-skills.lock.json.

Example output layout

.claude/skills/api-error-handling/SKILL.md
.agents/skills/api-error-handling/SKILL.md
pm-skills.lock.json
.pm-skills.json

See Agents & folders for the mapping table.

Keep in sync

pm-skills status
pm-skills update              # consent to newer SHAs
pm-skills pull --frozen       # CI: exact lockfile SHAs only

Agentkit

If you use Agentkit’s AgentSkills plugin, point it at the same skill directories pm-skills writes (or your project’s configured skills root). The plugin loads local files; Skills Manager governs which versions land there.