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.
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-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 an explicit 'Use when...' clause and strong domain scoping to WooCommerce. The main weakness is that the capability descriptions could be more specific about the exact tools and actions involved (e.g., PHPUnit, PHPCS, specific commands).
Suggestions
Add more specific concrete actions such as 'run PHPUnit tests, execute PHPCS linting, validate coding standards' to improve specificity beyond general categories.
| 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, check coding standards'. The actions are somewhat general categories rather than detailed operations. | 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 | Clearly scoped to WooCommerce projects specifically, combining testing/linting/quality checks with the WooCommerce domain. This is a distinct niche unlikely to conflict with generic testing or linting skills due to the WooCommerce qualifier. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill provides a reasonable overview of the WooCommerce development workflow with concrete commands and clear references to supporting files. However, it includes some unnecessary filler content, lacks explicit error recovery/feedback loops in the workflow, and the referenced bundle files are not provided to verify the progressive disclosure structure. The Key Principles section adds little value beyond what Claude already knows.
Suggestions
Add an explicit feedback loop to the workflow: e.g., 'If tests fail: read the error output, fix the issue, re-run the specific failing test, then proceed'
Remove the Key Principles section or reduce it to only non-obvious project-specific constraints (e.g., 'Fix linting errors solely for code in your current branch' is useful; 'Test failures provide detailed output' is not)
Remove the introductory sentence ('This skill provides guidance...') and the off-topic note about bun vs pnpm for other projects
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient but includes some unnecessary filler like 'This skill provides guidance for the WooCommerce development workflow' and the Key Principles section restates things Claude already knows (e.g., 'test failures provide detailed output showing expected vs actual values'). The note about bun vs pnpm for other projects is off-topic. | 2 / 3 |
Actionability | The Development Workflow section provides concrete, executable commands (pnpm run test:php:env, pnpm run lint:changes:branch:php, pnpm run lint:php:fix), but the main content delegates most actionable detail to referenced files. Without the bundle files, the skill itself provides only a surface-level workflow with a few commands. | 2 / 3 |
Workflow Clarity | The 5-step development workflow is clearly sequenced and includes a validation checkpoint ('Commit changes only after tests pass'), but lacks explicit feedback loops for error recovery (e.g., what to do if tests fail, how to iterate). The instruction to 'fix any issues' is vague without guidance on diagnosing failures. | 2 / 3 |
Progressive Disclosure | The skill references four separate markdown files with clear descriptions, which is good progressive disclosure structure. However, no bundle files were provided, so the referenced files (running-tests.md, code-quality.md, etc.) cannot be verified to exist. The overview itself is appropriately concise and delegates detail, but the references are unverifiable. | 2 / 3 |
Total | 8 / 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.