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.

60

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No known issues

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

50%

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

The body is reasonably lean and contains real executable pnpm commands, with a clear sequenced workflow. Its main weaknesses are restated filler, a missing failure-retry feedback loop, and four reference links pointing to files that are not bundled.

Suggestions

Drop the redundant intro paragraph and the 'Follow these guidelines for WooCommerce development workflow:' lead-in, which restate the frontmatter description, so the body opens directly with actionable content.

Add an explicit feedback loop to the Development Workflow (e.g., 'If tests or linting fail, fix the issue and re-run until both pass before committing') to satisfy workflow-clarity level 3.

Either create the referenced bundle files (running-tests.md, code-quality.md, php-linting-patterns.md, markdown-linting.md) or inline their essential content, since the current links resolve to nothing and break progressive-disclosure navigation.

DimensionReasoningScore

Conciseness

Mostly efficient, but the opening paragraph ('This skill provides guidance for the WooCommerce development workflow...') and the 'Follow these guidelines for WooCommerce development workflow:' line restate the description and could be trimmed; it is not a clean level-3 'every token earns its place'.

2 / 3

Actionability

Concrete copy-paste commands appear ('pnpm run test:php:env -- --filter YourTestClass', 'pnpm run lint:php:fix'), but the bulk of detailed guidance is delegated to four reference files that do not exist, leaving the actionable guidance incomplete.

2 / 3

Workflow Clarity

The five-step Development Workflow is sequenced with a commit-only-after-tests-pass checkpoint, but it lacks an explicit validate-fix-retry feedback loop, so it sits at 'steps listed but validation gaps' rather than level 3.

2 / 3

Progressive Disclosure

Sections are well-organized and references are clearly signaled one level deep, but the linked files (running-tests.md, code-quality.md, php-linting-patterns.md, markdown-linting.md) are absent from the bundle, so navigation leads nowhere — structure is present but undermined.

2 / 3

Total

8

/

12

Passed

Description

90%

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 well-constructed description with an explicit 'Use when' trigger, third-person voice, and a clear WooCommerce niche. The only weakness is mild genericness in 'quality checks' rather than enumerating concrete actions.

DimensionReasoningScore

Specificity

Names the domain and several actions ('Run tests, linting, and quality checks'), but 'quality checks' is generic and the action set is not comprehensive, matching the anchor that names a domain and some actions.

2 / 3

Completeness

Explicitly states what it does ('Run tests, linting, and quality checks for WooCommerce development') and when to use it via an explicit 'Use when...' clause, satisfying both halves.

3 / 3

Trigger Term Quality

Covers natural phrases a user would say — 'running tests', 'fixing code style', 'linting', 'development workflow', 'WooCommerce projects' — giving good coverage of likely trigger terms.

3 / 3

Distinctiveness Conflict Risk

Scoped specifically to WooCommerce development with WooCommerce-specific triggers, giving it a clear niche unlikely to fire for unrelated skills.

3 / 3

Total

11

/

12

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.