CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

63

Quality

79%

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 body is efficient and actionable with a clear test-lint-fix-commit workflow built on concrete pnpm commands. Its critical weakness is that every detailed reference file it points to is missing from the bundle, leaving the progressive-disclosure structure broken and most substantive detail inaccessible.

Suggestions

Include the four referenced files (running-tests.md, code-quality.md, php-linting-patterns.md, markdown-linting.md) in the bundle (e.g., under references/), or inline the essential details they were meant to hold.

Add an explicit feedback loop after test/lint failures, e.g. "If tests fail: read the expected-vs-actual output, fix, and re-run the same filtered command before proceeding".

Trim redundancy: the intro sentence duplicates the frontmatter description and "Key Principles" repeats workflow steps already stated above.

DimensionReasoningScore

Conciseness

The body is lean with concrete commands and no concept explanations, but the intro sentence duplicates the description and the "Key Principles" section repeats steps already in the workflow ("Always run tests after making changes"), matching the minor-trimming anchor 4.

4 / 5

Actionability

Concrete, copy-paste-ready pnpm commands ("pnpm run test:php:env -- --filter YourTestClass", "pnpm run lint:changes:branch:php", "pnpm run lint:php:fix") anchor the guidance, but common cases like JavaScript testing and environment setup are deferred to files that are not in the bundle, matching anchor 4 rather than fully-covered anchor 5.

4 / 5

Workflow Clarity

The 5-step development workflow is clearly sequenced with a validation gate ("Commit changes only after tests pass"), but there is no explicit fix-and-re-run feedback loop after failures, matching anchor 4 rather than the explicit-feedback-loop anchor 5.

4 / 5

Progressive Disclosure

References are clearly signaled and one level deep, but all four referenced files (running-tests.md, code-quality.md, php-linting-patterns.md, markdown-linting.md) are absent from the bundle — no references/ directory exists — so navigation is broken and the detailed content is unreachable, matching anchor 3 rather than the resolvable-references anchor 4.

3 / 5

Total

15

/

20

Passed

Description

78%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.

A strong description that clearly states what the skill does and when to use it with natural trigger phrases, appropriately scoped to WooCommerce. Its main weaknesses are slightly overlapping capability terms ("quality checks") and missing common trigger synonyms such as "unit tests" or "lint".

DimensionReasoningScore

Specificity

"Run tests, linting, and quality checks" names the domain and concrete actions, but "quality checks" is vague and overlaps with the other two, leaving coverage non-comprehensive as in the anchor for 3 rather than the fuller action list of 4.

3 / 5

Completeness

It 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, matching anchor 5.

5 / 5

Trigger Term Quality

"running tests, fixing code style, or following the development workflow in WooCommerce projects" uses natural phrases users would say, but common variations like "unit tests", "PHPUnit", or "lint" are missing, matching the good-but-not-comprehensive anchor 4.

4 / 5

Distinctiveness Conflict Risk

The WooCommerce scoping gives it a clear niche with distinct triggers, but "running tests" and "fixing code style" overlap with generic test/lint skills, matching the mostly-distinct anchor 4 rather than the minimal-conflict anchor 5.

4 / 5

Total

16

/

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 4 missing

Warning

Total

15

/

16

Passed

Repository

secondsky/claude-skills

Path

plugins/woocommerce-dev-cycle/skills/woocommerce-dev-cycle/SKILL.md

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.