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.
56
62%
Does it follow best practices?
Impact
—
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 with explicit 'Use when' guidance and good trigger term coverage specific to WooCommerce UI copywriting. Its main weakness is that the 'what' portion is somewhat vague—'Guidelines for' doesn't convey concrete actions the skill performs (e.g., writing, reviewing, formatting). Adding specific action verbs would strengthen it.
Suggestions
Replace 'Guidelines for UI text and copy' with concrete actions like 'Provides style rules for writing UI text, crafting error messages, and formatting button labels in WooCommerce projects'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | It names the domain (UI text and copy in WooCommerce) and mentions some specific artifacts (labels, buttons, messages, documentation), but doesn't describe concrete actions like 'write error messages', 'create button labels following style guide', or 'review copy for consistency'. 'Guidelines for' is somewhat vague about what it actually does. | 2 / 3 |
Completeness | Clearly 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 an explicit 'Use when' clause and specific triggers. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'UI text', 'copy', 'WooCommerce', 'labels', 'buttons', 'messages', 'documentation', 'user-facing text'. These cover a good range of terms a user working on WooCommerce UI would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | The combination of 'WooCommerce' with 'UI text and copy' creates a clear, narrow niche. It's unlikely to conflict with general coding skills, general writing skills, or other e-commerce platform skills due to the specific platform and content type scoping. | 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 extremely thin and provides mostly generic writing advice that Claude already knows, with very little WooCommerce-specific actionable guidance. The only concrete, differentiating instruction is the sentence case rule, which is delegated to a referenced file that doesn't exist in the bundle. The skill would benefit greatly from concrete examples of WooCommerce UI copy patterns, before/after comparisons, and specific terminology conventions.
Suggestions
Add concrete before/after examples of WooCommerce UI text (e.g., button labels, error messages, success notifications) showing correct vs incorrect copy patterns.
Replace generic principles ('Use clear, simple language') with WooCommerce-specific conventions, such as preferred terminology (e.g., 'order' vs 'purchase'), tone guidelines, or specific phrasing patterns used in the codebase.
Include the sentence-case.md file in the bundle or inline its key rules, since the reference currently points to a non-existent file.
Add a quick-reference table of common UI elements (buttons, headings, tooltips, error messages) with example copy for each.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The opening line restates the description ('This skill provides guidelines for writing user-facing copy...') which is redundant. The 'Key Principles' section includes generic advice ('Use clear, simple language', 'Keep copy concise and action-oriented') that Claude already knows and doesn't add WooCommerce-specific value. | 2 / 3 |
Actionability | The skill provides only vague, high-level principles ('Keep copy concise and action-oriented', 'Be consistent with existing WooCommerce copy patterns') without concrete examples of good vs bad copy, specific patterns, or any executable guidance. There are no before/after examples of UI text. | 1 / 3 |
Workflow Clarity | For a simple instruction-only skill, the single step ('Follow these guidelines') is clear but the workflow is minimal. The reference to sentence-case.md is a reasonable step, but there's no guidance on how to verify copy meets the standards or what to do when existing patterns conflict. | 2 / 3 |
Progressive Disclosure | The skill references sentence-case.md which is good progressive disclosure, but the bundle has no files, so we can't verify the reference exists. The content that is inline is thin enough that it doesn't need splitting, but the reference to a non-existent bundle file is problematic. | 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
5e92b71
- 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.