woocommerce-backend-dev
Add or modify WooCommerce backend PHP code following project conventions. Use when creating new classes, methods, hooks, or modifying existing backend code in WooCommerce projects.
76
70%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/woocommerce-backend-dev/skills/woocommerce-backend-dev/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 is a competent description that clearly communicates both what the skill does and when to use it, with an explicit 'Use when' clause. However, it could be stronger by listing more specific concrete actions beyond the generic 'classes, methods, hooks' and by including more natural trigger terms that users would actually say when needing WooCommerce backend help.
Suggestions
Add more specific concrete actions like 'register custom post types, create payment gateways, add REST API endpoints, implement custom shipping methods' to improve specificity.
Expand trigger terms to include common variations users would say: 'WordPress', 'woo', 'plugin', 'action hook', 'filter', 'custom endpoint', '.php files'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (WooCommerce backend PHP) and some actions (creating classes, methods, hooks, modifying code), but doesn't list truly specific concrete actions like 'register custom post types, add REST API endpoints, create payment gateway integrations'. | 2 / 3 |
Completeness | Clearly answers both 'what' (add or modify WooCommerce backend PHP code following project conventions) and 'when' (when creating new classes, methods, hooks, or modifying existing backend code) with an explicit 'Use when' clause. | 3 / 3 |
Trigger Term Quality | Includes relevant keywords like 'WooCommerce', 'PHP', 'classes', 'methods', 'hooks', and 'backend code', but misses common user variations like 'plugin', 'filter', 'action hook', 'woo', 'WordPress', 'custom endpoint', or file extensions like '.php'. | 2 / 3 |
Distinctiveness Conflict Risk | Reasonably specific to WooCommerce backend PHP, but could overlap with general WordPress PHP skills, generic PHP coding skills, or WooCommerce frontend skills. The 'backend' qualifier helps but 'modifying existing backend code' is broad. | 2 / 3 |
Total | 9 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured hub skill that excels at progressive disclosure and conciseness, serving as an effective index to detailed sub-documents. Its main weakness is limited actionability in the skill itself—it lacks concrete code examples, specific CLI commands for linting/testing, and explicit validation workflows. The version information section is a standout for providing non-obvious, project-specific guidance.
Suggestions
Add specific linting and testing commands (e.g., `composer run phpcs`, `composer run phpunit`) to make the 'run linting and tests before committing' guidance actionable and copy-paste ready.
Include a brief workflow sequence with validation checkpoints, e.g., '1. Write code → 2. Run `composer run phpcs` → 3. Fix any issues → 4. Run `composer run phpunit` → 5. Only commit when both pass.'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. It doesn't explain what WooCommerce is, what PHP is, or how hooks work conceptually. Every section earns its place by pointing to specific resources or providing concrete, non-obvious project-specific information like the version numbering convention. | 3 / 3 |
Actionability | The skill provides specific guidance (e.g., namespace conventions, file placement in `src/Internal/`, version determination from a specific file), but the core content is mostly pointers to other files rather than executable code or commands. The version information section is concrete and actionable, but there are no code examples or specific commands for linting/testing. | 2 / 3 |
Workflow Clarity | The instructions list steps but they read more as a reference index than a workflow sequence. There's a mention of 'run linting and tests before committing' but no specific commands, validation checkpoints, or feedback loops for error recovery. For a skill involving code modification, explicit validate-fix-retry steps would strengthen this. | 2 / 3 |
Progressive Disclosure | Excellent progressive disclosure with a clear overview and well-signaled one-level-deep references to seven specific sub-documents. Each reference is clearly labeled with its purpose, making navigation easy and keeping the main skill file concise. | 3 / 3 |
Total | 10 / 12 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- secondsky/claude-skills
- Commit
88da5ff
- 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.