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.
60
70%
Does it follow best practices?
Impact
—
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.
The description is functional with a clear 'what' and 'when' structure, making it complete. However, it could be more specific in listing concrete actions beyond generic terms like 'classes, methods, hooks' and could include more natural trigger terms that users would actually say when requesting WooCommerce backend work. The distinctiveness is moderate—it would benefit from sharper differentiation from general WordPress/PHP skills.
Suggestions
Add more specific concrete actions like 'register custom post types, create payment gateway integrations, add REST API endpoints, implement custom shipping methods' to improve specificity.
Expand trigger terms to include natural variations users would say: 'WordPress plugin', 'action hooks', 'filters', 'woo', 'custom endpoint', '.php files', 'WooCommerce extension'.
| 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/overview skill that effectively delegates detailed guidance to topic-specific files. Its strengths are excellent progressive disclosure and concise presentation. Its weaknesses are the lack of executable code examples in the main file and the absence of an explicit development workflow with validation checkpoints (linting/testing steps should be more prominent as a sequential process).
Suggestions
Add a brief sequential workflow section (e.g., '1. Write code → 2. Run linting: `composer run lint` → 3. Run tests: `composer run test` → 4. Fix issues → 5. Commit') with actual commands to improve both actionability and workflow clarity.
Include at least one minimal executable code example showing the namespace/class structure pattern (e.g., a skeleton class in `src/Internal/`) to make the skill more immediately actionable without needing to consult referenced files.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. It doesn't explain what WooCommerce is or how PHP works. Every section serves a purpose—references, key principles, and version info are all concise and non-redundant. The 'Key Principles' section is a tight bullet list of project-specific conventions. | 3 / 3 |
Actionability | The skill provides specific guidance (e.g., 'Place new internal classes in src/Internal/', the version number derivation process with a concrete example), but the main body delegates almost all concrete instructions to referenced files. Without those bundle files available, the SKILL.md itself lacks executable code or copy-paste-ready commands. The version information section is the most actionable part. | 2 / 3 |
Workflow Clarity | The numbered list provides a logical organization of concerns but doesn't represent a sequential workflow with validation checkpoints. The mention of 'Run linting and tests before committing changes' is a validation step but is buried in Key Principles rather than being an explicit checkpoint in a workflow. For a skill involving code modification (potentially destructive), a clearer develop-validate-commit workflow would be beneficial. | 2 / 3 |
Progressive Disclosure | The skill is an excellent overview document with well-signaled, one-level-deep references to seven specific topic files. Each reference is clearly labeled with its purpose and linked to a specific markdown file. The content appropriately splits detailed conventions into separate files while keeping the overview navigable. | 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
5e92b71
- 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.