CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

woocommerce-code-review

Review WooCommerce code changes for coding standards compliance. Use when reviewing code locally, performing automated PR reviews, or checking code quality in WooCommerce projects.

65

Quality

82%

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

SKILL.md
Quality
Evals
Security

Quality

Content

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

A tight, actionable review checklist with clear structure, a defined output format, and well-signaled one-level-deep references. The main weaknesses are a redundant Notes section, absence of an explicit coverage checkpoint in the review workflow, and total dependence on external sibling skills for the detailed standards the skill promises to cite.

Suggestions

Delete or collapse the Notes section — all three bullets restate the inline 'Consult the <skill>' pointers already given in each section, saving tokens without losing information.

Add an explicit checkpoint to the Review Approach, e.g. a final step 'Confirm every file in the diff and every violation category above was checked before reporting', so reviews don't stop at the first finding.

Inline one-line right/wrong examples for the highest-frequency rules (snake_case, $container->get(), $sut) so the skill remains actionable when the woocommerce-backend-dev sibling skill is not installed.

DimensionReasoningScore

Conciseness

The body is a lean, well-scoped checklist of violations with brief rules and one-line justifications, assuming Claude's competence throughout. The only padding is the Notes section, whose three bullets ("All detailed standards are in the... skills", "Consult those skills", "refer to the specific skill documentation linked above") restate what every preceding section already says inline — anchor 4 (efficient, minor trimmable instances) rather than 5.

4 / 5

Actionability

Rules are concrete and specific — "Must use `$sut` variable name", "Required `@testdox`", "Must use snake_case", wrong/correct title-case examples, and a copy-paste output-format template. However, the actual standards detail is deferred to sibling skill files ("Consult the `woocommerce-backend-dev` skill for detailed standards") that are not part of this skill's own bundle, so an agent can only execute fully when those siblings are installed — mostly executable with minor gaps, anchor 4.

4 / 5

Workflow Clarity

The five-step Review Approach (scan violations, cite skill files, provide correct examples, group related issues, be constructive) plus the structured output format gives a clear, unambiguous sequence. There is no explicit checkpoint (e.g. confirming every file in the diff was scanned or that all violation categories were checked); since reviewing is read-only and non-destructive, the missing-validation cap does not apply — anchor 4, not 5, due to the absent checkpoints.

4 / 5

Progressive Disclosure

The body is a well-organized overview with one-level-deep, clearly signaled per-topic links ([file-entities.md](../woocommerce-backend-dev/file-entities.md), [sentence-case.md](../woocommerce-copy-guidelines/sentence-case.md)). The structure matches the good pattern, but the references point to external sibling skills rather than files in this skill's own bundle (no references/ directory exists, and the linked siblings are not present in this environment), so navigation depends on the surrounding installation — anchor 4 rather than 5.

4 / 5

Total

16

/

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.

A concise, well-constructed description that clearly states what the skill does and when to use it, with a distinct WooCommerce-scoped niche. Its only weakness is that it names a single concrete action and leans on usage contexts rather than enumerating several specific capabilities.

DimensionReasoningScore

Specificity

"Review WooCommerce code changes for coding standards compliance" names the domain and one concrete action, but the remaining clauses ("reviewing code locally, performing automated PR reviews, or checking code quality") describe usage contexts rather than additional capabilities. It fits anchor 3 (domain plus 1-2 concrete actions, not comprehensive) better than 4, which expects several listed actions.

3 / 5

Completeness

It explicitly answers both questions: the "what" ("Review WooCommerce code changes for coding standards compliance") and the "when" with a concrete "Use when..." clause listing three trigger scenarios. This matches the anchor-5 example pattern of clear what plus explicit trigger phrases.

5 / 5

Trigger Term Quality

Natural phrases a user would say are present — "reviewing code locally", "automated PR reviews", "checking code quality", "WooCommerce" — giving good synonym coverage. A few natural terms are missing (e.g. "lint", "conventions"), so it matches anchor 4 rather than the comprehensive synonym/extension coverage of anchor 5.

4 / 5

Distinctiveness Conflict Risk

The WooCommerce-specific niche ("WooCommerce code changes", "WooCommerce projects") gives it distinct triggers with minimal overlap risk against generic code-review or linting skills. It matches anchor 5: clear niche, distinct triggers, minimal conflict risk.

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 13 suspicious

Warning

Total

15

/

16

Passed

Repository

secondsky/claude-skills

Path

plugins/woocommerce-code-review/skills/woocommerce-code-review/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.