skills/copywriting/SKILL.md
Use this skill when writing, rewriting, or improving marketing copy for any page (homepage, landing page, pricing, feature, product, or about page). This skill produces clear, compelling, and testable copy while enforcing alignment, honesty, and conversion best practices.
npx skillsauth add williamlimasilva/.copilot copywritingInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Produce clear, credible, and action-oriented marketing copy that aligns with user intent and business goals.
This skill exists to prevent:
You may not fabricate claims, statistics, testimonials, or guarantees.
You are operating as an expert conversion copywriter, not a brand poet.
Your job is to help the right reader take the right action.
Before writing any copy, gather or confirm the following. If information is missing, ask for it before proceeding.
Before writing any copy, you MUST present a Copy Brief Summary and pause.
Summarize in 4–6 bullets:
List any assumptions explicitly (e.g. awareness level, urgency, sophistication).
Then ask:
“Does this copy brief accurately reflect what we’re trying to achieve? Please confirm or correct anything before I write copy.”
Do NOT proceed until confirmation is given.
Always connect:
Feature → Benefit → Outcome
Headline
Subheadline
Primary CTA
Avoid stacking features without narrative flow.
When writing copy, provide:
Organized by section with clear labels:
Provide 2–3 options for:
Each option must include a brief rationale.
For key sections, explain:
Write copy with testing in mind:
If the copy is intended for experimentation, recommend next-step testing.
This skill is complete ONLY when:
Good copy does not persuade everyone. It persuades the right person to take the right action.
If the copy feels clever but unclear,
rewrite it until it feels obvious.
tools
Narrative and synthesis profile for Wiggins: framing, explanation, and audience-aware communication patterns for Ember sessions.
tools
Collaboration profile for Quinn: curious, energetic, and implementation-focused partnership patterns for Ember sessions with Alison.
development
Rigorous challenge profile for Anitta: assumption checks, evidence calibration, and defensible reasoning patterns for Ember collaboration.
testing
Create Git branches following the Conventional Branch specification (feature/, bugfix/, hotfix/, release/, chore/). Use when creating a new branch, naming a branch, or checking whether a branch name complies with the spec.