Index of every page on this site: llms.txt
All skills
wordpress avatar

/wp-plugin-directory-guidelines

@7374e6f official
by wordpresswordpress/agent-skills2.4k stars
351
Run it yourself

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.

Use this Skill: https://skilld.dev/gh/wordpress/agent-skills/wp-plugin-directory-guidelines

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈117 tokens for metadata: the name and description. ≈1.9k when used: this file. ≈13k more on demand in 4 files.

Description uses 5.9% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈468 characters, or 5.9%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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.

  1. Check the plugin's license header against the Valid License Headers section below.
  2. Walk through the 18 Guidelines checklist, paying special attention to Guidelines 1, 4, 5, 7, 8, and 17.
  3. Confirm trialware/freemium compliance using the checklist in guideline-review-checklist.md (Guideline 5 section).
  4. For bundled third-party code, verify license compatibility against GPL-Compatible Licenses (Quick) below.
  5. Flag matches from Common GPL Violations (Quick) below.
  6. For edge cases, consult the detailed references and the GNU GPL FAQ.
  7. For source-code reviews or validation after changes, load Plugin Check validation: test, check, assess findings, apply authorized fixes, and retest. It includes commands, reporting requirements, and troubleshooting.

Verification

  • Report evidence for each conclusion using the licensing, naming, or Plugin Check reporting guidance below. Distinguish manual review, executed checks, and proposed next steps.

Failure modes / debugging

  • If automated validation is unavailable, continue manual review and use the prerequisite and coverage fallbacks in Plugin Check validation. Never report an unexecuted check as passed.

Escalation

Use official Plugin Check documentation for tool behavior and the directory guidelines for policy. Surface unresolved policy ambiguity, uncertain findings, and fixes outside the authorized scope for human review.

18-Guideline Review Checklist

Use the detailed, per-guideline checklist in guideline-review-checklist.md. Load this reference file only when a full guideline audit is requested.

GPL Compliance (Guideline 1 in Detail)

Use gpl-compliance.md for full license tables, compatibility nuances, and examples. Keep this inline section as a quick decision aid.

Verification (Licensing)

  • Every licensing-related issue must cite Guideline 1 and include the file path and exact license string.
  • Confirm compatibility claims against GPL-Compatible Licenses (Quick) and escalate ambiguous licenses.
  • When recommending a header correction, provide both literal License: and License URI: values from the examples below. Link to gpl-compliance.md for the compatibility basis; do not merely say to add a matching URI.

Failure modes (Licensing)

  • If a license is not clearly GPL-compatible, do not guess. Check the GNU license list.
  • For dual-license packages, verify both licenses and redistribution terms.

Quick Reference: WordPress GPL Requirements

  • WordPress is GPLv2 or later.
  • Plugins distributed on WordPress.org must be 100% GPL-compatible (code and assets).
  • Include a valid License: header and License URI: in the main plugin file.
  • Do not add restrictions that conflict with GPL freedoms.

Valid License Headers

GPL Versions Summary

Version Year Key Addition
GPLv1 1989 Base copyleft: share-alike for modifications
GPLv2 1991 "Liberty or death" clause (Section 7), clearer distribution terms
GPLv3 2007 Anti-tivoization, explicit patent grants, compatibility provisions

WordPress uses GPLv2 or later, meaning plugins can use GPLv2, GPLv3, or "GPLv2 or later".

For full license texts, see:

License Compliance Checklist

When reviewing a plugin, verify:

  • Main plugin file has a valid License: header (e.g., GPL-2.0-or-later, GPL-2.0+, GPLv2 or later)
  • Main plugin file has a License URI: header pointing to the GPL text
  • If bundled libraries exist, each has a GPL-compatible license
  • No "split licensing" (e.g., code GPL but premium features proprietary)
  • No additional restrictions beyond what GPL allows
  • No clauses restricting commercial use, modification, or redistribution
  • No obfuscated code (violates the spirit of source code availability)

Valid License Headers for WordPress Plugins

