pressship: Skill for Claude Code

.claude/skills/wordpress-plugin-publish/SKILL.md

wordpress-plugin-publish is a skill for Claude Code from Automattic/pressship. It costs 80 tokens per session (1,450 once invoked), scanned A, original, MIT.

A release guide for submitting and publishing WordPress.org plugins with Pressship, a tool for packaging, checking, and sending plugins to WordPress.org. It covers local plugin folders, review checks, demos, and release workflows.

In plain words
What is it for?
Use it to verify, package, submit, reupload, release, or locally demonstrate a WordPress.org plugin while following safe dry-run and review steps.
Why use it?
It provides a repeatable process for checking a plugin and reduces mistakes during submission or release.

Skill for Claude Code

Written for Claude Code: installed under .claude/. Also seen: mentions Codex.

This is Automattic/pressship's own configuration. It tells Claude Code how to work on pressship itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything pressship configures →

Reuse

Borrowing it

Nothing to install: this file belongs to Automattic/pressship. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/Automattic/pressship/main/.claude/skills/wordpress-plugin-publish/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/Automattic/pressship

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for wordpress-plugin-publish

README.md
[![agentmods](https://agentmods.dev/badge/skills/automattic/pressship/wordpress-plugin-publish/github.svg)](https://agentmods.dev/skills/automattic/pressship/wordpress-plugin-publish)
Your own site
<a href="https://agentmods.dev/skills/automattic/pressship/wordpress-plugin-publish"><img src="https://agentmods.dev/badge/skills/automattic/pressship/wordpress-plugin-publish/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for wordpress-plugin-publish

Your own site · 80×15
<a href="https://agentmods.dev/skills/automattic/pressship/wordpress-plugin-publish"><img src="https://agentmods.dev/badge/skills/automattic/pressship/wordpress-plugin-publish.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 80 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,450 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 36 findings, up to medium

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • medium MCP Rug Pull · line 8
    npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
    Fix: Pin the version: npx @scope/[email protected]
  • medium MCP Rug Pull · line 15
    npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
    Fix: Pin the version: npx @scope/[email protected]
  • medium MCP Rug Pull · line 37
    npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
    Fix: Pin the version: npx @scope/[email protected]
  • medium MCP Rug Pull · line 45
    npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
    Fix: Pin the version: npx @scope/[email protected]
  • medium MCP Rug Pull · line 46
    npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
    Fix: Pin the version: npx @scope/[email protected]
  • medium MCP Rug Pull · line 47
    npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
    Fix: Pin the version: npx @scope/[email protected]
  • medium MCP Rug Pull · line 48
    npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
    Fix: Pin the version: npx @scope/[email protected]
  • medium MCP Rug Pull · line 49
    npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
    Fix: Pin the version: npx @scope/[email protected]
  • medium MCP Rug Pull · line 60
    npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
    Fix: Pin the version: npx @scope/[email protected]
  • medium MCP Rug Pull · line 66
    npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
    Fix: Pin the version: npx @scope/[email protected]
  • medium MCP Rug Pull · line 67
    npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
    Fix: Pin the version: npx @scope/[email protected]
  • medium MCP Rug Pull · line 68
    npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
    Fix: Pin the version: npx @scope/[email protected]
  • medium MCP Rug Pull · line 69
    npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
    Fix: Pin the version: npx @scope/[email protected]
  • medium MCP Rug Pull · line 77
    npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
    Fix: Pin the version: npx @scope/[email protected]
  • medium MCP Rug Pull · line 83
    npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
    Fix: Pin the version: npx @scope/[email protected]
  • medium MCP Rug Pull · line 89
    npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
    Fix: Pin the version: npx @scope/[email protected]
  • medium MCP Rug Pull · line 95
    npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
    Fix: Pin the version: npx @scope/[email protected]
  • medium MCP Rug Pull · line 96
    npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
    Fix: Pin the version: npx @scope/[email protected]
  • medium MCP Rug Pull · line 108
    npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
    Fix: Pin the version: npx @scope/[email protected]
  • medium MCP Rug Pull · line 114
    npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
    Fix: Pin the version: npx @scope/[email protected]
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00080 $0.01450
Opus 5.5 $0.00032 $0.00580
Sonnet 5.5 $0.00016 $0.00290
Haiku 4.5 $0.00008 $0.00145

Measured 2mo ago against content hash 57daa9b4a386, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

wordpress-plugin-publish scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/skills/wordpress-plugin-publish/SKILL.md · 207 lines

How it starts

The opening of the file, as written. The whole thing — 207 lines — stays where its author put it; the contents beside it link to each section on GitHub.

WordPress Plugin Publish

Use Pressship for WordPress.org plugin submission and release work. Prefer npx pressship unless the user explicitly wants the local checkout version or the WP-CLI package (wp ship).

Install Surfaces

Use the install surface the user asks for:

npx pressship verify .
wp package install f/pressship
wp ship verify .
npm install -g pressship
pressship verify .

For agent skill installation:

npx skills add f/pressship --skill wordpress-plugin-publish -a codex
npx skills add f/pressship --skill wordpress-plugin-publish -a claude-code

Safety Rules

  • Never publish, submit, reupload, or release without first running a dry run, unless the user explicitly says to skip it.
  • Do not push git commits or tags unless the user explicitly asks.
  • Report Plugin Check findings clearly. Do not hide them just because Pressship can continue.
  • Use repeatable excludes for large or source-only files. Prefer .pressshipignore when the project already has one.
  • Use --no-verify only when the user explicitly asks to bypass readme validation and Plugin Check.
  • If Pressship prompts interactively, answer only with user-approved or obvious plugin metadata.
  • If authentication fails, run npx pressship login and let the user complete WordPress.org login.
  • For approved-plugin SVN releases, expect Pressship to verify before SVN changes, reject already-published versions, and ask for a generated WordPress.org SVN password when needed.

Orientation

From the plugin directory:

npx pressship whoami
npx pressship verify .
npx pressship status .
npx pressship info .
npx pressship info --remote

Use status to determine whether publish will target a pending submission reupload or an approved SVN release. Use verify when you need readme validation and Plugin Check without creating a zip.

Local Playground Test

Start a local WordPress Playground with the plugin mounted:

npx pressship demo .

Useful options:

Read the full file on GitHub · 207 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2mo ago First seen · 207 lines · 80 tokens per session scan A 57daa9b4a386

Subscribe to this mod's changes

wordpress-plugin-publish is a skill published in the GitHub repository Automattic/pressship (51 stars, last pushed 1mo ago), licensed MIT. It adds 80 tokens to every session and 1,450 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

wordpress-plugin-publish compared with skills from other repositories

wordpress-plugin-publish next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
wordpress-plugin-publishAutomattic/pressshipSkill511mo agoMITA80Claude Code
rea-changelog-updatemorluto/reaSkill435kyesterdayMITA33Claude Code
codew-release-qa-sweepHmbown/CodeWhaleSkill41k5d agoMITA31Claude Code, Codex
releaseHmbown/CodeWhaleSkill41k5d agoMITA0Claude Code, Codex
skillshare-changelogrunkids/skillshareSkill2.9kyesterdayMITA134Claude Code
githubAtomicBot-ai/atomic-agentSkill3.4k8d agoMITA48Claude Code, Codex
commit-prZaxbyHub/opencode-swarmSkill518yesterdayMITA100Codex