landing-page
Skill6 starsChanged 4 months agoMITView on GitHub
Writes complete landing-page copy section by section — headline options, lead, mechanism, proof, offer, FAQ, and CTA blocks — with a design note per section. Use when the page needs copy a designer can build from directly, not a wireframe full of placeholders.
44 other projects use a version of this.
Adopted by
Most recently taken up by
- ImBIOS/skillstheir own version, first seen Nov 8, 2026
- ainurdev/mystical-assistanttheir own version, first seen Nov 8, 2026
- itsryanarmani/skillstheir own version, first seen Nov 8, 2026
- pooriaarab/skillstheir own version, first seen Nov 7, 2026
- Littlpinguin/marketing-cockpit-templatetheir own version, first seen Nov 3, 2026
- tandryukha/aidemotheir own version, first seen Nov 3, 2026
Used with
Projects with it also use operational-enterprise-ai, product-proof-saas and 10 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 versions44 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 44
- emotixco/claude-skills-founder★ 796same name
- boraoztunc/skills★ 454same 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★ 27same name
- ariaxhan/kernel-claude★ 15same name
34 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 repository29 other files it gives its agents.
- ad-scriptsSkill
- battlecardSkill
- brand-voiceSkill
- campaign-debriefSkill
- case-study-writerSkill
- channel-pickerSkill
- cmoSkill
- competitor-teardownSkill
- content-calendarSkill
- creative-briefSkill
- customer-deep-diveSkill
- email-sequenceSkill
- experiment-backlogSkill
- funnel-mapSkill
- hook-factorySkill
- kpi-treeSkill
- launch-planSkill
- lead-magnet-builderSkill
- marketing-auditSkill
- market-research-sprintSkill
- message-mapSkill
- objection-mapSkill
- offer-builderSkill
- onboardSkill
- positioning-workshopSkill
- pricing-testSkill
- repurposeSkill
- research-to-briefSkill
- weekly-reviewSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 39 edited versions we read keep these.
1
Distinctive
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 37
Every section advances the argument or gets cut.
“Common” is measured: kept by at least 6 in 10 of the 39 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
Landing Page — one argument, delivered in sections
A landing page is a single argument. The visitor arrives mid-thought — from an ad, an email, a post — carrying a problem and a doubt. Every section either advances the argument or leaks visitors. This skill writes the argument in order, in the buyer's language, and shows its proof or admits it does not have it.
Inputs
- The offer, the audience, and the traffic source feeding the page: $ARGUMENTS
- From
marketing-brief.mdif present: the offer, positioning & message, top pains and desired outcomes, objections & beliefs, the language bank (voice-of-customer), any recorded proof and results, and the banned-phrases list.
Do this
- Fix the entry state. What did the visitor just see, and what do they already believe? An ad click, an email click, and an organic search arrive at different temperatures. The headline continues their thought — it never restarts the conversation.
- Write five headline options, one per structure, each with its subhead. Recommend one and give the reasoning in a line:
- Outcome-led — the result, specific, no adjectives doing the work.
- Problem-led — the pain named so precisely it reads like surveillance.
- Mechanism-led — the how, for markets tired of big promises.
- Proof-led — the strongest verifiable number, up front.
- Identity-led — who this is for, said plainly enough to repel the wrong visitor.
- Write the lead (the first screen): the problem in the buyer's own words, the cost of leaving it unsolved, and the promise the rest of the page will keep. Language bank, not marketing voice.
- Write the mechanism section. Why this works when what they already tried did not. Name the mechanism plainly — a believable "how" does more selling than a louder "what".
- Write the proof section using only evidence from the brief or the user: results, testimonials, demonstrations, credentials. List every proof gap explicitly rather than papering over it.
- Write the offer block. What they get, the price or the CTA that reveals it, the risk reversal, and urgency only where it is real. No invented countdowns.
- Write the FAQ from real objections — stated and real, answer-first, 5–8 questions. If the brief's objections section is thin, run
/marketing:objection-mapfirst; a FAQ answering questions nobody asks is decoration. - Place the CTA blocks — after the lead, after proof, after the offer, at the close. One action, identical everywhere; only the surrounding wording shifts with commitment level.
Output
The full page in section order — headlines with the pick, lead, mechanism, proof, offer, FAQ, CTA blocks — each with a one-line design note (what the section must look like to do its job). End with the proof-gap list: the missing evidence that would most strengthen the page.
Rules
- Headlines may exaggerate curiosity, never facts. The page must cash every cheque the headline writes.
- Evidence over invention: no fabricated testimonials, numbers, or logos. A proof gap named is fixable; a proof gap faked is fatal.
- One CTA action per page. A page asking for two things gets neither.
- Every section advances the argument or gets cut. Length is fine; padding is not.
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.

