CtrlK
BlogDocsLog inGet started
Tessl Logo

woocommerce-copy-guidelines

Guidelines for UI text and copy in WooCommerce. Use when writing user-facing text, labels, buttons, messages, or documentation in WooCommerce projects.

58

Quality

67%

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-copy-guidelines/skills/woocommerce-copy-guidelines/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%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 skill body is admirably lean and well-sectioned, but it offers almost no actionable, concrete copy guidance — mostly abstract principles — and its single external reference points to a file that is not present in the bundle.

Suggestions

Add concrete before/after examples for each principle (e.g., 'Settings' vs 'Settings & Configuration', button 'Save changes' vs 'Submit') so the guidance is executable rather than abstract.

Provide the missing sentence-case.md reference file (under references/), or inline the sentence-case rules directly so the link is not dangling.

Flesh out the 'Instructions' section with the actual copy rules (capitalization, button verb conventions, error-message tone) instead of a single pointer.

DimensionReasoningScore

Conciseness

The body is short and lean with no padding or explanation of concepts Claude already knows; every line states a guideline or points to a reference, fitting the 'lean and efficient; every token earns its place' anchor.

5 / 5

Actionability

The guidance is almost entirely abstract principles ('Keep copy concise', 'Use clear, simple language') with no before/after examples or concrete rules beyond 'use sentence case, not title case', matching the 'minimal concrete guidance; high-level hints but missing specific steps' anchor rather than 1 only because the sentence-case rule is at least concrete.

2 / 5

Workflow Clarity

There is a single-step instruction ('Follow these guidelines...') plus a pointer to sentence-case.md, but no clear sequence or checkpoints; for a simple skill the action is only partially unambiguous because 'follow these guidelines' is vague, landing at the mid anchor.

3 / 5

Progressive Disclosure

The body is sectioned and signals a one-level reference to sentence-case.md, but no bundle directory exists so that referenced file is absent, breaking navigation — structure is present but the signaled reference does not resolve to real content.

3 / 5

Total

13

/

20

Passed

Description

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

The description cleanly answers both what the skill does and when to use it, with a distinct WooCommerce niche and natural trigger terms. Its main weakness is specificity — it describes the domain more than concrete actions.

Suggestions

Lead with concrete verbs (e.g., 'Write, edit, and review user-facing copy in WooCommerce') instead of the generic 'Guidelines for' framing.

Add a few natural synonyms or variation phrases (e.g., 'microcopy', 'UI strings', 'admin notices') to broaden trigger coverage.

DimensionReasoningScore

Specificity

The description names the domain ('UI text and copy in WooCommerce') but the only action is the generic 'writing/guidelines for', with no concrete operations like 'write', 'rewrite', or 'review' — matching the 'names the domain but actions are minimal or generic' anchor rather than the 3-anchor which requires 1-2 concrete actions.

2 / 5

Completeness

It explicitly answers both 'what' ('Guidelines for UI text and copy in WooCommerce') and 'when' ('Use when writing user-facing text, labels, buttons, messages, or documentation in WooCommerce projects') with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

It surfaces natural trigger terms a user would say ('writing user-facing text, labels, buttons, messages, or documentation') with good coverage of copy types, though it lacks synonyms or file-extension-style variants that would push it to 5.

4 / 5

Distinctiveness Conflict Risk

'WooCommerce' carves out a clear niche with distinct triggers, and the copy-writing scope is specific enough to minimize conflict with other skills.

5 / 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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 1 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.