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
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 boundary-setting via cross-references to related skills. The main weakness is that the 'what' portion could be more specific about concrete actions beyond 'write, rewrite, or improve' — for example, mentioning headline generation, value proposition crafting, or CTA optimization. Overall, it would perform well in a multi-skill selection scenario.
Suggestions
Add more specific concrete actions to the capability list, e.g., 'Crafts headlines, writes value propositions, optimizes CTAs, structures page sections' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (marketing copy) and lists page types (homepage, landing pages, pricing pages, etc.), but doesn't list specific concrete actions beyond 'write, rewrite, or improve.' It lacks detail on what specific outputs or techniques are involved (e.g., headline generation, CTA optimization, A/B variants). | 2 / 3 |
Completeness | Clearly answers both 'what' (write, rewrite, or improve marketing copy for various page types) and 'when' (explicit 'Use when' triggers and specific phrases). Also includes helpful boundary-setting 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,' plus specific page types like 'homepage,' 'landing pages,' 'pricing pages,' 'feature pages,' 'about pages,' 'product pages.' | 3 / 3 |
Distinctiveness Conflict Risk | The description carves out a clear niche (page-level marketing copy) and explicitly delineates boundaries with 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 with strong actionability, clear workflow, and good progressive disclosure. Its main weakness is moderate verbosity — some sections explain concepts Claude already knows (benefits vs features, active vs passive voice, simple vs complex language). The concrete examples, CTA formulas, page structure framework, and output format requirements are genuinely valuable additions.
Suggestions
Trim the 'Writing Style Rules' and 'Copywriting Principles' sections significantly — Claude already knows these writing fundamentals. Keep only the project-specific constraints like 'no exclamation points' and 'never fabricate statistics.'
Condense the 'Best Practices' section; the Slack example is useful but the explanations of rhetorical questions and analogies are concepts Claude already understands well.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably well-structured 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, before/after copy examples (e.g., the Slack example), and explicit output format requirements. The guidance is specific enough to be directly applied. | 3 / 3 |
Workflow Clarity | The workflow is clearly sequenced: gather context first (with a checklist of questions), apply principles, follow page structure framework, then output in a specific format with annotations and alternatives. The 'Before Writing' section establishes a clear starting point including checking for existing context files. For a non-destructive creative task, this level of workflow clarity is appropriate. | 3 / 3 |
Progressive Disclosure | The skill provides a clear overview with well-signaled one-level-deep references to 'references/copy-frameworks.md' and 'references/natural-transitions.md' for detailed content. 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 | |
- Repository
- freekmurze/dotfiles
- Commit
05d40bb
- 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.