landing-copy
Skill0 starsChanged 4 months agoMITView on GitHub
Write conversion-focused landing page copy with a clear hero, objection-mapped sections, and a single call to action. Use when the user wants landing page copy, a homepage rewrite, hero text, or asks why their page is not converting.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- Mikefluff/skillstheir own version, first seen Aug 8, 2026
- moses607/skillforgetheir own version, first seen Jul 14, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- Mikefluff/skills★ 26same name
- moses607/skillforge★ 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 repository10 other files it gives its agents.
- cold-outreachSkill
- competitor-scanSkill
- customer-discoverySkill
- hiring-kitSkill
- investor-updateSkill
- launch-planSkill
- metrics-reviewSkill
- mvp-cutSkill
- pitch-deck-reviewSkill
- pricing-strategySkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 39
Write like one person explaining to another.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Landing Copy
A landing page has one job: get a specific visitor to take one action. This skill writes the words; layout and code are separate concerns.
Before writing
Get from the user:
- Who lands here and where from (an ad? a tweet? a cold email?)
- The one action the page exists for (signup, demo booking, download, waitlist)
- The top 3 reasons a fitting visitor says no (price, trust, effort, "we already have X")
- Real proof available: customer names, numbers, quotes, screenshots
The page, section by section
Hero. Three parts:
- Headline: the outcome the visitor gets, in their words, under 10 words. Not the category ("AI-powered platform") and not cleverness that needs decoding.
- Subheadline: one sentence on what it is, who it is for, and the mechanism.
- CTA button: verb plus outcome ("Start polling free"), with a friction-killer line under it ("Free, no signup").
The bar: a stranger knows what it is, who it is for, and what to do within 5 seconds.
Proof strip. Logos, a usage number, or one strong quote, immediately after the hero. If pre-launch with zero proof, skip it; never fabricate or pad with "as seen on" fluff.
Problem/solution block. Name the current painful way in the visitor's vocabulary, then show (screenshot beats paragraph) how the product replaces it.
Objection sections. One section per objection from the intake list, in descending order of importance. Each: a header that states the worry's resolution, 2-3 sentences or bullets of evidence.
Final CTA. Same action as the hero, one line restating the core outcome. One page, one action: navbars full of links and competing CTAs leak conversions.
Voice rules
- Write like one person explaining to another. Read every line aloud; if you would not say it, cut it.
- Verbs and nouns over adjectives. "Cutting-edge," "seamless," "revolutionize," "supercharge," and "unlock" are banned.
- Specific numbers beat superlatives: "loads in 200ms" beats "blazing fast."
- "You" appears more often than the product name.
Output format
Deliver as an annotated wireframe: each section labeled, copy in full, with a one-line note on intent (which objection it handles). Offer 3 headline options with different angles: outcome, enemy (the old way), and speed/ease.
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.