Name: wp-plugin-directory-guidelines
Rating: 75.2 (1 reviews)
Author: WordPress

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, 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.

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Critical

Do not install without reviewing

Quality

Content

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured compliance-review skill with actionable checklists, a sequenced procedure with verification/failure-mode checkpoints, and clean one-level-deep progressive disclosure; the only weakness is mild redundancy and general-knowledge padding.

Suggestions

Remove the 'GPL Versions Summary' table (GPLv1/v2/v3 history is general knowledge Claude already has) to tighten conciseness.

Delete the empty '### Valid License Headers' header at line 61 and consolidate it with the 'Valid License Headers for WordPress Plugins' section to avoid a dangling structural artifact.

Merge or deduplicate the inline 'License Compliance Checklist' against the referenced guideline-review-checklist.md so the inline body stays a lean quick reference rather than repeating checklist items.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient quick-reference material, but it retains a 'GPL Versions Summary' table (GPLv1/v2/v3 history) that Claude already knows and has redundant/empty structural artifacts such as an empty '### Valid License Headers' header and overlapping inline checklists.	2 / 3
Actionability	Concrete, copy-paste-ready guidance is present: valid license-header code blocks and a checklist with exact thresholds (e.g. 'at least 5 alphanumeric characters', slug '<= 50 chars'), so the instruction-only skill is fully actionable.	3 / 3
Workflow Clarity	The 6-step Procedure is clearly sequenced and backed by a 'Verification (Licensing)' section and 'Failure modes (Licensing)' recovery guidance, providing explicit checkpoints for a review workflow.	3 / 3
Progressive Disclosure	SKILL.md keeps inline quick-reference material while pushing detail to three real, one-level-deep, clearly signaled references (guideline-review-checklist.md, gpl-compliance.md, naming-rules.md), all verified to exist.	3 / 3
	Total	11 / 12 Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, third-person description with explicit 'Use when' triggers and many concrete, naturally-phrased actions tied to a distinct WordPress.org compliance niche.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — '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' — matching the score-3 anchor for multiple specific concrete actions.	3 / 3
Completeness	Explicitly answers both what (the enumerated review actions) and when via a leading 'Use when reviewing WordPress plugins for...' trigger clause, satisfying the score-3 anchor.	3 / 3
Trigger Term Quality	Covers natural terms a plugin reviewer would actually say — 'GPL compliance', 'license headers', 'upsell/freemium/trialware', 'plugin slugs', 'rejected from WordPress.org' — giving good coverage rather than jargon.	3 / 3
Distinctiveness Conflict Risk	The narrow niche of 'WordPress.org Plugin Directory guidelines' with domain-specific triggers makes it unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 12 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: WordPress/agent-skills
Path: skills/wp-plugin-directory-guidelines/SKILL.md
Commit: 120d309

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.