Skip to main content

Agent Publishing Skill

Pressship includes an agent skill for cautious WordPress.org plugin publishing workflows:

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

The skill is designed for agents that help maintain plugins with Pressship. It turns the publishing process into a safer checklist instead of a loose sequence of commands.

Install The Skill​

You can install the skill with the open agent skills CLI. First, list the skills exposed by the Pressship repository:

npx skills add f/pressship --list

Install the publishing skill for a specific agent:

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

For a global, non-interactive install, combine --global, --agent, and --yes:

npx skills add f/pressship --skill wordpress-plugin-publish --global --agent claude-code --yes

Useful skills add flags:

  • --list shows available skills without installing them.
  • --skill wordpress-plugin-publish installs only Pressship's publishing workflow skill.
  • --agent <name> targets a compatible agent, such as claude-code or codex.
  • --global installs to the user-level skills directory instead of the current project.
  • --yes skips confirmation prompts for repeatable setup scripts.

See the skills CLI reference for the full option list.

What It Enforces​

  • Run a dry run before any submit, reupload, or release unless explicitly told otherwise.
  • Inspect account, plugin info, and WordPress.org status before choosing a publishing route.
  • Use pressship verify when you need readme validation and Plugin Check without building a zip.
  • Keep Plugin Check findings visible instead of hiding them behind automation.
  • Use --no-verify only when explicitly asked to bypass readme validation and Plugin Check.
  • Use repeatable package exclusions for bulky or source-only files.
  • Avoid git commits, pushes, or tags unless the user explicitly asks for them.
  • Report exactly what happened at the end of the workflow.

Suggested Flow​

Start by orienting around the current account and plugin state:

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

Test the plugin locally when useful:

npx pressship demo .

Validate and package:

npx pressship verify .
npx pressship pack .

For review uploads or pending reuploads, dry-run first:

npx pressship publish . --dry-run -y

Then publish only after the dry run is understood:

npx pressship publish . -y

For approved plugins, force the release route:

npx pressship publish . --release --dry-run -y
npx pressship publish . --release -y

For an existing WordPress.org SVN plugin, the skill follows the checkout-root flow:

npx pressship get my-plugin ./my-plugin
cd ./my-plugin
npx pressship version patch
npx pressship publish --release --dry-run -y
npx pressship publish --release -y

The skill also understands the WP-CLI package surface:

wp package install f/pressship
wp ship verify .
wp ship publish . --dry-run

Final Report Checklist​

The skill asks agents to report:

  • whether a dry run was run;
  • whether verify ran and whether validation was bypassed;
  • package size and notable included or excluded files;
  • Plugin Check result summary;
  • upload or release status and slug;
  • whether git was left untouched or changed.

This keeps the automation useful without making WordPress.org publishing feel invisible.