# Wp Plugin Directory Guidelines

Use when reviewing WordPress plugins for GPL compliance, checking license headers or...

- Repository: https://github.com/WordPress/agent-skills (2319 stars)
- Category: Engineering
- License: see repository
- Last updated: 2026-10-26
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add WordPress/agent-skills --skill wp-plugin-directory-guidelines -g -a claude-code -y`
Codex: `npx skills add WordPress/agent-skills --skill wp-plugin-directory-guidelines -g -a codex -y`
Cursor: `npx skills add WordPress/agent-skills --skill wp-plugin-directory-guidelines -g -a cursor -y`
Gemini CLI: `npx skills add WordPress/agent-skills --skill wp-plugin-directory-guidelines -g -a gemini-cli -y`

## Description

Use when reviewing WordPress plugins for GPL compliance, checking license headers or compatibility, evaluating upsell/freemium/trialware patterns, validating plugin naming or trademark rules, checking plugin slugs, running Plugin Check (PCP) to validate plugin changes, interpreting its findings, understanding why a plugin was rejected from WordPress.org, or answering questions about the 18 WordPress.org Plugin Directory guidelines.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

## Overview

Authoritative reference for the 18 WordPress.org Plugin Directory guidelines. Covers GPL licensing, plugin naming/trademark rules, trialware restrictions, and all other submission requirements.

## When to use

Use this skill when you need to:
- Review a WordPress plugin for compliance with the WordPress.org Plugin Directory guidelines
- Check GPL license compatibility for a plugin or its bundled libraries
- Verify license headers in plugin files
- Identify common guideline violations before submission
- Answer questions about what is or is not allowed on WordPress.org
- Evaluate premium/upsell flows, license checks, or freemium positioning
- Review "teaser" or "preview" UI for trialware violations
- Validate plugin changes with Plugin Check and assess errors or warnings in context

## Inputs required

- Plugin source code (or specific files to review)
- Optional: plugin readme and plugin header metadata for naming and license checks
- For automated validation: target plugin slug/path, local WordPress environment and command runner, available tests, and whether the task authorizes fixes or only review

## Procedure

Scope the review to the request. Conceptual licensing or naming questions do not require a WordPress installation or a full audit.

The rest: https://github.com/WordPress/agent-skills/blob/HEAD/skills/wp-plugin-directory-guidelines/SKILL.md