skills.rest
dxxx
dxxxCOMMUNITY
Explore all skills by this author →
Website𝕏@DXXX1988GitHub

wp-plugin-directory-guidelines

Validate WordPress plugins against WordPress.org Plugin Directory guidelines.

Updated Aug 23, 2026
Search Tags:#code review#compliance#plugin#WordPress#GPL
One-click install
npx skills add https://github.com/dxxx/Bot-OS --skill wp-plugin-directory-guidelines
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: wp-plugin-directory-guidelines
Source: https://github.com/dxxx/Bot-OS/tree/main/skills/wordpress-agent-skills/skills/wp-plugin-directory-guidelines
Command: npx skills add https://github.com/dxxx/Bot-OS --skill wp-plugin-directory-guidelines

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a comprehensive guide to help developers ensure their WordPress plugins comply with the Plugin Directory guidelines, reducing the risk of rejection and enhancing plugin quality.

Core Features & Use Cases

  • GPL Compliance: Checks for GPL compatibility of plugin code and bundled libraries.
  • Plugin Naming: Validates plugin names and slugs against WordPress rules.
  • License Headers: Confirms the presence and correctness of license headers.
  • Use Case: When preparing a plugin for submission to the WordPress.org Plugin Directory, use this Skill to verify compliance with all necessary guidelines.

Quick Start

Use the wp-plugin-directory-guidelines skill to review the plugin 'my-plugin' for compliance with WordPress.org guidelines.

Frequently Asked Questions about wp-plugin-directory-guidelines

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check my WordPress plugin for GPL compliance before submitting it?▼

WordPress plugin directory guidelines require validating plugin names and slugs against WordPress rules. This process checks your chosen identifiers to ensure they meet the directory's specific naming conventions before you submit your plugin for review.

How do I validate my plugin's name and slug against WordPress.org rules?▼

WordPress plugin directory guidelines require validating plugin names and slugs against WordPress rules. This process checks your chosen identifiers to ensure they meet the directory's specific naming conventions before you submit your plugin for review.

What are the license header requirements for a WordPress plugin?▼

License header requirements for a WordPress plugin demand correct and present license declarations in your code. Validating these headers against Plugin Directory guidelines confirms your submission accurately declares its GPL-compatible license.

Do I need to know WordPress development practices to use this validation process?▼

You need working knowledge of WordPress plugin development practices and the WordPress.org Plugin Directory guidelines. This background is required to effectively validate GPL compatibility, license header correctness, and naming conventions for your plugin submission.

Why was my WordPress plugin rejected from the directory submission?▼

WordPress plugin submissions are often rejected due to GPL incompatibility, incorrect license headers, or invalid naming conventions. Reviewing your plugin against the Plugin Directory guidelines identifies these compliance issues before you submit.

Related Skills

Explore More Software Engineering Skills→
tyk-labtyk-lab

using-git-worktrees

Create an isolated git worktree for feature development with safety checks.

Community
Advanced
wp-mediawp-media
81

compliance

Automates WordPress plugin compliance checks against PHPCS and WordPress.org rules.

Official
Intermediate
bonnybonny
316

code-quality

Enforce WordPress coding standards for PHP, CSS, and JavaScript.

Community
Intermediate
lushly-devlushly-dev
4

audit-licenses

Audit OSS dependency licenses and generate SBOMs in CycloneDX and SPDX formats.

Official
Advanced