CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

64

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/woocommerce-dev-cycle/skills/woocommerce-dev-cycle/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is concise and offers concrete executable commands within a clear sequenced workflow, but its progressive disclosure is undermined by four referenced files that do not exist in the bundle, breaking navigation to the detailed guidance.

Suggestions

Add the four referenced bundle files (running-tests.md, code-quality.md, php-linting-patterns.md, markdown-linting.md) to the references/ directory so the linked guidance is actually reachable.

Add an explicit feedback loop in the Development Workflow (e.g., "If tests fail, review expected vs actual output, fix, and re-run tests before committing") to strengthen validation.

Tighten the "Key Principles" section by removing guidance that restates the workflow steps above it, reducing token use.

DimensionReasoningScore

Conciseness

The body is lean (~30 lines) with executable commands and no padding about concepts Claude already knows, though the "Key Principles" section restates some guidance that could be trimmed, keeping it just below the lean/efficient anchor.

4 / 5

Actionability

Provides concrete executable commands ("pnpm run test:php:env -- --filter YourTestClass", "pnpm run lint:changes:branch:php", "pnpm run lint:php:fix") with minor gaps, but the detailed guidance is offloaded to four referenced files that are not present in the bundle.

4 / 5

Workflow Clarity

The Development Workflow is a clear five-step sequence with a verification checkpoint ("Commit changes only after tests pass"), but it lacks an explicit failure feedback loop (if tests fail, fix and re-run), leaving minor validation gaps.

4 / 5

Progressive Disclosure

The body is well-sectioned with clearly signaled one-level-deep references to four .md files, but none of those referenced files exist in the bundle, so the navigation paths are broken and the promised detail is unreachable.

3 / 5

Total

15

/

20

Passed

Description

82%Weight 40%Scale 1-5

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 strong: it clearly states what the skill does and when to use it with natural trigger phrases, and is well-scoped to a distinct WooCommerce niche. Its only weakness is that the listed capabilities are somewhat broad categories rather than a comprehensive set of specific actions.

DimensionReasoningScore

Specificity

Names the domain (WooCommerce development) and three concrete action categories ("Run tests, linting, and quality checks"), but the actions are broad categories rather than comprehensive specific capabilities, matching the anchor for naming a domain with a few concrete actions but not full coverage.

3 / 5

Completeness

Explicitly 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 concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural phrases users would say ("running tests, fixing code style, or following the development workflow") scoped to WooCommerce, giving good keyword coverage, though it misses some common synonyms like "linting errors" or "CI".

4 / 5

Distinctiveness Conflict Risk

"WooCommerce development" is a clear niche with distinct, project-scoped triggers and minimal risk of firing for unrelated skills.

5 / 5

Total

17

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 4 missing

Warning

Total

15

/

16

Passed

Repository
secondsky/claude-skills
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.