Guidelines for UI text and copy in WooCommerce. Use when writing user-facing text, labels, buttons, messages, or documentation in WooCommerce projects.
80
70%
Does it follow best practices?
Impact
100%
1.23xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/woocommerce-copy-guidelines/skills/woocommerce-copy-guidelines/SKILL.mdQuality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-structured skill description with a clear 'Use when' clause and good trigger term coverage. The main weakness is the somewhat vague 'Guidelines for' framing which doesn't specify concrete actions the skill performs (e.g., 'write', 'review', 'format'). Overall, it effectively communicates when to select this skill.
Suggestions
Replace 'Guidelines for' with specific action verbs like 'Write and review UI text and copy' to clarify what the skill actually does
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (UI text/copy in WooCommerce) and lists some actions (writing text, labels, buttons, messages, documentation), but 'Guidelines for' is somewhat vague about what concrete actions the skill performs. | 2 / 3 |
Completeness | Clearly answers both what (guidelines for UI text and copy in WooCommerce) and when (explicit 'Use when' clause with specific triggers: writing user-facing text, labels, buttons, messages, or documentation in WooCommerce projects). | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'UI text', 'copy', 'labels', 'buttons', 'messages', 'documentation', 'WooCommerce', 'user-facing text'. Good coverage of terms a developer would use when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche combining WooCommerce-specific context with UI text/copy focus. The combination of 'WooCommerce' + 'UI text/copy/labels/buttons' creates distinct triggers unlikely to conflict with general writing or other e-commerce skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is extremely concise but lacks actionability - it tells Claude what to do ('use sentence case', 'be consistent') without showing how. The key principles are abstract guidelines without concrete examples of good/bad copy, making it difficult for Claude to apply them correctly. The content essentially serves as a pointer to another file rather than a useful standalone reference.
Suggestions
Add concrete before/after examples for each key principle (e.g., 'Bad: Add To Cart' → 'Good: Add to cart')
Include specific examples of WooCommerce copy patterns for common UI elements like buttons, error messages, and labels
Expand the key principles with actionable guidance rather than abstract directives (e.g., what does 'action-oriented' look like in practice?)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, with no unnecessary explanations. Every line serves a purpose and assumes Claude's competence with basic concepts. | 3 / 3 |
Actionability | The content provides only vague principles ('use sentence case', 'keep copy concise') without concrete examples of good vs bad copy, specific patterns, or executable guidance. The actual rules are deferred to another file. | 1 / 3 |
Workflow Clarity | For a simple guideline skill, the single instruction to follow sentence-case.md is clear, but the 'Key Principles' section lists items without explaining how to apply them or what constitutes violations. | 2 / 3 |
Progressive Disclosure | References sentence-case.md appropriately, but the SKILL.md itself is too sparse - it lists principles without enough substance to be useful as an overview. The balance between overview and reference is off. | 2 / 3 |
Total | 8 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
90d6bd7
Table of Contents
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.