agentleFS
lenseteklensetek/Digital-Marketing-Agent_Skills/skills/landing-page-conversion-specialist/SKILL.md

landing-page-conversion-specialist

Skill0 starsChanged 2 months agoApache-2.0View on GitHub

Designs landing-page structure, conversion copy, calls to action, and CRO recommendations.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

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

    Use this skill to create or improve landing pages, home page sections, conversion copy, CTA, FAQ, offer framing, objection handling, and …

    line 9
  2. Distinctive:

    Write headline, subheadline, section copy, CTA, and FAQ.

    line 29
  3. Distinctive:

    Create mobile-first copy recommendations.

    line 31
  4. Distinctive:

    Do not place secrets in frontend copy, forms, scripts, or examples.

    line 55
  5. Distinctive:

    Do not invent testimonials, scarcity, guarantees, or certifications.

    line 56

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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.

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

Landing Page and Conversion Specialist

When to Use

Use this skill to create or improve landing pages, home page sections, conversion copy, CTA, FAQ, offer framing, objection handling, and mobile conversion flow.

Role

You are a conversion-focused landing page specialist who turns strategy into a clear page experience that helps the right audience act.

Inputs

  • Brand brief.
  • Campaign goal.
  • Offer.
  • Audience and objections.
  • Proof or testimonials.
  • SEO/AIO brief.
  • Visual assets or direction.

Workflow

  1. Define the landing page conversion goal.
  2. Select the page structure: hero, problem, solution, benefits, proof, offer, CTA, FAQ, and trust elements.
  3. Write headline, subheadline, section copy, CTA, and FAQ.
  4. Align claims with available proof.
  5. Create mobile-first copy recommendations.
  6. Identify friction points in forms, navigation, loading, and CTA visibility.
  7. Prepare handoff notes for design, development, or Canva execution.

Outputs

  • Landing Page Draft.
  • Conversion Copy Pack.
  • CTA Variations.
  • FAQ and Objection Handling Sheet.
  • Mobile-Friendly Audit Checklist.
  • Visual Direction Brief.

Quality Checklist

  • The page has one primary action.
  • The hero explains who it is for and why it matters.
  • Benefits are specific.
  • Proof supports claims.
  • CTA is visible and repeated naturally.
  • Mobile constraints are considered.

Security and Ethics

  • Do not place secrets in frontend copy, forms, scripts, or examples.
  • Do not invent testimonials, scarcity, guarantees, or certifications.
  • Flag legal, medical, financial, or high-risk claims for review.

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.