SkillAgentSearch skills...

wp-plugin-directory-guidelines

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, und…

Install / Use

npx skills add WordPress/agent-skills --skill wp-plugin-directory-guidelines

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

91/100

Category

Automation

Supported Platforms

Universal

Our assessment of wp-plugin-directory-guidelines

wp-plugin-directory-guidelines scores 91/100 on our quality scale, 1022nd of 2,780 Automation skills we index (top 37%).

Its SKILL.md is 6.1 KB long, well organised into 17 sections with 3 code examples: a thorough specification that gives an agent plenty to work with.

With 2,162 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
29/30
Structure
18/20
Description
15/15
Adoption
14/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so wp-plugin-directory-guidelines is actively maintained.
  • Our last check on 2026-10-29 found the source still online.
  • No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
  • Its trust signals score 88/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-09-30. Automated pattern scan on 2026-09-29. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

wp-plugin-directory-guidelines compared with similar skills

All 4 of these similar skills score higher than wp-plugin-directory-guidelines; compare them before choosing.

SkillScoreStarsUpdatedFormat
wp-plugin-directory-guidelines (this skill)by WordPress912.2k54d agoSKILL.md
Agent-Reachby Panniantong100112.3k9d agoCLAUDE.md
rufloby ruvnet10081.9ktodayCLAUDE.md
Claude-Code-Game-Studiosby Donchitos10039.7k7d agoCLAUDE.md
Scraplingby D4Vinci100103.6k2d agoMCP Server

Frequently asked questions

How do I install wp-plugin-directory-guidelines?
Run npx skills add WordPress/agent-skills --skill wp-plugin-directory-guidelines. The install tabs above show the steps for each supported agent.
Which AI agents does wp-plugin-directory-guidelines work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is wp-plugin-directory-guidelines safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It declares no license and scores 88/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is wp-plugin-directory-guidelines still maintained?
The repository was last updated about 2 months ago, so wp-plugin-directory-guidelines is actively maintained.

name: wp-plugin-directory-guidelines 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, understanding why a plugin was rejected from WordPress.org, or answering any question about the 18 WordPress.org Plugin Directory guidelines — even if the user doesn't mention 'guidelines' explicitly." compatibility: "Targets WordPress 7.0+ (PHP 7.4.0+)."

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

Inputs required

  • Plugin source code (or specific files to review)
  • Optional: plugin readme and plugin header metadata for naming and license checks

Procedure

  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.

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.

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.

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.

Related Skills

View on GitHub
GitHub Stars2.2k
CategoryAutomation
Updated1mo ago
Forks322

Languages

JavaScript

Trust signals

88/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

1 medium