landing-copy
Skill0 starsChanged 4 months agoMITView on GitHub
Write conversion-focused landing page copy using a proven message hierarchy. Use whenever the user asks for landing page copy, a hero section, "headline for my product", website copy that converts, a value proposition, or wants to rewrite a page that "isn't converting". Trigger even when they only describe their product and audience without saying "landing page".
2 other projects use a version of this.
Adopted by
Most recently taken up by
- Mikefluff/skillstheir own version, first seen Aug 8, 2026
- agentdynarq/founder-skillstheir own version, first seen Jul 15, 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
- agentdynarq/founder-skills★ 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 repository8 other files it gives its agents.
- commit-craftSkill
- inbox-triageSkill
- incident-postmortemSkill
- meeting-to-actionsSkill
- newsletter-forgeSkill
- pr-review-guardianSkill
- social-repurposeSkill
- weekly-reviewSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is 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.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
If any is missing, ask — copy written without these is guesswork:
- Very specific: line 52
Never fabricate testimonials or stats — insert [NEEDS REAL DATA] and tell the user what to fill.
≈ “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
Landing copy converts when it moves the reader through one clear line of reasoning: I have this problem → there's a better way → this is that way → I can trust it → here's my one next step. Clever gets remembered; clear gets bought. Choose clear.
Before writing: get three inputs
If any is missing, ask — copy written without these is guesswork:
- Who is the reader (specific role/situation, not "everyone").
- What painful job are they trying to get done.
- What's the mechanism that makes this product work better than their current alternative.
Message hierarchy (write in this order)
- Hook / headline — the outcome or the enemy, in the reader's words. Not the feature. ≤10 words ideal. Test: could a competitor put their name on it? If yes, it's too generic.
- Subhead — one sentence adding the how or the who it's for. Earns the click to keep reading.
- Problem — name the pain sharply enough that the reader thinks "that's me". Specific > dramatic.
- Mechanism — why this works. The unique insight or approach. This is what separates you from "yet another tool".
- Proof — evidence the claim is real: numbers, named outcomes, testimonials, logos, guarantee. Never claim without at least gesturing at proof.
- CTA — one primary action, phrased as the reader's benefit ("Start converting"), not the mechanic ("Submit"). One CTA repeated beats five competing ones.
Output template
### Hero
Headline: <...>
Subhead: <...>
CTA button: <...>
### Problem section
<2-3 lines>
### How it works (mechanism)
<the unique approach; 3 steps or 1 paragraph>
### Proof
<testimonial / stat / guarantee placeholders — mark [NEEDS REAL DATA] where the user must supply>
### Closing CTA
<repeat of primary action + risk reducer, e.g. "No card required">Copy rules
- Second person ("you"), active voice, present tense.
- Concrete nouns and numbers beat adjectives. "Cut invoicing from 3 hours to 10 minutes" > "save tons of time".
- One idea per sentence. Short sentences carry momentum.
- Never fabricate testimonials or stats — insert
[NEEDS REAL DATA]and tell the user what to fill. - Cut every word that survives its own deletion.
Example
Product: scheduling tool for solo therapists. Weak: "The all-in-one platform to manage your practice." Strong headline: "Stop losing an evening a week to scheduling." Subhead: "Booking, reminders, and no-show fees — automatic, for solo therapists."
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
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.

