Wp Plugin Directory Guidelines

What it does

The document combines a directory-guideline checklist with references for bundled code, trademarks, upsells and automated Plugin Check findings. It distinguishes a narrow conceptual review from a full source audit. Its practical output is a list of concrete submission risks and evidence needed to resolve them.

Best for

Plugin authors preparing a directory submission or interpreting review feedback on an existing package.

Tradeoffs and requirements

Policies can change, and automated findings need context. Passing Plugin Check is not approval by the directory review team. Licensing conclusions also depend on every bundled dependency and asset, not only the main plugin header.

Targets WordPress 7.0+ (PHP 7.4.0+). Automated validation requires a local WordPress environment, WP-CLI, and Plugin Check.

Install from the source

First time installing a skill? Follow the walkthrough →

Inspect the pinned source snapshot and its supporting files first. The command selects this skill through the open-source skills CLI. Node.js and agent-specific setup may be required. Installation can download code. Catalog ingestion never executes skill instructions or install scripts.

npx skills add https://github.com/WordPress/agent-skills/tree/eff3785fc28c4380d172094518c66a6a997c95d4/skills/wp-plugin-directory-guidelines --skill wp-plugin-directory-guidelines

Review pinned skill folder ↗ · CLI documentation ↗

After source review, use npx skills check and npx skills update to inspect and apply upstream updates. Re-check changed instructions before running them.

Safety & review signals

Static review only. This is not a security audit or a guarantee of safety.

SKILL.md text only; scripts, dependencies and runtime behavior not audited.

• Network Access — review the source context.

Allowed tools declaration: Unknown. Runtime permissions and network behavior: Unknown.

Offline package integrity

A temporary folder-copy check, not an agent installation or runtime safety verdict.

5 files copied and checksummed from this exact source snapshot. No package code or installation scripts were executed.

Inventory SHA-256: 24eff8b18c82655e86a27bbc3ccd713a41349cf53b722247ad76a90dfba09b83

AI Craft Pad Skill Score

75/100 · Metadata coverage 80% · Model 1.0

Scores summarize observable discovery signals. Popularity and repository activity apply to the whole repository. Unknown runtime safety earns no certification.

Documentation

100/100

100

Maintenance

100/100

100

License Clarity

0/100

0

Repository Health

85/100

85

Compatibility Evidence

80/100

80

Popularity

61/100

61

Originality

80/100

80

Static Safety

60/100

60

Suggested workflow

Inventory the release package and dependency licenses, check names and promotional flows, then run the available validation tools in a local WordPress environment. Separate confirmed defects, contextual warnings and questions that require current policy interpretation.

How to judge the result

Inspect the exact distributable archive, verify that reported fixes are included and repeat relevant checks. Record unresolved licensing or naming questions with source references, and retain actual reviewer feedback rather than presenting a checklist as a guarantee of acceptance.