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.
67
62%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./backend-php/wordpress-plugin-starter/SKILL.mdQuality
Discovery
67%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description excels at specificity and distinctiveness, clearly defining WordPress plugin scaffolding with concrete technical capabilities. However, it lacks explicit trigger guidance ('Use when...') which is critical for Claude to know when to select this skill from a large pool. The trigger terms are adequate but could include more user-friendly variations.
Suggestions
Add a 'Use when...' clause with trigger phrases like 'Use when the user asks to create a WordPress plugin, scaffold WP functionality, or build custom WordPress features'
Include common variations of trigger terms such as 'WP plugin', 'WordPress extension', 'WordPress development', or 'build a plugin'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'custom post types, meta boxes, REST API endpoints, admin settings pages, asset enqueuing, and WP-CLI commands' - these are all distinct, concrete WordPress development capabilities. | 3 / 3 |
Completeness | Clearly answers 'what' with detailed scaffolding capabilities, but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. | 2 / 3 |
Trigger Term Quality | Contains good technical terms like 'WordPress', 'plugin', 'REST API', 'WP-CLI' that developers would use, but missing common variations like 'WP plugin', 'WordPress extension', or simpler terms like 'admin panel' or 'backend'. | 2 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with 'WordPress 6.x plugin' as a clear niche. The specific WordPress terminology (custom post types, meta boxes, WP-CLI) makes it unlikely to conflict with generic coding or other CMS skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
57%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides excellent, production-ready code examples covering all major WordPress plugin components with strong security practices (nonces, sanitization, escaping). However, it suffers from being overly long and monolithic—the extensive inline code would be better organized into separate reference files. The workflow section could benefit from explicit validation steps and error recovery guidance.
Suggestions
Split the extensive code examples into separate reference files (e.g., PATTERNS.md, REST_API.md, CLI.md) and keep SKILL.md as a concise overview with links to detailed documentation
Add explicit validation checkpoints to the 'First Steps After Scaffold' section, such as 'Verify activation succeeded: wp plugin list | grep my-awesome-plugin' and error recovery steps
Trim the Key Conventions section by removing items Claude already knows (e.g., basic security practices) and focus on WordPress-specific gotchas
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some unnecessary verbosity, such as explaining prerequisites that Claude would know and providing extensive inline code that could be referenced externally. However, it avoids explaining basic concepts and stays focused on WordPress-specific patterns. | 2 / 3 |
Actionability | Excellent actionability with fully executable, copy-paste ready code examples for every major component (main plugin file, post types, meta boxes, REST API, WP-CLI, settings pages). All code is complete and production-ready, not pseudocode. | 3 / 3 |
Workflow Clarity | The 'First Steps After Scaffold' section provides a clear sequence, but lacks explicit validation checkpoints. For example, there's no verification step after activation or guidance on what to do if the REST API endpoint check fails. | 2 / 3 |
Progressive Disclosure | The skill is a monolithic wall of text with all code inline. At 500+ lines, this content would benefit significantly from splitting into separate reference files (e.g., REST_API.md, METABOXES.md, CLI.md) with the main skill providing an overview and links. | 1 / 3 |
Total | 8 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 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 |
Total | 9 / 11 Passed | |
- Repository
- achreftlili/deep-dev-skills
- Commit
181fcbc
- 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.