wordpress-plugin-starter

Scaffold a WordPress 6.x plugin with custom post types, meta boxes, REST API endpoints, admin settings pages, asset enqueuing, and WP-CLI commands.

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./backend-php/wordpress-plugin-starter/SKILL.md

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.

The content is highly actionable with comprehensive executable code and a reasonably clear sequenced workflow, but it is a monolithic single-file skill with no progressive disclosure — the full class implementations belong in reference files that SKILL.md points to. Splitting the bulk into references would improve both conciseness and progressive disclosure.

Suggestions

Move the full per-component class implementations (Plugin.php, EventPostType, EventDetailsMeta, SettingsPage, EventsEndpoint, SyncCommand, uninstall.php) into files under references/ or scripts/, keeping only a concise overview and key snippets inline in SKILL.md with one-level-deep links.

Add an explicit validation/feedback step to 'First Steps After Scaffold', e.g. 'If the curl returns a 404 or error, run `wp rewrite flush` and confirm MAP_PLUGIN_DIR/assets paths before retrying.'

Remove the duplicated blockquote at the top (it repeats the frontmatter description) to tighten conciseness.

Dimension	Reasoning	Score
Conciseness	The body is dense with executable code and avoids explaining concepts Claude already knows (no 'WordPress is a CMS...' padding), but the opening blockquote repeats the frontmatter description verbatim and a few sections overlap, so minor trimming would reach anchor 5.	4 / 5
Actionability	Every section provides copy-paste-ready, executable PHP — main plugin file, bootstrap class, CPT, metabox with nonce/capability checks, Settings API page, REST routes, WP-CLI command, hooks, and uninstall cleanup — covering the common cases comprehensively per the level-5 anchor.	5 / 5
Workflow Clarity	'First Steps After Scaffold' gives a clear sequenced workflow (install → activate → flush → verify via curl) with a verification checkpoint, but it lacks an explicit error-recovery feedback loop (what to do if the curl check fails), keeping it just below anchor 5.	4 / 5
Progressive Disclosure	Section headers are well organized, but the entire ~700-line skill is inlined in SKILL.md with no reference, script, or asset bundle files and zero pointers to separate documents, so content that clearly belongs in per-component reference files (full class implementations) is inline rather than one level deep.	3 / 5
	Total	16 / 20 Passed

Description

71%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.

The description is specific and lists comprehensive concrete capabilities with strong WordPress-domain trigger terms, but it omits any explicit 'Use when...' guidance, which caps its completeness. Adding a trigger clause would lift the weakest dimension.

Suggestions

Append a 'Use when...' clause, e.g. 'Use when scaffolding or bootstrapping a WordPress plugin, or when the user asks to create custom post types, meta boxes, REST endpoints, admin settings pages, or WP-CLI commands.'

Add common synonyms and file cues a user might naturally say, such as 'plugin development', 'Gutenberg blocks', 'shortcodes', or '.php plugin', to broaden trigger coverage toward anchor 5.

Confirm the description reads in third person (it does — 'Scaffold...'); keep it that way and avoid any first/second-person phrasing if revised.

Dimension	Reasoning	Score
Specificity	The description enumerates multiple concrete capabilities — 'custom post types, meta boxes, REST API endpoints, admin settings pages, asset enqueuing, and WP-CLI commands' — giving comprehensive coverage of what the scaffold produces, matching the level-5 anchor that lists several specific concrete actions.	5 / 5
Completeness	It clearly answers 'what' (scaffold a plugin with the listed features) but contains no 'Use when...' clause or equivalent explicit trigger guidance, so per the judging guidelines completeness is capped at 3 even though the 'what' is strong.	3 / 5
Trigger Term Quality	Natural WordPress-domain terms a user would say are present ('WordPress plugin', 'custom post types', 'meta boxes', 'REST API', 'WP-CLI'), but common synonyms and extensions (e.g. 'plugin development', 'Gutenberg blocks', 'shortcodes', '.php') are missing, so it falls at good-but-not-comprehensive coverage rather than 5.	4 / 5
Distinctiveness Conflict Risk	'Scaffold a WordPress 6.x plugin' carves a clear niche with distinct WP-CLI/REST triggers and minimal conflict risk, but it could still overlap with broader WordPress development skills, placing it just below the minimal-conflict anchor 5.	4 / 5
	Total	16 / 20 Passed

Validation

81%

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 — 13 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (770 lines); consider splitting into references/ and linking	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
referenced_paths_exist	Referenced path issues: 4 missing, 4 deeper-than-1-level	Warning

	Total	13 / 16 Passed

Repository: achreftlili/deep-dev-skills
Path: backend-php/wordpress-plugin-starter/SKILL.md
Commit: 181fcbc

Reviewed: 1 day 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.