CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

72

Quality

89%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Critical

Do not install without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

78%Weight 40%Scale 1-5

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

A well-structured reference skill with concrete checklists, clear progressive disclosure to three real reference files, and a sound review procedure. The main weakness is minor redundancy (a duplicate/empty heading and overlapping checklists) and an implicit rather than explicit validation feedback loop.

Suggestions

Remove the empty '### Valid License Headers' heading (line 61) or merge it with the '## Valid License Headers for WordPress Plugins' section to eliminate the duplicate.

Consolidate the overlapping 'Quick Reference: WordPress GPL Requirements' and 'License Compliance Checklist' into a single checklist to reduce redundancy.

Make the validation feedback loop explicit in the Procedure (e.g., 'If a finding fails verification, correct the citation/license string and re-verify before reporting') to strengthen the workflow checkpoints.

DimensionReasoningScore

Conciseness

Mostly lean decision-aids and checklists with little concept explanation, but a duplicate/empty '### Valid License Headers' heading and some overlap between the Quick Reference and License Compliance Checklist keep it from being perfectly tight.

4 / 5

Actionability

Provides concrete, executable guidance (exact License/License URI header strings, specific SPDX identifiers, license-family lists, naming thresholds like >=5 chars and slug <=50 chars), with minor gaps where edge cases are deferred to references.

4 / 5

Workflow Clarity

The Procedure section sequences six clear steps with a verification cue (cite Guideline 1 with file path and license string) and failure-mode handling (do not guess on ambiguous licenses), though the validate-fix-retry loop is implicit rather than a tight gated feedback loop.

4 / 5

Progressive Disclosure

Three real reference files are linked with clear signaling ('Load this reference file only when a full guideline audit is requested'), one level deep, with the body acting as a well-organized overview and quick reference.

5 / 5

Total

17

/

20

Passed

Description

100%Weight 40%Scale 1-5

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 highly specific, well-triggered description that clearly scopes a niche domain and gives concrete, natural-language entry points for when to use it. It answers both what and when without padding or over-claiming.

DimensionReasoningScore

Specificity

Lists multiple concrete actions (reviewing for GPL compliance, checking license headers, evaluating upsell/freemium/trialware, validating naming/trademark, checking slugs, understanding rejections) with comprehensive coverage.

5 / 5

Completeness

Explicitly answers both what (review plugins against the 18 directory guidelines, license/naming/trialware compliance) and when via a 'Use when...' clause with concrete trigger phrases.

5 / 5

Trigger Term Quality

Covers natural terms users say (GPL compliance, license headers, trialware, slugs, rejected from WordPress.org) plus synonyms (upsell/freemium/trialware) and an explicit meta-trigger for implicit mentions.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (WordPress.org Plugin Directory guidelines) with specific triggers (GPL headers, trialware, slugs, rejection reasons) that minimize overlap with unrelated skills.

5 / 5

Total

20

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
WordPress/agent-skills
Reviewed

Table of Contents

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.