RepoAI
Browse MCPs

WP Plugin Directory Guidelines

94TrustedInstructions only

Verification of WordPress repository standards, GPL licensing, and plugin submission rules.

What it does

Installing this skill equips your assistant with a structured reference for the complete WordPress.org Plugin Directory guidelines. It transforms the AI into an informed compliance reviewer that can evaluate code, license headers, and distribution patterns against the specific requirements enforced for repository inclusion.

By adding this knowledge base, you enable the assistant to identify potential points of failure before submission. It serves as a specialized lens for analyzing plugin source code, third-party library bundling, and freemium feature positioning to ensure alignment with the platform's open-source expectations.

When it earns its place

Reach for it when…

Apply this skill when preparing a plugin for the WordPress.org repository or auditing existing code for license compatibility. It is appropriate for confirming that license headers are formatted correctly, verifying that bundled assets do not violate GPL freedoms, and evaluating whether trialware or upsell flows conflict with official directory policies.

Look elsewhere when…

This skill is not designed for functional code reviews, performance testing, or security vulnerability assessments. Do not use it for debugging broken features or optimizing SQL queries, as it focuses strictly on administrative compliance and policy adherence rather than technical quality or software performance.

What to say to use it

You never invoke a skill directly — the assistant picks it up when your request matches what it covers. These are the kinds of things that do that.

  • check if my plugin follows wordpress.org rules
  • is this license compatible with wordpress plugins
  • verify my plugin readme and headers for submission
  • does my freemium model violate the directory guidelines

Install it

Install for all your projects

Copy the skill directory into your personal skills folder. Claude picks it up on its own the next time your request matches what it does — there is nothing to enable.

bash
git clone --depth 1 --branch trunk https://github.com/WordPress/agent-skills.git /tmp/agent-skills
mkdir -p ~/.claude/skills
cp -r /tmp/agent-skills/skills/wp-plugin-directory-guidelines ~/.claude/skills/wp-plugin-directory-guidelines

Install for one project only

Put it in the project's own skills folder instead, so it can be committed and shared with everyone working on that repository.

bash
cp -r /tmp/agent-skills/skills/wp-plugin-directory-guidelines .claude/skills/wp-plugin-directory-guidelines

If a skill of the same name exists in both places, the personal one wins.

Installing on Claude.ai or through the API instead? The full guide covers every surface.

Pair it with an MCP server

WP Plugin Directory Guidelines changes how the work is done. These servers change what Claude can reach while doing it.

How skills and MCP servers differ →