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.
Install with Tessl CLI
npx tessl i github:coreyhaines31/marketingskills --skill copywritingOverall
score
90%
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillEvaluation — 92%
↑ 1.10xAgent success when using this skill
Validation for skill structure
Discovery
90%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 scope boundaries. The explicit disambiguation ('For email copy, see email-sequence. For popup copy, see popup-cro.') is particularly valuable for skill selection. The main weakness is that the capability description could be more specific about concrete actions beyond generic '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 multiple specific concrete actions 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 includes helpful disambiguation 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. These are phrases users would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused on marketing page copy with explicit boundaries. The cross-references to email-sequence and popup-cro skills actively reduce conflict risk by clarifying scope boundaries. | 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, actionable skill that provides concrete copywriting guidance with clear workflows and good progressive disclosure. The main weakness is some verbosity around principles Claude already understands (basic writing rules), though the specific examples and frameworks add genuine value. The output format section and related skills navigation are particularly strong.
Suggestions
Trim the 'Writing Style Rules' section - Claude knows basic writing principles like 'active over passive' and 'simple over complex'; focus only on domain-specific copywriting guidance
Consider moving the detailed 'Page-Specific Guidance' section to a reference file, keeping only brief pointers in the main skill
| 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 tables give Claude exactly what to do. | 3 / 3 |
Workflow Clarity | Clear sequence: gather context first (with specific questions), apply principles, follow page structure framework, then output in specified format. The 'Before Writing' section establishes a proper workflow with context-checking steps. | 3 / 3 |
Progressive Disclosure | Excellent structure with clear overview sections and well-signaled one-level-deep references to 'references/copy-frameworks.md' and 'references/natural-transitions.md'. Related skills section provides clear navigation to adjacent capabilities. | 3 / 3 |
Total | 11 / 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.
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.