License: GPL-2.0-or-later
License URI: https://www.gnu.org/licenses/gpl-2.0.html
License: GPL-3.0-or-later
License URI: https://www.gnu.org/licenses/gpl-3.0.html
License: GPLv2 or later
License URI: https://www.gnu.org/licenses/gpl-2.0.html

GPL-Compatible Licenses (Quick)

  • Safe defaults: GPL-2.0-or-later, GPL-3.0-or-later.
  • Commonly accepted permissive families: MIT/Expat, BSD, ISC, zlib, Boost.
  • Conditional compatibility requires care: Apache-2.0 and MPL-2.0 (verify usage context).
  • For full accepted and rejected identifiers, use gpl-compliance.md.

Common GPL Violations (Quick)

  • Split licensing that restricts distributed code.
  • Obfuscated or non-corresponding source distribution.
  • Restrictive clauses (non-commercial, no-resale, forced backlink).
  • Bundling GPL-incompatible libraries or assets.

Plugin Naming Rules (Guideline 17)

Use naming-rules.md for full trademark lists, slug blocks, and naming examples. Keep this inline checklist for quick screening.

For naming reviews, cite Guideline 17, explain the applicable trademark or blocked-slug rule, and link to the reference. When proposing a replacement, give both name and slug and explicitly verify lowercase, hyphen separation, and the 50-character limit.

Naming Checklist (Quick)

  • Name is not a placeholder and has at least 5 alphanumeric characters.
  • Header name and readme name match.
  • Name is specific and function-related; avoid keyword stuffing.
  • Trademark/project names appear only after connectors like for, with, using, and.
  • No banned/discouraged terms or trademark portmanteaus.
  • Slug is lowercase, hyphenated, <= 50 chars, and avoids blocked terms.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts1mo3 checks · Risk SAFE
  • Gen Agent Trust Hub1mo

    This skill serves as an authoritative reference for reviewing WordPress plugins against the official WordPress.org Plugin Directory guidelines. It contains no executable code, network operations, or security risks, and all external references point to trusted domains.

  • Socket1mo

    No alerts

  • Snyk1mo

    Risk: LOW · No issues

Signed by skilld at 7374e6f. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last week.

Activeupdated last month
Other metadata
compatibility
Targets WordPress 7.0+ (PHP 7.4.0+). Automated validation requires a local WordPress environment, WP-CLI, and Plugin Check.
  • wordpress
  • gpl
  • licensing
  • plugin-compliance
  • trademark
  • wordpress-org
  • php
  • plugin-directory

README badge

README badge for wordpress/agent-skills/wp-plugin-directory-guidelines

Authoritative reference for the 18 WordPress.org Plugin Directory guidelines covering GPL licensing, plugin naming, trademark rules, trialware restrictions, and submission requirements. Use this skill to audit plugins for compliance before WordPress.org submission, verify GPL header validity and license compatibility, or answer questions about what is allowed in the plugin directory.

Generated from the current SKILL.md.

Does this skill cover all 18 WordPress.org Plugin Directory guidelines?
Yes. The skill is an authoritative reference for all 18 guidelines, with detailed checklists and specific procedures for GPL compliance, naming rules, trialware restrictions, and submission requirements.
What license headers does WordPress.org accept?
WordPress.org accepts GPL-2.0-or-later, GPL-3.0-or-later, or GPLv2/GPLv3 or later formats, with a corresponding License URI header pointing to the GPL text.
Does this help identify why a plugin was rejected from WordPress.org?
Yes. The skill guides you through the 18-guideline checklist to identify common violations (GPL incompatibility, trialware patterns, trademark issues, obfuscation) that typically cause rejections.
Can I use MIT or BSD licensed libraries in my WordPress plugin?
Yes, MIT, BSD, ISC, zlib, and Boost are commonly accepted as GPL-compatible. For conditional licenses like Apache-2.0 or MPL-2.0, the skill provides detailed compatibility guidance.
What counts as trialware and violates the guidelines?
The skill includes a trialware checklist covering premium upsells, freemium flows, license checks, and teaser UI. It flags patterns that restrict core functionality based on payment or licensing.

Generated from the current SKILL.md. These answers refresh after source changes.