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.
70
62%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
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 solid description that clearly communicates its purpose and when to use it. The 'Use when...' clause with multiple trigger terms is well-constructed. The main weakness is that the 'what' portion is somewhat abstract—'guidelines for UI text' doesn't specify concrete actions like reviewing, writing, or enforcing specific style rules.
Suggestions
Add specific concrete actions to the description, e.g., 'Provides tone, capitalization, and formatting guidelines for writing UI text in WooCommerce' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (UI text/copy in WooCommerce) and lists some types of content (labels, buttons, messages, documentation), but doesn't describe concrete actions like 'write error messages', 'create button labels following tone guidelines', or 'review copy for consistency'. | 2 / 3 |
Completeness | Clearly answers both 'what' (guidelines for UI text and copy in WooCommerce) and 'when' with an explicit 'Use when...' clause listing specific trigger scenarios (writing user-facing text, labels, buttons, messages, or documentation in WooCommerce projects). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'UI text', 'copy', 'labels', 'buttons', 'messages', 'documentation', 'WooCommerce', and 'user-facing text'. These cover common variations of how someone would describe this need. | 3 / 3 |
Distinctiveness Conflict Risk | The combination of 'WooCommerce' with 'UI text and copy' creates a clear niche. It's unlikely to conflict with general coding skills, general writing skills, or other e-commerce skills due to the specific focus on copy/text guidelines within WooCommerce. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
35%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is a thin skeleton that provides almost no actionable guidance for writing WooCommerce copy. The key principles are generic writing advice that Claude already knows, and the only concrete rule (sentence case) is entirely deferred to another file. The skill needs substantial concrete examples of good and bad WooCommerce copy patterns to be useful.
Suggestions
Add concrete before/after examples of WooCommerce UI copy (e.g., button labels, error messages, success messages) showing correct vs incorrect patterns.
Replace generic principles like 'Use clear, simple language' with specific, actionable rules (e.g., 'Use verbs for buttons: "Add to cart" not "Cart addition"; limit button text to 3 words').
Add more referenced sub-files or inline sections covering specific copy contexts: error messages, confirmation dialogs, empty states, tooltips, etc.
Remove the introductory sentence that restates the skill description—start directly with the instructions or key principles.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The opening sentence restates what the YAML description already says, and 'This skill provides guidelines for...' is unnecessary preamble. The Key Principles section has some filler ('Be consistent with existing WooCommerce copy patterns' is vague). However, it's relatively short overall. | 2 / 3 |
Actionability | The content provides only vague, high-level guidance ('Keep copy concise and action-oriented', 'Use clear, simple language') with no concrete examples of good vs bad copy, no specific patterns, and no executable guidance. The only concrete rule (sentence case) is deferred to another file. | 1 / 3 |
Workflow Clarity | This is a simple instruction-only skill with no multi-step process, so a clear single action could score 3. However, the instructions are too vague to be unambiguous—there's no clear workflow for how to apply these guidelines when writing copy, and the key principles are generic platitudes without specifics. | 2 / 3 |
Progressive Disclosure | There is a reference to sentence-case.md which is good progressive disclosure, but the skill only references one sub-file and the main content is too thin to serve as a useful overview. Additional references for other copy patterns (error messages, button text, etc.) would improve navigation. | 2 / 3 |
Total | 7 / 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.
- Repository
- secondsky/claude-skills
- Commit
88da5ff
- 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.