woocommerce-backend-dev

Add or modify WooCommerce backend PHP code following project conventions. Use when creating new classes, methods, hooks, or modifying existing backend code in WooCommerce projects.

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/woocommerce-backend-dev/skills/woocommerce-backend-dev/SKILL.md

Quality

Content

68%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 an efficient, well-organized hub that delegates detail to reference files, but it offers little inline executable guidance and lacks validation checkpoints for code changes. Referenced files are also absent from the bundle.

Suggestions

Add a brief inline code example or command for the most common backend task so the body is actionable without requiring every reference file.

Include a validation/checkpoint step (e.g. run linting and tests before committing) in the main instructions to support the destructive nature of code modifications.

Ensure the referenced files (file-entities.md, code-entities.md, coding-conventions.md, hooks.md, dependency-injection.md, data-integrity.md, unit-tests.md) actually exist in the bundle.

Dimension	Reasoning	Score
Conciseness	Lean and efficient; no padding and no explanation of concepts Claude already knows. Every line earns its place.	5 / 5
Actionability	The body is mostly a list of pointers to reference files ("See [file-entities.md] for conventions") with no inline concrete code or commands; the version-determination section is actionable but the core guidance is indirect.	3 / 5
Workflow Clarity	A rough sequence exists (instructions list plus a clear version-numbering procedure), but there are no validation checkpoints for code modifications, which are batch/destructive operations on a codebase — capping this at 3.	3 / 5
Progressive Disclosure	Good structure as an overview pointing to one-level-deep references, each clearly signaled by topic; however the referenced bundle files (file-entities.md, code-entities.md, etc.) are not present in the bundle to fully verify the split.	4 / 5
	Total	15 / 20 Passed

Description

87%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-targeted description that explicitly covers both what the skill does and when to use it, with concrete domain-specific trigger terms. Minor gaps in keyword synonyms keep trigger quality just below maximum.

Dimension	Reasoning	Score
Specificity	Names the domain and several concrete actions ("creating new classes, methods, hooks, or modifying existing backend code"), with only minor coverage gaps relative to a fully comprehensive list.	4 / 5
Completeness	Clearly states what it does ("Add or modify WooCommerce backend PHP code following project conventions") and gives an explicit "Use when..." clause with concrete trigger phrases.	5 / 5
Trigger Term Quality	Good natural keyword coverage ("WooCommerce", "PHP", "classes, methods, hooks", "backend code") but misses common synonyms and file extensions like .php.	4 / 5
Distinctiveness Conflict Risk	A clear WooCommerce-backend niche with distinct triggers; minimal conflict risk with other skills.	5 / 5
	Total	18 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
relative_links	Relative link issues: 8 missing	Warning

	Total	15 / 16 Passed

Repository: secondsky/claude-skills
Path: plugins/woocommerce-backend-dev/skills/woocommerce-backend-dev/SKILL.md
Commit: ad16332

Reviewed: 12 days ago

Table of Contents

Discovery Implementation Validation

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.