CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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," "hero section copy," "this copy is weak," "this sounds like AI," "AI slop," "make it sound human," or "help me describe my product." Drafts never use AI tells like "it's not X, it's Y" reveals, "no X, no Y, no Z" lists, or sentences that trail into extra comma clauses. For email copy, see emails. For popup copy, see popups. For editing existing copy, see copy-editing. For the offer underneath the copy (bonuses, guarantees, value framing), see offers. Claims must be supportable, and a declined claim names the evidence that would unlock it. Diagnoses the input first (blank brief, real voice, or point edit) and changes only what it calls for.

Quality

95%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

92%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body delivers a coherent, highly actionable copywriting workflow with validation checkpoints and a well-structured reference bundle, and it correctly treats AI-tells and framework detail as progressively disclosed material. Its only weakness is a handful of generic advice sections (analogies, humor, voice/tone checklists) that could be trimmed for token efficiency.

DimensionReasoningScore

Conciseness

Most sections are tight and skill-specific (diagnosis table, three-question gate, AI-tell rules with rewrites, claims protocol), but a few sections restate copywriting knowledge Claude already has — "Use Analogies When Helpful", "Pepper in Humor (When Appropriate)", and the "Voice and Tone" formality/boldness checklists — which is minor over-explanation fitting anchor 4 rather than the every-token-earns-its-place level of anchor 5.

4 / 5

Actionability

For an instruction-only skill the guidance is fully executable: the A/B/C situation table with per-situation jobs, the three-question gate with explicit pass thresholds, banned patterns with named rewrites, CTA formula "[Action Verb] + [What They Get] + [Qualifier if needed]", ❌/✅ Slack example, and a [NEED: ...] flagging convention with a defined output format — specific examples cover the common cases.

5 / 5

Workflow Clarity

The multi-step process is clearly sequenced (read product-marketing context file → gather context → state diagnosis "in one line with the evidence" → decompose and lock units → three-question gate → leave-it-alone test → deliver) with explicit validation checkpoints ("Three passes, keep it. Two, sharpen the weak one. One or none, rewrite it") and feedback loops (revert changes you can't justify; flag missing proof rather than inventing it).

5 / 5

Progressive Disclosure

The body is a well-organized overview with three real, clearly signaled, one-level-deep references (ai-tells.md, copy-frameworks.md, natural-transitions.md); anchor links resolve to actual sections ("The Self-Check", "Build a Writer", "Clarity & Message-Market Fit"), and bulk detail (full blacklist, headline formula catalog, templates) is appropriately split into the bundle with concise summaries retained inline.

5 / 5

Total

19

/

20

Passed

Description

95%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is dense with explicit triggers, boundary redirects, and behavioral constraints, answering both what and when with no padding despite its length. Third-person voice is used throughout and no buzzwords or over-claims appear.

DimensionReasoningScore

Specificity

Names concrete actions ("write, rewrite, or improve marketing copy") plus specific behaviors ("Drafts never use AI tells", "a declined claim names the evidence that would unlock it", "Diagnoses the input first") in third person, but the distinct operation set is a single family — produce/improve page copy — leaving minor coverage gaps versus the multi-action comprehensiveness of anchor 5.

4 / 5

Completeness

Explicitly answers both questions: what ("write, rewrite, or improve marketing copy for any page", with behavioral constraints) and when ("When the user wants to... Also use when the user says..." followed by fourteen concrete trigger phrases), which matches the anchor-5 example structure exactly.

5 / 5

Trigger Term Quality

Comprehensive natural trigger phrases users would actually say — "write copy for", "headline help", "CTA copy", "this sounds like AI", "AI slop", "make it sound human", "help me describe my product" — plus an enumeration of page types, matching the anchor-5 level of synonym coverage (file extensions are not applicable to this domain).

5 / 5

Distinctiveness Conflict Risk

Clear niche (page marketing copy) with explicit disambiguation redirects — "For email copy, see emails. For popup copy, see popups. For editing existing copy, see copy-editing. For the offer underneath the copy... see offers" — which actively minimizes conflict with adjacent skills rather than just being distinct.

5 / 5

Total

19

/

20

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

coreyhaines31/marketingskills

Path

skills/copywriting/SKILL.md

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.