woocommerce-dev-cycle
Run tests, linting, and quality checks for WooCommerce development. Use when running tests, fixing code style, or following the development workflow in WooCommerce projects.
79
73%
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-dev-cycle/skills/woocommerce-dev-cycle/SKILL.mdQuality
Discovery
89%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 solid skill description that clearly communicates its purpose and when to use it. It benefits from the explicit 'Use when...' clause and WooCommerce-specific scoping that makes it distinctive. The main weakness is that the capabilities could be more granular—listing specific tools or actions (e.g., PHPUnit, PHPCS, PHPStan) rather than general categories.
Suggestions
List more specific concrete actions such as 'run PHPUnit tests, execute PHPCS linting, perform PHPStan static analysis' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (WooCommerce development) and some actions (tests, linting, quality checks), but doesn't list specific concrete actions like 'run PHPUnit tests, execute PHPCS linting, run PHPStan analysis'. The actions are somewhat general categories rather than detailed specifics. | 2 / 3 |
Completeness | Clearly answers both 'what' (run tests, linting, and quality checks for WooCommerce development) and 'when' (Use when running tests, fixing code style, or following the development workflow in WooCommerce projects) with an explicit 'Use when...' clause. | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'tests', 'linting', 'quality checks', 'code style', 'development workflow', 'WooCommerce'. These are terms a developer would naturally use when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | The combination of WooCommerce-specific context with testing/linting/quality checks creates a clear niche. The 'WooCommerce projects' qualifier strongly distinguishes it from generic testing or linting skills. | 3 / 3 |
Total | 11 / 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 is a reasonably well-structured skill that effectively uses progressive disclosure to organize WooCommerce development guidance across multiple files. Its main weaknesses are some unnecessary explanatory content that Claude doesn't need, and a workflow that lacks explicit validation/feedback loops for error recovery. The inline commands are helpful but the skill could be tighter.
Suggestions
Remove or trim the Key Principles section — most points are obvious to Claude (e.g., 'run tests after making changes', 'test failures provide detailed output').
Add an explicit feedback loop to the Development Workflow: after step 4 (fix issues), loop back to re-run linting/tests before proceeding to commit.
Remove the introductory sentence 'This skill provides guidance for the WooCommerce development workflow, including running tests, code quality checks, and troubleshooting' as it adds no actionable value.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient but includes some unnecessary statements like 'This skill provides guidance for the WooCommerce development workflow' and the Key Principles section contains some obvious advice Claude already knows (e.g., 'Always run tests after making changes to verify functionality', 'Test failures provide detailed output showing expected vs actual values'). | 2 / 3 |
Actionability | The Development Workflow section provides concrete commands which is good, but the main skill body delegates most actionable content to referenced files. The inline commands are specific and executable, but key details like test environment setup are deferred. | 2 / 3 |
Workflow Clarity | The 5-step development workflow is clearly sequenced with concrete commands, but lacks explicit validation checkpoints and feedback loops. Step 5 says 'commit changes only after tests pass' but doesn't specify what to do if tests fail or how to iterate on failures. | 2 / 3 |
Progressive Disclosure | Excellent structure with a clear overview and well-signaled one-level-deep references to four specific sub-files (running-tests.md, code-quality.md, php-linting-patterns.md, markdown-linting.md). The main file stays concise while pointing to detailed materials. | 3 / 3 |
Total | 9 / 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
40506e5
- 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.