- Home
- Skills
- Pedrosantiagodev
- Buildup
- Copywriting
copywriting_skill
- Java
0
GitHub Stars
1
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill pedrosantiagodev/buildup --skill copywriting- skill.md7.4 KB
Overview
This skill teaches marketing and sales copywriting that converts by focusing on benefits, concrete outcomes, and emotional clarity. It shows how to lead with reader pain, make the reader feel smart, and turn features into compelling results. Use the skill to write landing pages, product descriptions, emails, and headlines that actually move people to act.
How this skill works
It inspects copy for weak features-first language, vagueness, and jargon, then rewrites lines to surface specific benefits and measurable outcomes. It applies formulas like Before-After-Bridge, Pain-Agitate-Solution, and Feature-Advantage-Benefit to restructure messaging. It also tests headlines against the 4 U's and runs clarity and “so what?” checks to keep copy scannable and persuasive.
When to use it
- Writing landing page headlines and hero sections
- Converting feature lists into benefit-driven product descriptions
- Drafting marketing or sales emails and subject lines
- A/B testing copy variants for clarity and impact
- Improving CTAs and short-form ad copy
Best practices
- Always ask “so what?” until you reach a clear outcome or emotion
- Start with the reader’s pain, not your product
- Use concrete numbers and timeframes whenever possible
- Keep sentences short and conversational—write like you’d speak to a friend
- Make the reader feel smart by explaining value simply, not showing off jargon
- Run quick clarity tests: read aloud, scroll test, friend test
Example use cases
- Landing page hero: turn “cloud backup” into “Recover files in minutes, not days”
- Product description: replace specs with outcomes like “Work all day without charging”
- Email subject line: use urgency and specificity — “Ship fixes in 24 hours, not 3 days”
- Feature list rewrite: transform bullets into direct benefits and next steps
- Headline rewrite: apply 4 U’s to make a short, compelling promise
FAQ
Ask “so what?” repeatedly. Translate what the feature does into a concrete user outcome or emotion (time saved, pain avoided, control regained).
When should I use a headline template vs. writing fresh?
Use a template when you need speed or a proven structure; customize it with specific numbers, timeframes, or contrasts to keep it fresh and relevant.
What’s the fastest clarity check?
Read the copy out loud and do the scroll test: can someone grasp the offer in three seconds? If not, lead with the benefit or pain.