landing-page
Skill796 starsChanged 40 days agoMITView on GitHub
Write landing page copy section by section, from hero to final call to action, including FAQ and SEO metadata. Use when a founder needs copy for a new or existing landing page.
47 other projects use a version of this.
Adopted by
Most recently taken up by
- vaferkhanom/Website-skillstheir own version, first seen Nov 16, 2026
- teodstr/garagetheir own version, first seen Nov 15, 2026
- igoroliveirg/claude-copytheir own version, first seen Nov 15, 2026
- tandryukha/aidemotheir own version, first seen Nov 9, 2026
- ImBIOS/skillstheir own version, first seen Nov 8, 2026
- ainurdev/mystical-assistanttheir own version, first seen Nov 8, 2026
Used with
Projects with it also use operational-enterprise-ai, product-proof-saas and 9 more.
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.
boraoztuncSkilloperational-enterprise-ai
Create or redesign enterprise AI, automation, security, and operations product pages that explain system boundaries, approvals, auditability, exceptions, and rollback. Use for dark cinematic heroes, hairline grids, metric pauses, expandable solution rows, case-study evidence, security proof, and qualified demo or waitlist handoffs.
Also in 3 projects that use this
boraoztuncSkillproduct-proof-saas
Create or redesign SaaS and AI product landing pages where a real workflow, interface, or deterministic demo is the central proof. Use for pale atmospheric shells, product UI in the hero, prompt-to-output stories, audience tabs, compact feature modules, honest pricing comparisons, and FAQ handoffs.
Also in 3 projects that use this
Dragoon0xSkillpricing-page
Present pricing in ways that reduce friction and increase clarity. Handles tier naming, feature comparison, anchor pricing, and plan selection psychology. Use when designing pricing pages, plan selectors, or upgrade prompts.
Also in 3 projects that use this
Dragoon0xSkillonboarding-flow
Design first-run experiences that create the aha moment fast. Reduces time-to-value by sequencing actions, progressive disclosure, and contextual guidance. Use when building signup flows, product tours, or empty states.
Also in 3 projects that use this
shawnpangSkilllead-scoring
When a founder needs to qualify inbound leads, define their ICP, build a lead scoring model, set MQL criteria, or route prospects through pipeline stages. Activate when the user mentions lead scoring, ICP, MQL, SQL, lead qualification, inbound leads, or pipeline design.
Also in 3 projects that use this
claude-office-skillsSkillemail-marketing
Email marketing automation - campaign creation, sequence building, A/B testing, deliverability optimization, and analytics
Also in 4 projects that use this
- +2 more from boraoztunc
Other versions47 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 47
- boraoztunc/skills★ 473same name
- shawnpang/startup-founder-skills★ 331same name
- whawkinsiv/solo-founder-skills★ 260same name
- whawkinsiv/claude-code-skills★ 258same name
- realjaymes/marketingagentskills★ 68same name
- duncan-buildroom/freeskills★ 65same name
- KeWang0622/agent-zero-to-hero★ 55same name
- tandryukha/aidemo★ 32same name
- ariaxhan/kernel-claude★ 15same name
- calven-ai/marketing-as-code★ 10same name
37 more not listed
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 repository13 other files it gives its agents.
- competitor-matrixSkill
- email-sequenceSkill
- fundraise-prepSkill
- go-to-marketSkill
- metrics-dashboardSkill
- mvp-scopeSkill
- persona-genSkill
- pitch-deckSkill
- pricing-strategySkill
- product-briefSkill
- statusSkill
- user-interviewsSkill
- validate-ideaSkill
The file
We split this skill into the rules it gives an agent
9 rules. 0 are common, 6 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 42 edited versions we read keep these.
6
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 14
Read ${CLAUDE_PLUGIN_ROOT}/shared/conventions.md and follow it.
- Very specific: line 20
Use the persona's own words from founder/persona-gen.md or founder/user-interviews.md in the problem section when they exist.
- Very specific: line 58
Write 2 testimonial slots as placeholders that say what a strong quote would cover, for example [Quote from an ops manager: hours saved per …
- Distinctive: line 62
If pricing is simple, show it
- Distinctive: line 63
If it's complex, show "Starting at $X/month" with a link to full pricing
- Distinctive: line 87
Write for the reader: "you" before "we", "we" before "our product".
- Distinctive: line 88
Every headline must work if the reader sees nothing else on the page.
- Distinctive: line 89
No jargon unless the audience uses it daily.
- Distinctive: line 92
Keep total output under 1500 words.
“Common” is measured: kept by at least 6 in 10 of the 42 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
You are a conversion copywriter. You write copy a stranger understands in 5 seconds, not copy that sounds clever.
Input: $ARGUMENTS
Before you start
Read ${CLAUDE_PLUGIN_ROOT}/shared/conventions.md and follow it.
- Reads:
founder/facts.md,founder/product-brief.md,founder/persona-gen.md,founder/pricing-strategy.md,founder/competitor-matrix.md - Needs: the product, who it's for, and what it does for them
- Saves to:
founder/landing-page.md
Use the persona's own words from founder/persona-gen.md or founder/user-interviews.md in the problem section when they exist.
Instructions
1. Hero
- Headline (6-12 words): a clear outcome, not wordplay. A stranger should understand what this does.
- Subheadline (15-25 words): who it's for and how it works.
- Button text: not "Get started" or "Sign up". Describe the value ("Start analyzing competitors", "Generate your first brief").
- Proof line: one line under the button. Use a real number from
founder/facts.mdor the input. If there isn't one, write a placeholder such as[Waitlist count].
2. Problem
- Headline: the pain in the customer's words
- 3 pain points, 1-2 sentences each, written as the reader would say them
- Bold the key phrase in each pain point
3. Solution
- Headline: the bridge from problem to product
- 3 benefit blocks, each with:
- a short title (3-5 words)
- 2-3 sentences about the outcome, not the feature
- one concrete detail: a number, a timeframe, or a comparison
4. How it works
- 3-4 steps from signup to value
- Each step: number, title, one sentence
- The whole flow should feel doable in under 5 minutes
5. Social proof
Recommend the type of proof that fits the stage:
- Pre-launch: waitlist count, advisor quotes, the team's track record
- Early stage: beta user quotes, results from the first users
- Growing: logo bar, case studies, specific numbers
Write 2 testimonial slots as placeholders that say what a strong quote would cover, for example [Quote from an ops manager: hours saved per week, and what they did before]. Never write the quote itself. Invented testimonials are false advertising, and in the US the FTC's rules on fake reviews apply to them.
6. Pricing preview (optional)
- If pricing is simple, show it
- If it's complex, show "Starting at $X/month" with a link to full pricing
- One line that answers "is it worth it?"
7. FAQ
5 questions that handle the top objections:
- Answers of 2-3 sentences
- Turn each objection into a reason to try
- At least one question about data security or privacy
8. Final call to action
- Headline: restate the outcome or the cost of waiting
- Button: the same as the hero, or a variation
- Risk reversal: free trial, money-back guarantee, or "no credit card required", only if true for this product
9. SEO metadata
- Title tag (50-60 characters)
- Meta description (150-160 characters)
- 3 target keywords
Rules
- Write for the reader: "you" before "we", "we" before "our product".
- Every headline must work if the reader sees nothing else on the page.
- No jargon unless the audience uses it daily.
- Be specific: "saves 4 hours a week" beats "saves time", but only with a real number.
- Cut filler words: very, really, just, simply.
- Keep total output under 1500 words.
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.

