How do I install the Wpm skill?

Run npx skillmds@latest add trywpm/wpm in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Wpm?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

trywpm (@trywpm) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Wpm by trywpm — Agent Skill

Name: Wpm
Author: trywpm

Wpm

Manages WordPress plugins, themes, and mu-plugins using wpm, a package manager for the WordPress ecosystem. Use when the user wants to install, update, remove, or publish WordPress packages, initialize a WordPress project with wpm, manage wpm.json dependencies, or work with the wpm registry.

trywpm 4436d99 4 files · 9.7 KB Updated Sep 17, 2026

File contents

wpm - Package Manager for WordPress

Installation

# Check if installed
wpm --version

# Install (Unix)
curl -fsSL https://wpm.so/install | bash

# Install (Windows PowerShell)
irm wpm.so/install.ps1 | iex

Quick start

Initialize a project:

wpm init

Install a package:

wpm install wordpress-seo@26.9.0

wpm.json overview

Two modes based on context:

	Project (site)	Publishable package
`private`	`true` (recommended)	`false` or omitted
`type`	optional	required (`plugin`/`theme`/`mu-plugin`)
`version`	optional	required (SemVer)
`config.runtime`	recommended	—
`requires`	—	recommended

Critical version rules

dependencies, devDependencies, config.runtime.wp, config.runtime.php → exact versions only (no ^, ~, >=)
requires.wp, requires.php → version ranges allowed (>=6.0.0)

Schema: Read reference/schema.json for the full JSON schema.

Commands

CLI reference: See reference/commands.md for all commands and workflows.

Common commands:

wpm init                          # New project
wpm init --existing               # Existing plugin/theme
wpm install <pkg>@<version>       # Install package
wpm ls                            # List dependencies
wpm outdated                      # Check for updates
wpm uninstall <pkg>               # Remove (⚠️ confirm first)

If unsure about a command or flag, run wpm <command> --help.

Publishing

Publishing guide: See reference/publishing.md for auth, CI, and publish workflow.

Lockfile

wpm.lock is auto-generated. Commit it. Never edit manually.

Common pitfalls

Do NOT use version ranges in dependencies or devDependencies
Do NOT use ranges in config.runtime
Do NOT publish when "private": true
Always run wpm outdated before updating; re-install specific versions explicitly

---name: wpmdescription: Manages WordPress plugins, themes, and mu-plugins using wpm, a package manager for the WordPress ecosystem. Use when the user wants to install, update, remove, or publish WordPress packages, initialize a WordPress project with wpm, manage wpm.json dependencies, or work with the wpm registry.---# wpm - Package Manager for WordPress## Installation```bash# Check if installedwpm --version# Install (Unix)curl -fsSL https://wpm.so/install | bash# Install (Windows PowerShell)irm wpm.so/install.ps1 | iex```## Quick startInitialize a project:```bashwpm init```Install a package:```bashwpm install wordpress-seo@26.9.0```## wpm.json overviewTwo modes based on context:| | Project (site) | Publishable package ||---|---|---|| `private` | `true` (recommended) | `false` or omitted || `type` | optional | **required** (`plugin`/`theme`/`mu-plugin`) || `version` | optional | **required** (SemVer) || `config.runtime` | recommended | — || `requires` | — | recommended |### Critical version rules- `dependencies`, `devDependencies`, `config.runtime.wp`, `config.runtime.php` → **exact versions only** (no `^`, `~`, `>=`)- `requires.wp`, `requires.php` → version ranges allowed (`>=6.0.0`)**Schema**: Read [reference/schema.json](reference/schema.json) for the full JSON schema.## Commands**CLI reference**: See [reference/commands.md](reference/commands.md) for all commands and workflows.Common commands:```bashwpm init # New projectwpm init --existing # Existing plugin/themewpm install <pkg>@<version> # Install packagewpm ls # List dependencieswpm outdated # Check for updateswpm uninstall <pkg> # Remove (⚠️ confirm first)```If unsure about a command or flag, run `wpm <command> --help`.## Publishing**Publishing guide**: See [reference/publishing.md](reference/publishing.md) for auth, CI, and publish workflow.## Lockfile- `wpm.lock` is auto-generated. Commit it. Never edit manually.## Common pitfalls- Do NOT use version ranges in `dependencies` or `devDependencies`- Do NOT use ranges in `config.runtime`- Do NOT publish when `"private": true`- Always run `wpm outdated` before updating; re-install specific versions explicitly

Frequently asked questions

Wpm