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

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No known issues

Quality

Content

65%

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

The body is concise and free of padding, with a genuinely useful version-lookup procedure and specific conventions. Its main weakness is that it functions as a reference hub pointing to six detail files that are not actually bundled, leaving the core guidance incomplete and the progressive disclosure broken.

Suggestions

Bundle the six referenced files (file-entities.md, code-entities.md, coding-conventions.md, hooks.md, dependency-injection.md, data-integrity.md, unit-tests.md) in ./references/ so the progressive-disclosure links resolve and the core guidance is complete.

Add a concrete, copy-paste-ready code or command example for at least the most common task (e.g. a minimal hook callback class under src/Internal/) to lift actionability toward 3.

Insert an explicit validation checkpoint in the workflow (e.g. 'run `composer lint` and `phpunit` before committing') so the multi-step guidance has a verifiable feedback loop.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence — it never explains concepts Claude already knows (e.g. what WooCommerce or hooks are) and nearly every token earns its place, including the non-obvious version-lookup procedure.	3 / 3
Actionability	Some guidance is concrete and actionable (e.g. 'Place new internal classes in `src/Internal/`', 'PSR-4 autoloading with `Automattic\WooCommerce` namespace', the version-lookup steps), but the primary instruction list defers to reference files that are not present and there is no copy-paste-ready code.	2 / 3
Workflow Clarity	The version-numbering section is a clear sequenced procedure, but there are no explicit validation checkpoints or feedback loops, and the main content is a navigation index to absent detail files rather than a multi-step workflow with checkpoints.	2 / 3
Progressive Disclosure	The SKILL.md is a well-organized, well-signaled hub pointing one level deep to six reference files, but none of those referenced files exist in references/, scripts/, or assets/, so the disclosure leads nowhere and cannot score 3.	2 / 3
	Total	9 / 12 Passed

Description

100%

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, concise description that clearly states the skill's purpose and provides an explicit 'Use when' trigger scoped to WooCommerce backend PHP work. It is specific, naturally worded, and unlikely to conflict with other skills.

Dimension	Reasoning	Score
Specificity	Names multiple concrete actions — 'Add or modify WooCommerce backend PHP code', 'creating new classes, methods, hooks, or modifying existing backend code' — matching the 'lists multiple specific concrete actions' anchor.	3 / 3
Completeness	Explicitly answers both what ('Add or modify WooCommerce backend PHP code following project conventions') and when via a clear 'Use when ...' trigger clause, so it is not capped at 2.	3 / 3
Trigger Term Quality	Uses natural terms a user would say ('WooCommerce backend PHP code', 'classes, methods, hooks') with good coverage of the domain vocabulary rather than abstract jargon.	3 / 3
Distinctiveness Conflict Risk	Targets a clear niche (WooCommerce backend PHP) with distinct triggers unlikely to overlap with generic skills, and uses correct third-person voice.	3 / 3
	Total	12 / 12 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
Commit: c4889f6

Reviewed: 1 day 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.