agentleFS
styfinitystyfinity/claude-marketing-department/skills/landing-page/SKILL.md

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

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.
  • boraoztuncSkill

    operational-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

  • boraoztuncSkill

    product-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

  • Dragoon0xSkill

    pricing-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

  • Dragoon0xSkill

    onboarding-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

  • shawnpangSkill

    lead-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-skillsSkill

    email-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

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
  1. Distinctive:

    Every section advances the argument or gets cut.

    line 37

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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.md if 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

  1. 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.
  2. 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.
  3. 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.
  4. 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".
  5. 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.
  6. 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.
  7. 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-map first; a FAQ answering questions nobody asks is decoration.
  8. 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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.