landing-page-copywriter
Skill4 starsChanged 4 months agoMITView on GitHub
Writes full landing-page copy under AIDA discipline — hero with 3 headline variants, problem, proof, offer, objection handling, and one CTA repeated down the page; conversion-focused, never clever-for-clever's-sake. Use when the user asks to "write landing page copy", "sales page", "homepage copy", "hero headline", or "copy for my offer page". Don't use for ranking-oriented blog articles — that's seo-blog-writer.
7 other projects use a version of this.
Adopted by
Most recently taken up by
- imtiazrayhan/agentscamp-librarytheir own version, first seen Nov 16, 2026
- theexperiencecompany/gaiatheir own version, first seen Nov 13, 2026
- julianromli/ai-skillstheir own version, first seen Oct 25, 2026
- OneWave-AI/onewave-toolkittheir own version, first seen Oct 2, 2026
- OneWave-AI/claude-skillstheir own version, first seen Sep 21, 2026
- whyashthakker/agent-skills-marketingtheir own version, first seen Jun 21, 2026
Used with
Projects with it also use seo-geo.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
ReScienceLabSkillseo-geo
SEO & GEO (Generative Engine Optimization) for websites. Analyze keywords, generate schema markup, optimize for AI search engines (ChatGPT, Perplexity, Gemini, Copilot, Claude) and traditional search (Google, Bing). Use when user wants to improve search visibility.
Also in 3 projects that use this
Other versions7 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 7
- OneWave-AI/claude-skills★ 378same name
- theexperiencecompany/gaia★ 327same name
- julianromli/ai-skills★ 222same name
- whyashthakker/agent-skills-marketing★ 15same name
- imtiazrayhan/agentscamp-library★ 1same name
- itsyasirkhandev/spec-driven-development★ 1same name
- OneWave-AI/onewave-toolkit★ 1same 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 repository74 other files it gives its agents.
- agent-eval-harnessSkill
- context-budget-managerSkill
- incident-rollbackSkill
- memory-hygieneSkill
- model-cost-optimizerSkill
- prompt-debuggerSkill
- skill-author-coachSkill
- third-party-skill-vetterSkill
- api-endpoint-testerSkill
- bug-triage-protocolSkill
- changelog-release-notesSkill
- docs-readme-writerSkill
- env-secrets-hygieneSkill
- github-pr-reviewSkill
- git-ship-flowSkill
- lovable-brief-writerSkill
- supabase-migration-writerSkill
- vercel-deploy-checkSkill
- cold-outreach-sequencerSkill
- competitor-pricing-scanSkill
- contract-redline-scanSkill
- customer-support-inboxSkill
- invoice-runnerSkill
- kpi-dashboard-weeklySkill
- lead-research-dossierSkill
- payment-reconciliationSkill
- pipeline-trackerSkill
- proposal-builderSkill
- stripe-payment-linkSkill
- testimonial-harvesterSkill
- weekly-revenue-reportSkill
- brand-voice-guardianSkill
- case-study-builderSkill
- content-repurposerSkill
- deep-research-briefSkill
- email-nurture-sequenceSkill
- linkedin-content-packSkill
- newsletter-assemblerSkill
- seo-blog-writerSkill
- social-listening-reportSkill
- x-thread-builderSkill
- youtube-script-writerSkill
- budget-guardrailsSkill
- ceo-operating-doctrineSkill
- delegation-protocolSkill
- editor-personaSkill
- heartbeat-standupSkill
- hiring-briefSkill
- ops-agent-personaSkill
- researcher-personaSkill
- sales-agent-personaSkill
- support-agent-personaSkill
- weekly-retroSkill
- writer-personaSkill
- calendar-conciergeSkill
- decision-journalSkill
- email-triageSkill
- file-organizerSkill
- habit-trackerSkill
- inbox-zero-sprintSkill
- The first 60 shown.
The file
Files
Landing Page Copywriter
Produces a complete page of copy where every section moves one visitor toward one action. AIDA runs the structure (Attention → Interest → Desire → Action), proof outweighs adjectives, objections get answered before they're asked, and the same single CTA repeats until it's the obvious next step. Clever that doesn't convert gets cut.
When to Use
- The user needs copy for a landing page, sales page, waitlist page, or homepage with one primary action.
- Existing page copy converts poorly and needs a rewrite against AIDA.
- The user asks for "headline options", "hero copy", or "objection handling section".
- Not for: SEO blog articles (
seo-blog-writer), email sequences that warm people up before the page (email-nurture-sequence), or sourcing the customer proof itself (case-study-builderproduces it; this skill deploys it).
Quick Reference
| Action | Rule |
| One page, one CTA | A single action, repeated 3–5× verbatim; secondary links only in footer |
| Hero headline | 3 variants: outcome-led, pain-led, proof-led — each ≤12 words |
| Proof | Real numbers, named customers, or quotes only; no proof available → say so, never invent |
| Objections | List top 3–5 real objections; each answered in copy, not dodged |
| Clever test | If a line needs a beat to "get it", replace with the clear version |
| Reading level | Hero and CTA readable in one pass; no jargon the visitor didn't bring |
Procedure
- Gather — confirm before writing: the offer (what, price/commitment), the one action (buy/book/join), the audience and their current alternative, 3–5 real objections (ask "why do interested people not buy?"), and available proof (numbers, quotes, logos, case studies). Proof missing → mark
[PROOF NEEDED]slots; never fabricate testimonials or stats. - Write the hero (Attention) — 3 headline variants: (a) outcome-led ("Ship your product in 30 days"), (b) pain-led (names the frustration), (c) proof-led (leads with the number). Each ≤12 words, each paired with one subhead that adds the mechanism, plus the CTA button text (2–4 words, verb-first). Recommend one variant and say why.
- Problem section (Interest) — describe the visitor's situation in their words (from step 1 inputs), sharp enough that they think "that's me". No product mention yet; agitate honestly, don't catastrophize.
- Proof + offer (Desire) — introduce the offer as the turn: what it is, how it works in 3 steps, then stack proof — strongest first. Real quotes verbatim with names/roles; numbers with context. Every
[PROOF NEEDED]slot lists exactly what asset would fill it. - Objections — one short block per objection from step 1 (FAQ format or inline). Answer directly; where the honest answer is "this isn't for you if X", write that — it strengthens everything else.
- Action — closing CTA section: restate outcome, the CTA verbatim, and one risk-reversal line if it truly exists (guarantee, free tier, cancel-anytime). CTA text identical everywhere on the page — count occurrences.
- Clever audit + deliver — reread every line: any pun, wordplay, or vague-but-pretty phrase that a distracted visitor wouldn't instantly parse gets replaced with the plain version. Assemble the Output Template.
Output Template
# Landing Page Copy: [Offer]
**One action:** [CTA text, verbatim] | **Audience:** [who] | **Recommended headline:** [a/b/c + why]
## Hero
H1 variants: A) [outcome] B) [pain] C) [proof]
Subhead: ... | CTA button: [text]
## Problem
[2–4 short paragraphs in the visitor's words]
## How it works
1) ... 2) ... 3) ...
## Proof
[quotes verbatim + numbers with context, or [PROOF NEEDED: asset]]
## Objections
**"[objection]"** — [direct answer] (×3–5)
## Final CTA
[outcome restated] → [CTA text] | Risk reversal: [line or omit]Pitfalls
- Clever headline, unclear offer — the hero wins applause and the visitor can't say what's sold. Recovery: apply the "stranger test" — could someone state the offer after reading only H1+subhead? No → outcome-led variant becomes the recommendation.
- Invented social proof — a plausible testimonial appears because the section felt empty. Recovery: strip anything the user didn't supply; ship
[PROOF NEEDED]slots with a list of the exact assets to collect — an honest gap beats a fake quote. - CTA drift — "Get started", "Try it free", and "Join now" all on one page. Recovery: pick one phrasing in step 1 and search-replace; every button reads identically.
- Objections dodged — the price objection gets a vibe ("incredible value") instead of an answer. Recovery: rewrite each objection block to pass "would a skeptic feel answered?"; anchor price against the alternative's cost or admit the fit boundary.
- Feature-dump Desire section — a spec list where the payoff should be. Recovery: rewrite each feature as "so you can [outcome]"; any feature without a "so you can" gets demoted or cut.
Verification
- Exactly one CTA phrasing; appears 3–5×, verbatim (counted)
- 3 hero variants present (outcome / pain / proof), each ≤12 words, one recommended with rationale
- Every proof element is user-supplied or an explicit
[PROOF NEEDED]slot — zero invented quotes/stats - Each objection from step 1 has a direct answer in the copy
- AIDA order intact: attention → interest → desire → action, no section out of role
- Clever audit done: no line requires a second read to parse
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.

