CtrlK
BlogDocsLog inGet started
Tessl Logo

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," "CTA copy," "value proposition," "tagline," "subheadline," "hero section copy," "above the fold," "this copy is weak," "make this more compelling," or "help me describe my product." Use this whenever someone is working on website text that needs to persuade or convert. For email copy, see emails. For popup copy, see popups. For editing existing copy, see copy-editing.

68

Quality

83%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

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 'when' guidance is thorough with many natural user phrases. The main weakness is that the 'what' could be more specific about concrete capabilities beyond 'write, rewrite, or improve' — e.g., mentioning specific deliverables like headline variations, A/B test copy, or conversion-focused frameworks.

Suggestions

Add more specific concrete actions/outputs beyond 'write, rewrite, or improve' — e.g., 'generates headline variations, crafts CTAs, structures value propositions, writes hero section copy, creates A/B test variants.'

DimensionReasoningScore

Specificity

The description names the domain (marketing copy) and mentions several page types (homepage, landing pages, pricing pages, etc.), and actions like 'write, rewrite, or improve,' but doesn't list specific concrete output actions beyond those three verbs. It's more about scope than concrete capabilities.

2 / 3

Completeness

Clearly answers both 'what' (write, rewrite, or improve marketing copy for various page types) and 'when' (extensive explicit trigger phrases and use-case guidance). It also includes helpful boundary-setting with 'For email copy, see emails' and similar cross-references.

3 / 3

Trigger Term Quality

Excellent coverage of natural trigger terms users would actually say: 'write copy for,' 'improve this copy,' 'rewrite this page,' 'headline help,' 'CTA copy,' 'value proposition,' 'tagline,' 'hero section copy,' 'above the fold,' 'this copy is weak,' 'make this more compelling,' and 'help me describe my product.' These are highly natural phrases.

3 / 3

Distinctiveness Conflict Risk

The description explicitly carves out its niche by distinguishing itself from email copy, popup copy, and copy-editing skills. The specific focus on website marketing copy with conversion intent, combined with the cross-references, makes it clearly distinguishable from adjacent skills.

3 / 3

Total

11

/

12

Passed

Implementation

77%

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, highly actionable copywriting skill with clear workflow sequencing and good concrete examples (headline formulas, CTA comparisons, page structure tables). Its main weakness is moderate verbosity — it explains some concepts Claude already knows well (basic writing principles, active vs passive voice) and could be more concise by moving detailed guidance into reference files. The references to external files suggest good progressive disclosure intent, but without bundle files to verify, the actual disclosure structure can't be fully validated.

Suggestions

Trim or remove the 'Writing Style Rules' and 'Copywriting Principles' sections — Claude already knows these fundamentals. Keep only project-specific style constraints or reduce to a brief checklist.

Move page-specific guidance and detailed CTA examples into a reference file (e.g., references/copy-frameworks.md) to reduce the main skill's token footprint while preserving the information.

DimensionReasoningScore

Conciseness

The skill is generally well-structured but includes some unnecessary explanation that Claude already knows (e.g., 'Features: What it does. Benefits: What that means for the customer,' basic writing style rules like active vs passive voice). Some sections like 'Writing Style Rules' and 'Best Practices' cover ground Claude is already expert in. However, the page-specific guidance and CTA formulas add genuine value.

2 / 3

Actionability

The skill provides highly concrete, actionable guidance: specific headline formulas, CTA examples with good/bad comparisons, a clear page structure framework with section purposes, and a defined output format. The before-writing checklist and page-specific guidance give Claude exact steps to follow.

3 / 3

Workflow Clarity

The workflow is clearly sequenced: gather context first (with specific questions organized by category), apply principles, follow page structure framework, then output in a defined format with annotations and alternatives. The cross-reference to copy-editing for post-draft review creates a natural validation checkpoint. For a non-destructive creative task, this level of workflow clarity is appropriate.

3 / 3

Progressive Disclosure

The skill references two external files (references/copy-frameworks.md and references/natural-transitions.md) which is good progressive disclosure design, but no bundle files were provided to verify these exist. The main SKILL.md itself is quite long (~200 lines) and some content like the detailed page-specific guidance or the full writing style rules could potentially be split into reference files to keep the main skill leaner.

2 / 3

Total

10

/

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.

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository
coreyhaines31/marketingskills
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.