When the user wants to write, rewrite, or improve marketing copy for any page — including homepage, landing pages, pricing pages, feature pages, about pages, or product pages. Also use when the user says "write copy for," "improve this copy," "rewrite this page," "marketing copy," "headline help," or "CTA copy." For email copy, see email-sequence. For popup copy, see popup-cro.
89
87%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
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 strong skill description with excellent trigger term coverage and clear disambiguation from related skills. The explicit 'Use when' triggers and cross-references to adjacent skills make it highly functional for skill selection. The main weakness is that the core capabilities could be more specific — listing concrete deliverables beyond 'write, rewrite, or improve' would strengthen it further.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (marketing copy) and lists page types (homepage, landing pages, pricing pages, etc.), but the actual actions are somewhat generic — 'write, rewrite, or improve' — without listing more concrete deliverables like 'craft headlines, write CTAs, structure value propositions.' | 2 / 3 |
Completeness | Clearly answers both 'what' (write, rewrite, or improve marketing copy for various page types) and 'when' (explicit trigger phrases and use-case guidance). It also includes helpful boundary-setting by pointing to related skills for email and popup copy. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'write copy for,' 'improve this copy,' 'rewrite this page,' 'marketing copy,' 'headline help,' 'CTA copy,' plus specific page types like 'homepage,' 'landing pages,' 'pricing pages.' These are highly natural phrases. | 3 / 3 |
Distinctiveness Conflict Risk | The description carves out a clear niche (page-level marketing copy) and explicitly disambiguates from related skills (email-sequence for email copy, popup-cro for popup copy), significantly reducing conflict risk. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured copywriting skill that provides actionable frameworks, concrete examples, and clear workflow guidance. Its main weakness is some verbosity in explaining writing principles that Claude already knows (clarity over cleverness, active voice, etc.), which could be trimmed to save tokens. The progressive disclosure is excellent with appropriate references to supplementary files, and the output format specification ensures consistent deliverables.
Suggestions
Trim the 'Copywriting Principles' and 'Writing Style Rules' sections significantly — Claude already knows to prefer active voice, simple words, and specificity. Keep only the domain-specific guidance like the before/after Slack example and the 'no exclamation points' rule.
Consider condensing the 'Best Practices' section; advice like 'be direct' and 'use analogies' is general writing knowledge that doesn't need explicit instruction for Claude.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably well-organized but includes some content Claude already knows (e.g., explaining what benefits vs features means, basic writing principles like 'active over passive'). The copywriting principles section and writing style rules contain guidance that an expert LLM would already internalize. However, the page-specific guidance and CTA formulas add genuine value. | 2 / 3 |
Actionability | The skill provides concrete headline formulas, specific CTA examples (weak vs strong), a clear page structure framework with a table of sections, and explicit before/after examples (e.g., the Slack copy rewrite). The output format section specifies exactly what deliverables to produce. The guidance is specific enough to be directly applied. | 3 / 3 |
Workflow Clarity | The workflow is clearly sequenced: check for existing context → gather missing information (with specific questions) → apply principles → write using page structure framework → output in specified format → use copy-editing skill for polish. For a non-destructive creative task, this is a well-defined process with appropriate checkpoints (context gathering before writing, quality check after). | 3 / 3 |
Progressive Disclosure | The skill provides a clear overview with well-signaled one-level-deep references to 'references/copy-frameworks.md' for detailed headline formulas and page templates, and 'references/natural-transitions.md' for transition phrases. Related skills are clearly listed at the end with brief descriptions of when to use each. Content is appropriately split between the main file and reference materials. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
2c6f6e8
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.