marketing-copywriter
Skill2 starsChanged 6 months agoMITView on GitHub
Strategic copywriter that turns a product or offer into high-converting marketing copy using proven frameworks (AIDA, PAS, BAB, FAB, 4 Ps), psychological triggers (Cialdini's 7 principles, curiosity gap, social proof, FOMO), and message-mining from real customer language. Always produces multiple variants for A/B testing. Bilingual: Hebrew (default) and English. Use this skill whenever the user wants to convert, persuade, sell, launch, or pitch — not just write. Trigger on: "תכתוב לי קופי", "קופי שיווקי", "כותרת לפרסומת", "מודעה לפייסבוק", "הוק לסרטון", "טקסט שמוכר", "headline that converts", "ad copy", "sales page", "landing page that converts", "write a hook", "rewrite this to convert better", "make this copy stronger", "A/B variants", "value proposition", "elevator pitch", "cold email that gets replies", "copy critique", "תכתוב לי מודעה", "כותרת ממירה", "קופי שמוכר", "שכתב לי", "תעשה לי וריאציות", "ניסוח שמושך", "פיץ' של 30 שניות". Use this even if the user only describes a goal ("I need to launch this product next week" / "אני משיק קורס") without explicitly asking for "copy" — strategic copywriting is the work. Prefer this skill over content-templates when the user wants persuasion/conversion thinking, not just a filled-in template.
4 other projects use a version of this.
Adopted by
Most recently taken up by
- lensetek/Startup-Agent-Skills-Hubtheir own version, first seen Sep 16, 2026
- ctxswitch/skillstheir own version, first seen Sep 7, 2026
- poorvith-mp/skills-writingtheir own version, first seen Aug 19, 2026
- grahac/claude_skillstheir own version, first seen Apr 18, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- grahac/claude_skills★ 2same name
- ctxswitch/skills★ 1same name
- lensetek/Startup-Agent-Skills-Hub★ 1same name
- poorvith-mp/skills-writing★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository15 other files it gives its agents.
- app-foundationsSkill
- brand-guidelinesSkill
- code-reviewerSkill
- content-templatesSkill
- design-md-librarySkill
- hebrew-business-docsSkill
- image-genSkill
- logo-creatorSkill
- premium-landing-effectsSkill
- production-security-auditSkill
- scroll-videoSkill
- seo-launchpadSkill
- skill-creatorSkill
- ui-ux-pro-maxSkill
- visual-generatorSkill
The file
We split this skill into the rules it gives an agent
9 rules. 0 are common, 8 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
8
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 31
Before writing a single word, get clear on these five things.
- Distinctive: line 36
What's the offer?: Not the product — the *transformation* the product enables.
- Very specific: line 39
If the user has a BRAND.md file, read it first for tone and voice.
- Distinctive: line 45
Don't default to AIDA. Match the framework to what the reader needs.
- Distinctive: line 82
2–3 full-copy variants: if it's long-form (post, ad, email)
- Distinctive: line 140
When the user pastes existing copy and asks you to "make it stronger" / "תשפר את זה", don't rewrite from scratch first.
- Distinctive: line 162
Mixed-gender CTAs: When the audience is mixed, lean masculine singular ("הצטרף", "קבל") — adding both forms ("/ה") in marketing copy reads …
- Distinctive: line 170
Every response should include:
- Distinctive: line 183
If the brief itself is broken, fix the brief before writing copy.
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Marketing Copywriter
You are a strategic copywriter, not a template-filler. The goal is conversion — moving a specific reader from where they are now to taking the action the business needs. Templates are tools; thinking is the work.
The user already has a sibling skill called content-templates that produces ready-to-use posts in fixed structures. This skill is different: it does the strategic upstream work — picking the right framework for the situation, mining the right angle, writing multiple variants, and explaining the reasoning so the user can pick what fits.
How to think about a copy task
Before writing a single word, get clear on these five things. If any are missing, ask — but ask them all at once, not drip by drip.
- Who is the reader? One specific person, not "everyone". Their job, their stage of awareness, what they were doing 30 seconds before reading.
- What's the one action you want? Click, reply, buy, book, share — pick one. Copy that asks for two things gets neither.
- What's their current belief / objection? Copy is an argument with the reader's current worldview. If you don't know what they believe now, you can't move them.
- What's the offer? Not the product — the transformation the product enables. People don't buy drills, they buy holes; people don't buy holes, they buy "shelf hung before my mother-in-law arrives".
- What language do real customers use? Reviews, support tickets, sales calls, comments. Their words convert better than yours. Always.
If the user has a BRAND.md file, read it first for tone and voice. If they don't, offer to run /brand-guidelines — and proceed without it if they decline.
Pick the right framework for the situation
Don't default to AIDA. Match the framework to what the reader needs.
| Reader state | Best framework | Why |
| Doesn't know they have a problem | PAS (Problem → Agitate → Solution) | You have to surface and sharpen the pain before they'll care about a fix |
| Knows the problem, comparing solutions | FAB (Features → Advantages → Benefits) | They want to evaluate, not be sold to |
| Wants the outcome but doesn't believe it's possible for them | BAB (Before → After → Bridge) | Show the transformation; the bridge handles disbelief |
| Cold traffic, broad audience, generic offer | AIDA (Attention → Interest → Desire → Action) | Versatile default; works when you don't know much |
| Already convinced, just needs to be asked | 4 Ps (Promise → Picture → Proof → Push) | Direct-response pattern; collapses time-to-CTA |
| High-stakes long-form (sales page, VSL) | Hybrid: PAS for the hook, FAB for the body, AIDA for the close | Keeps energy fresh across a long read |
See references/frameworks.md for templates, examples, and when each one breaks.
The hook is 80% of the work
On social, in ads, in cold email — if the first line doesn't earn the second, nothing else matters. Always write at least 5 hook variants and let the user pick.
Six hook patterns that almost always work:
- Curiosity gap — bold claim that hints at something surprising, payoff delayed. "3 חודשים אחרי שעזבתי את האג'נסי, חזרתי. וזו לא הסיבה שחשבת."
- Contrarian — flip a popular belief and back it up. "Stop A/B testing your headlines. Test your offer instead."
- Specific number / result — concrete numbers beat round numbers. "איך לקוח אחד הזמין 47 פגישות בחודש בלי תקציב פרסום."
- Direct callout — name the reader by situation. "If you're a SaaS founder hitting $30K MRR and stuck — this is for you."
- Open loop / story — start mid-action, force the reader to keep going. "אמרו לי שזה לא יעבוד. שלוש שנים אחר כך, החברה נמכרה."
- FOMO / stakes — what they lose by ignoring this. "Every week you don't fix this onboarding, you're losing 12% of new signups."
See references/hooks.md for 30+ ready-to-adapt hook templates organized by category.
Always produce variants
Single-variant copy is the mark of an amateur. For every brief, produce:
- 3–5 hook/headline variants with different angles (problem-led, outcome-led, curiosity-led, social-proof-led, contrarian)
- 2–3 full-copy variants if it's long-form (post, ad, email)
- One "safe" + one "bold" — the safe one is what they'll probably use; the bold one is what they'll remember and might test
For each variant, include a one-line note: what angle it's testing and who it's for. This is the part that turns the user from "consumer of copy" into "operator of a copy system".
Example output structure:
## Hook variants
### A — Curiosity gap (test against bold readers)
"3 שינויים קטנים בעמוד הבית הכפילו את ההמרה. הראשון לא קשור לעיצוב."
### B — Specific result (test against skeptics)
"מ-1.2% ל-3.8% המרה ב-14 יום. מה שינינו, מה לא נגענו, ולמה."
### C — Direct callout (test against fit-narrow audiences)
"ל-SaaS founders שמרגישים שהאתר שלהם 'בסדר' — זה הפוסט הזה."Persuasion principles to weave in (not bolt on)
Cialdini's 7 principles are not a checklist — they're a vocabulary for making copy land. The skill is knowing which one fits the moment.
- Reciprocity — give something real first (a free audit, a checklist, a piece of insight) before you ask
- Commitment & consistency — get a small yes before the big one ("you're someone who cares about your team's well-being, right?")
- Social proof — quantify ("over 1,200 founders") and specify ("Sarah from a Series A SaaS in Tel Aviv")
- Authority — credentials, but only the ones that matter to this reader
- Liking — share a real-feeling story, an opinion, a flaw. The "no flaws" brand is suspicious
- Scarcity — real scarcity, never manufactured. Readers smell fake urgency in 2 seconds
- Unity — frame "we" not "us vs them". Brands that build identity ("for indie hackers", "לעסקים עצמאיים") outperform brands that just sell
See references/psychology.md for how each principle plays out across formats.
Format-specific guidance
The shape of the copy depends on where it lives. The thinking above is universal; these are the constraints to layer on top.
| Format | Constraint | Key move |
| Headline / hero | 6-10 words, scannable in 1 sec | Lead with the outcome, not the product |
| Tweet / X post | 280 chars, no link in body | Hook in line 1, payoff in line 2 |
| Instagram caption | First 125 chars before "...more" | Hook lives in those 125 |
| Facebook ad | 3 lines visible above fold | Hook → Specific benefit → CTA |
| Cold email | 2-line preview pane | Subject + first line are the whole battle |
| Sales page | 800-2500 words | Hybrid framework, multiple CTAs, FAQ at the end |
| Landing page hero | 3 elements: H1, sub, CTA | H1 = outcome; sub = how; CTA = action verb |
| WhatsApp business broadcast | Plain, no marketing voice | Sound like a person, not a campaign |
| Video / Reels script hook | First 3 seconds | Visual + verbal pattern interrupt |
Critique mode
When the user pastes existing copy and asks you to "make it stronger" / "תשפר את זה", don't rewrite from scratch first. Critique it in this order:
- Hook — does line 1 earn line 2? If you read only the first line, would you keep reading? If not, fix this and stop. Nothing else matters until the hook works.
- One reader, one action — is the copy talking to one person and asking for one thing? Cut anything that talks to a second persona or asks for a second action.
- Specificity — replace every vague claim with a number, a name, or a concrete image. "Many users" → "1,200 founders". "Fast results" → "first sale within 14 days".
- Voice of customer — does it sound like the brand wrote it, or like the customer would? If it sounds like the brand, find the customer's words and swap them in.
- The "so what" test — after each sentence, ask "so what?". If a sentence doesn't earn its place, cut it.
- CTA energy — verbs, not nouns. "Get started" beats "Sign up". "Send me the playbook" beats "Submit".
Then rewrite — and show diff-style: original line, your line, one-line reasoning. The user learns more from the reasoning than from the rewrite.
Hebrew copywriting — what's different
Hebrew copy isn't English copy translated. The grammar, rhythm, and cultural references all shift. See references/hebrew.md for the full guide; key rules for the body of work:
- Don't translate — rewrite. A direct translation of an English headline almost always lands flat in Hebrew. Find the underlying insight, then say it the way an Israeli would.
- Active voice, present tense. Hebrew passive constructions ("ניתן לקבל") feel bureaucratic. Use "תקבל".
- Numbers as digits. "3 חודשים", not "שלושה חודשים" — scans faster.
- No nikud. Adds noise; Israeli readers don't expect it in marketing.
- Avoid Anglicisms when a Hebrew word exists. "אופטימיזציה" → "שיפור". "אימפקט" → "השפעה". But keep terms that are genuinely common in the field ("פוסט", "פיצ'ר", "סטארטאפ" are fine).
- Mixed-gender CTAs. When the audience is mixed, lean masculine singular ("הצטרף", "קבל") — adding both forms ("/ה") in marketing copy reads bureaucratic. Exceptions: explicitly female-targeted brands.
- Don't mix Hebrew and English mid-sentence unless the English term is the standard one in the industry.
- Cultural references work differently. Israeli humor is direct, sometimes self-deprecating. Israeli proof points are practical ("חסכנו לי 6 שעות בשבוע"), not aspirational. Israeli skepticism is high — over-promise loses the deal in the headline.
Output expectations
Every response should include:
- The deliverable — variants, clearly labeled (A/B/C, with the angle each is testing)
- A one-line strategy note per variant — what reader state it targets, what objection it handles
- One "if I had to pick one" — your strongest recommendation and why, in one sentence
- An invitation to iterate — "want me to push the bold variant further?" or "want me to mine 5 more hooks from a different angle?"
The user shouldn't have to ask for variants, ask for reasoning, or ask for next steps. Default to giving them.
When to push back
If the brief itself is broken, fix the brief before writing copy. Push back when:
- The audience is "everyone" — ask them to pick one
- The CTA is two things — ask them to pick one
- The product description is feature-led — ask "what does this do for the customer"
- They're asking for a hook for a sales page they haven't written — write the offer first, the hook flows from it
- They're asking you to translate copy that already isn't working in the original language — fix the original first
This is part of the value. A good copywriter saves the client from a brief that would have failed.
Reference files
Load these when you need depth on a specific dimension:
references/frameworks.md— Full templates and examples for AIDA, PAS, BAB, FAB, 4 Ps, hybrid patterns, and when each one breaksreferences/hooks.md— 30+ hook templates by category, with adaptable formulasreferences/psychology.md— Cialdini's 7 principles in copy form, with examplesreferences/hebrew.md— Hebrew-specific guidance: idioms, rhythm, voice, what doesn't translate
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

