copywriting
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
Quality
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 that excels at trigger term coverage and completeness. It clearly defines when to use the skill with natural language triggers and helpfully delineates boundaries with related skills. The main weakness is that the capability description could be more specific about concrete actions beyond 'write, rewrite, or improve.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (marketing copy) and lists page types (homepage, landing pages, pricing pages, etc.), but the actions are somewhat generic ('write, rewrite, or improve') rather than listing specific concrete capabilities like 'craft headlines, optimize CTAs, structure value propositions.' | 2 / 3 |
Completeness | Clearly answers both what (write/rewrite/improve marketing copy for various page types) and when (explicit 'Use when' equivalent with trigger phrases). Also helpfully distinguishes scope by referencing 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.' These are realistic phrases users would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused on marketing page copy with explicit boundaries ('For email copy, see email-sequence. For popup copy, see popup-cro.'). The specific page types and trigger terms make it unlikely to conflict with other skills. | 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 with strong actionability and excellent progressive disclosure. The concrete examples, formulas, and frameworks make it immediately useful. Minor verbosity in explaining writing principles Claude already knows prevents a perfect conciseness score, but overall this is a high-quality skill that balances comprehensiveness with usability.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some content Claude already knows (basic writing principles like 'active over passive', 'simple over complex'). The page-specific guidance and CTA sections could be tightened, though the overall structure respects token budget. | 2 / 3 |
Actionability | Provides highly concrete guidance with specific formulas, examples of good vs bad copy, clear frameworks, and actionable checklists. The before/after examples (Slack copy), CTA formulas, and section-by-section templates are immediately usable. | 3 / 3 |
Workflow Clarity | Clear workflow from context gathering (4 numbered areas) through writing principles to output format. The 'Before Writing' section establishes a logical sequence, and the output format section provides explicit deliverables. For a non-destructive creative task, validation is appropriately handled via the copy-editing skill reference. | 3 / 3 |
Progressive Disclosure | Excellent structure with clear overview sections and well-signaled one-level-deep references to detailed materials (copy-frameworks.md, natural-transitions.md). Related skills section provides clear navigation to adjacent capabilities without nesting. | 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 | |
- Repository
- freekmurze/dotfiles
- Commit
355d067
- 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.