Agent skill

Write Landing

by OpenClaudia in OpenClaudia/openclaudia-skills

Create high-converting landing page copy and structure. An agent skill from OpenClaudia/openclaudia-skills.

MITAuto-check passedFrontend & Design

Install Write Landing

skills CLI
$ npx skills add OpenClaudia/openclaudia-skills --skill write-landing -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install OpenClaudia/openclaudia-skills write-landing --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/OpenClaudia/openclaudia-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/write-landing .claude/skills/write-landing && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
write-landing
GitHub stars
711
Token cost
~5k tokens
SKILL.md length
1,309 words
Files
1
Skills in repo
74
Repo updated
First seen
Licence
MIT

At a glance

Create high-converting landing page copy and structure. An agent skill from OpenClaudia/openclaudia-skills.

  • Works in 5 steps: Gather the Brief → Choose the Page Structure → Write Each Section → …
  • The user says landing page
  • SKILL.md covers Landing Page Process, Output Format and Important Notes
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Write Landing is an agent skill from OpenClaudia/openclaudia-skills. Create high-converting landing page copy and structure. Use when the user says "landing page", "sales page", "create a landing page", "landing page copy", "conversion page", "lead gen page", "signup page", "product page copy", "hero section", "write landing page", or asks for marketing page copy with conversion goals.

Its SKILL.md is about 5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Frontend & Design, covering Landing pages and Copywriting. The repository describes itself as: 77 open-source marketing skills for Claude Code, Codex, and other AI coding agents. SEO, content, email, ads, analytics, and growth. The licence is MIT.

When your agent uses it

  • The user says landing page
  • Create a landing page
  • Landing page copy
  • Conversion page

Example prompts

  • “landing page”
  • “sales page”
  • “create a landing page”
  • “/write-landing”

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Gather the Brief
  2. Choose the Page Structure
  3. Write Each Section
  4. SEO Optimization
  5. Conversion Optimization Checklist

What it can do on your machine

Read from SKILL.md and the folder at commit 28bf209. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are typescript).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Write Landing loads about 5k tokens when it runs. Until then it costs about 83 tokens; SKILL.md has 1,309 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~83
When it runs · the whole SKILL.md, loaded when a task matches
~5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from OpenClaudia/openclaudia-skills at commit 28bf209, republished under its MIT licence (© OpenClaudia). 1,309 words, ~4,996 tokens.

Download SKILL.mdSave it as .claude/skills/write-landing/SKILL.md (or your agent's skills folder).
name
write-landing
description
Create high-converting landing page copy and structure. Use when the user says "landing page", "sales page", "create a landing page", "landing page copy", "conversion page", "lead gen page", "signup page", "product page copy", "hero section", "write landing page", or asks for marketing page copy with conversion goals.

Write Landing Page Skill

You are an expert conversion copywriter and landing page strategist. Create complete landing page copy with wireframe structure, optimized for both conversions and SEO. Output is ready to implement in Next.js/React with Tailwind CSS.

Landing Page Process

Step 1: Gather the Brief

Before writing, understand:

QuestionWhy it matters
Product/Service: What are you selling?Core messaging foundation
Target audience: Who is the ideal customer?Voice, pain points, language
Primary goal: What action should visitors take?CTA optimization
Traffic source: How will people arrive? (Ads, organic, email)Message match
Price point: How much does it cost?Objection handling depth
Key differentiator: Why you over competitors?USP positioning
Proof points: Testimonials, case studies, metrics?Social proof section
Existing brand voice: Formal, casual, technical?Tone consistency

If the user doesn't provide all of these, ask for the critical ones (product, audience, goal) and make reasonable assumptions for the rest.

Step 2: Choose the Page Structure

Select the right framework based on the product type and traffic temperature:

Framework A: PAS (Problem-Agitation-Solution)

Best for: Cold traffic, awareness stage, complex problems

Hero (Problem statement)
  -> Agitate (Consequences of not solving)
  -> Solution (Your product)
  -> Features/Benefits
  -> Social Proof
  -> CTA
Framework B: AIDA (Attention-Interest-Desire-Action)

Best for: Warm traffic, known product category

Hero (Attention-grabbing headline)
  -> Interest (Key features and hook)
  -> Desire (Benefits, social proof, FOMO)
  -> Action (CTA with urgency)
Framework C: Before-After-Bridge

Best for: Transformation products (SaaS, courses, coaching)

Hero (Before: current painful state)
  -> After (Vision of success)
  -> Bridge (Your product is the bridge)
  -> How it works
  -> Proof
  -> CTA
Framework D: Feature-Benefit Grid

Best for: Technical products, SaaS, feature-rich tools

Hero (Bold promise)
  -> Feature-benefit grid
  -> How it works (3 steps)
  -> Integrations/Compatibility
  -> Pricing
  -> FAQ
  -> CTA
Step 3: Write Each Section
Section 1: Hero

The hero section has 5 seconds to hook the visitor. Every word must earn its place.

Headline formula (H1):

FormulaWhen to useExample
{End result} without {Pain point}When eliminating a known pain"Build your website without writing code"
{Action verb} your {metric} by {amount}When you have proven results"Double your email open rates in 30 days"
The {adjective} way to {desired outcome}When the method is the differentiator"The fastest way to deploy full-stack apps"
{Desired outcome} for {audience}When audience-specific"Enterprise-grade security for startups"
Stop {pain}. Start {benefit}.When the problem is acute"Stop losing leads. Start closing deals."
{Number} {people} use {product} to {outcome}When you have social proof scale"50,000 marketers use Buffer to grow on social"

Headline rules:

  • Max 10 words (6-8 is ideal)
  • Specific > vague ("50% faster" > "blazing fast")
  • Benefit > feature ("Save 10 hours/week" > "AI-powered automation")
  • Include the audience or their goal

Subheadline (H2): Expand on the headline with specifics. Formula:

{Product} helps {audience} {achieve outcome} by {mechanism/method}. {Proof point or time frame}.

Example: "Acme helps SaaS teams automate their deployment pipeline with one-click CI/CD. Ship 10x faster from day one."

CTA Button:

  • Use first-person: "Start my free trial" > "Start your free trial"
  • Action-oriented: "Get started free" > "Submit" > "Sign up"
  • Add micro-copy below: "No credit card required. Free for 14 days."
  • Button color should contrast with background (high contrast = more clicks)

Supporting element (choose one):

  • Product screenshot or demo video
  • Key metric ("Trusted by 10,000+ companies")
  • Logo bar of notable customers
  • Short demo GIF
tsx
{/* Hero Section */}
<section className="relative bg-white pt-20 pb-16 sm:pt-24 sm:pb-20 lg:pt-32 lg:pb-28">
  <div className="mx-auto max-w-7xl px-4 sm:px-6 lg:px-8">
    <div className="mx-auto max-w-2xl text-center lg:max-w-4xl">
      {/* Eyebrow / Social proof badge */}
      <p className="text-sm font-semibold text-indigo-600">
        Trusted by 10,000+ teams
      </p>

      {/* H1 Headline */}
      <h1 className="mt-4 text-4xl font-bold tracking-tight text-gray-900 sm:text-5xl lg:text-6xl">
        {headline}
      </h1>

      {/* Subheadline */}
      <p className="mt-6 text-lg leading-8 text-gray-600 sm:text-xl">
        {subheadline}
      </p>

      {/* CTA Group */}
      <div className="mt-10 flex flex-col items-center gap-4 sm:flex-row sm:justify-center">
        <a href="#" className="rounded-lg bg-indigo-600 px-8 py-4 text-base font-semibold text-white shadow-sm hover:bg-indigo-500 focus-visible:outline-2 focus-visible:outline-offset-2 focus-visible:outline-indigo-600">
          {primaryCTA}
        </a>
        <a href="#" className="text-base font-semibold text-gray-900 hover:text-gray-700">
          {secondaryCTA} <span aria-hidden="true">&rarr;</span>
        </a>
      </div>

      {/* Micro-copy */}
      <p className="mt-4 text-sm text-gray-500">
        No credit card required. Free 14-day trial.
      </p>
    </div>

    {/* Hero Image/Video */}
    <div className="mt-16 sm:mt-20">
      <div className="rounded-xl bg-gray-900/5 p-2 ring-1 ring-gray-900/10 lg:rounded-2xl">
        {/* Product screenshot or demo */}
      </div>
    </div>
  </div>
</section>

Section 2: Problem / Pain Points

Make the reader feel understood. Describe their current situation precisely.

Writing technique: Use the reader's own language. Mirror the words they use in reviews, support tickets, and forums.

tsx
<section className="bg-gray-50 py-16 sm:py-24">
  <div className="mx-auto max-w-7xl px-4 sm:px-6 lg:px-8">
    <div className="mx-auto max-w-2xl text-center">
      <h2 className="text-3xl font-bold tracking-tight text-gray-900 sm:text-4xl">
        {problem_headline}
      </h2>
      <p className="mt-4 text-lg text-gray-600">
        {problem_description}
      </p>
    </div>

    <div className="mt-12 grid grid-cols-1 gap-8 sm:grid-cols-2 lg:grid-cols-3">
      {/* Pain point cards */}
      {painPoints.map((pain) => (
        <div className="rounded-lg border border-red-100 bg-white p-6">
          <div className="text-red-500 text-2xl mb-3">{pain.icon}</div>
          <h3 className="text-lg font-semibold text-gray-900">{pain.title}</h3>
          <p className="mt-2 text-gray-600">{pain.description}</p>
        </div>
      ))}
    </div>
  </div>
</section>

Pain point formula:

Title: "{Frustrating situation}"
Description: "You {specific scenario}. But {consequence}. And {escalation}."

Example:

  • Title: "Deployment takes hours, not minutes"
  • Description: "You push code and wait. Build fails. Fix it. Wait again. By the time it's live, the bug report queue has doubled. And your weekend is gone."

Section 3: Solution / How It Works

Transition from pain to solution. Show the product as the bridge.

"How It Works" in 3 steps (always 3 - humans love triads):

tsx
<section className="bg-white py-16 sm:py-24">
  <div className="mx-auto max-w-7xl px-4 sm:px-6 lg:px-8">
    <div className="mx-auto max-w-2xl text-center">
      <h2 className="text-3xl font-bold tracking-tight text-gray-900 sm:text-4xl">
        How it works
      </h2>
      <p className="mt-4 text-lg text-gray-600">
        Get started in minutes, not months.
      </p>
    </div>

    <div className="mt-16 grid grid-cols-1 gap-12 lg:grid-cols-3">
      {steps.map((step, i) => (
        <div className="text-center">
          <div className="mx-auto flex h-12 w-12 items-center justify-center rounded-full bg-indigo-100 text-indigo-600 font-bold text-xl">
            {i + 1}
          </div>
          <h3 className="mt-6 text-xl font-semibold text-gray-900">{step.title}</h3>
          <p className="mt-4 text-gray-600">{step.description}</p>
        </div>
      ))}
    </div>
  </div>
</section>

Step formula:

Step 1: "{Simple first action}" - Lower the barrier to entry
Step 2: "{Core value action}" - The product doing its thing
Step 3: "{Desired outcome}" - The result they care about

Example:

  1. "Connect your repo" - Link your GitHub in one click
  2. "Push your code" - Our AI handles builds, tests, and deployment
  3. "Ship with confidence" - Go live in minutes with zero-downtime deploys

Section 4: Features & Benefits

Never list features alone. Always pair with the benefit (the "so what?").

Feature-Benefit formula:

Feature: {What it does}
Benefit: So you can {outcome the user cares about}
tsx
<section className="bg-white py-16 sm:py-24">
  <div className="mx-auto max-w-7xl px-4 sm:px-6 lg:px-8">
    <div className="mx-auto max-w-2xl text-center">
      <h2 className="text-3xl font-bold tracking-tight text-gray-900 sm:text-4xl">
        Everything you need to {desired outcome}
      </h2>
    </div>

    <div className="mt-16 grid grid-cols-1 gap-8 sm:grid-cols-2 lg:grid-cols-3">
      {features.map((feature) => (
        <div className="relative rounded-2xl border border-gray-200 p-8">
          <div className="text-indigo-600 mb-4">{feature.icon}</div>
          <h3 className="text-lg font-semibold text-gray-900">{feature.title}</h3>
          <p className="mt-2 text-gray-600">{feature.benefit}</p>
        </div>
      ))}
    </div>
  </div>
</section>

Arrange features by importance:

  1. The feature that solves the #1 pain point (biggest, most prominent)
  2. The feature that differentiates from competitors
  3. Supporting features that round out the product
  4. Nice-to-haves and integrations

Section 5: Social Proof

Social proof is the most persuasive element on the page. Layer multiple types:

Types of social proof (use 2-3):

TypeImpact LevelExample
Customer testimonials with photo + name + companyHighest"Acme increased revenue 40% in 3 months" - Jane Doe, CEO at TechCo
Case study metricsHighest"From 2 deploys/week to 50 deploys/day"
Logo bar of customersHighWell-known brand logos
Number of customersHigh"Join 50,000+ teams"
Star ratings / review scoresHigh"4.8/5 on G2 (500+ reviews)"
Awards / certificationsMedium"SOC 2 Certified", "G2 Leader 2025"
Media mentionsMedium"As featured in TechCrunch, Forbes..."
Integration partnersMedium"Works with Slack, GitHub, Jira..."
tsx
{/* Testimonial Section */}
<section className="bg-gray-50 py-16 sm:py-24">
  <div className="mx-auto max-w-7xl px-4 sm:px-6 lg:px-8">
    <div className="mx-auto max-w-2xl text-center">
      <h2 className="text-3xl font-bold tracking-tight text-gray-900 sm:text-4xl">
        Loved by teams worldwide
      </h2>
    </div>

    <div className="mt-16 grid grid-cols-1 gap-8 lg:grid-cols-3">
      {testimonials.map((t) => (
        <div className="rounded-2xl bg-white p-8 shadow-sm ring-1 ring-gray-200">
          <div className="flex items-center gap-1 text-yellow-400">
            {/* 5 star icons */}
          </div>
          <blockquote className="mt-4 text-gray-700">
            &ldquo;{t.quote}&rdquo;
          </blockquote>
          <div className="mt-6 flex items-center gap-4">
            <img src={t.avatar} alt={t.name} className="h-12 w-12 rounded-full" />
            <div>
              <p className="font-semibold text-gray-900">{t.name}</p>
              <p className="text-sm text-gray-500">{t.role} at {t.company}</p>
            </div>
          </div>
        </div>
      ))}
    </div>

    {/* Logo bar */}
    <div className="mt-16">
      <p className="text-center text-sm font-semibold text-gray-500">
        Trusted by leading companies
      </p>
      <div className="mt-6 flex flex-wrap items-center justify-center gap-x-12 gap-y-6">
        {/* Customer logos */}
      </div>
    </div>
  </div>
</section>

Testimonial writing rules:

  • Include specific outcomes ("40% more leads" > "more leads")
  • Include name, role, company, and photo (real > stock)
  • Match testimonials to the objection they overcome
  • Put the most impressive testimonial closest to the CTA

Show full SKILL.md (521 more words)Show less
Section 6: Objection Handling / FAQ

Address the top 5-7 objections that prevent conversion:

Common objection categories:

ObjectionHow to address
"It's too expensive"ROI comparison, cost of inaction, payment plans
"I don't have time to set up"Quick start time, onboarding support, migration help
"What if it doesn't work for me?"Guarantee, free trial, case studies from similar companies
"I'm locked into {competitor}"Migration tools, comparison, switching cost analysis
"Is my data safe?"Security certifications, compliance, data policies
"What if I need help?"Support channels, response time SLA, documentation
"It looks too complex"3-step "how it works", demo video, free trial
tsx
<section className="bg-white py-16 sm:py-24">
  <div className="mx-auto max-w-7xl px-4 sm:px-6 lg:px-8">
    <div className="mx-auto max-w-3xl">
      <h2 className="text-3xl font-bold tracking-tight text-gray-900 sm:text-4xl text-center">
        Frequently asked questions
      </h2>

      <dl className="mt-12 space-y-8">
        {faqs.map((faq) => (
          <div className="border-b border-gray-200 pb-8">
            <dt className="text-lg font-semibold text-gray-900">{faq.question}</dt>
            <dd className="mt-4 text-gray-600">{faq.answer}</dd>
          </div>
        ))}
      </dl>
    </div>
  </div>
</section>

Section 7: Pricing (if applicable)

Only include pricing on the landing page if:

  • The product has clear, fixed pricing
  • The user wants pricing on the page
  • The traffic is warm/hot (they already know what the product does)
tsx
<section className="bg-gray-50 py-16 sm:py-24" id="pricing">
  <div className="mx-auto max-w-7xl px-4 sm:px-6 lg:px-8">
    <div className="mx-auto max-w-2xl text-center">
      <h2 className="text-3xl font-bold tracking-tight text-gray-900 sm:text-4xl">
        Simple, transparent pricing
      </h2>
      <p className="mt-4 text-lg text-gray-600">
        {pricing_subheadline}
      </p>
    </div>

    <div className="mt-16 grid grid-cols-1 gap-8 lg:grid-cols-3">
      {plans.map((plan) => (
        <div className={`rounded-2xl p-8 ring-1 ${plan.featured ? 'bg-indigo-600 text-white ring-indigo-600' : 'bg-white ring-gray-200'}`}>
          <h3 className="text-lg font-semibold">{plan.name}</h3>
          <p className="mt-2 text-sm opacity-80">{plan.description}</p>
          <p className="mt-6">
            <span className="text-4xl font-bold">${plan.price}</span>
            <span className="text-sm opacity-80">/month</span>
          </p>
          <ul className="mt-8 space-y-3">
            {plan.features.map((f) => (
              <li className="flex items-center gap-3">
                {/* Check icon */}
                <span>{f}</span>
              </li>
            ))}
          </ul>
          <a href="#" className={`mt-8 block w-full rounded-lg py-3 text-center font-semibold ${plan.featured ? 'bg-white text-indigo-600' : 'bg-indigo-600 text-white'}`}>
            {plan.cta}
          </a>
        </div>
      ))}
    </div>
  </div>
</section>

Pricing copy rules:

  • Anchor with the highest plan first (or highlight the middle plan)
  • Use specific numbers ("$49/mo" > "Starting at...")
  • Show value: "$49/mo - less than the cost of one lost lead"
  • Feature the most popular plan with a badge
  • Include annual discount toggle if applicable

Section 8: Final CTA

The closing CTA should create urgency and restate the core value:

tsx
<section className="bg-indigo-600 py-16 sm:py-24">
  <div className="mx-auto max-w-7xl px-4 sm:px-6 lg:px-8">
    <div className="mx-auto max-w-2xl text-center">
      <h2 className="text-3xl font-bold tracking-tight text-white sm:text-4xl">
        {final_headline}
      </h2>
      <p className="mt-4 text-lg text-indigo-100">
        {final_subheadline}
      </p>
      <div className="mt-10">
        <a href="#" className="rounded-lg bg-white px-8 py-4 text-base font-semibold text-indigo-600 shadow-sm hover:bg-indigo-50">
          {finalCTA}
        </a>
      </div>
      <p className="mt-4 text-sm text-indigo-200">
        {risk_reversal - e.g., "30-day money-back guarantee. Cancel anytime."}
      </p>
    </div>
  </div>
</section>

Final CTA formulas:

"Ready to {desired outcome}?"
"Start {action}ing today"
"Join {number}+ {audience} already {outcome}"
"Don't let {pain point} hold you back"
"{Outcome} is one click away"
Step 4: SEO Optimization

Landing pages should rank too. Include:

Meta tags:

  • Title: "{Product} - {Primary benefit} | {Brand}" (50-60 chars)
  • Description: "{Product} helps {audience} {outcome}. {Proof point}. {CTA}." (150-160 chars)

On-page SEO:

  • H1 includes primary keyword
  • Primary keyword in first 100 words
  • Image alt text with keyword
  • Internal links to and from the landing page
  • Schema markup (Product, Organization, FAQ, or SoftwareApplication)

Reminder: Landing pages for paid traffic may need noindex if they duplicate content from organic pages.

Step 5: Conversion Optimization Checklist

Before delivering, verify:

  • Single, clear CTA (one primary action per page)
  • CTA appears 3+ times (hero, middle, end)
  • CTA button text is action-oriented and first-person
  • Page loads fast (minimize scripts, optimize images)
  • Mobile responsive (all sections tested at 375px)
  • No navigation menu (or minimal) to reduce exit points
  • Social proof within scroll of first CTA
  • Risk reversal near every CTA (guarantee, free trial, no CC)
  • Benefit-first headlines (not feature-first)
  • Specific numbers > vague claims
  • White space between sections (not cluttered)
  • Contrast on CTA buttons (stands out from page)
  • Urgency element where authentic (limited spots, deadline, rising price)

Output Format

Deliver in this order:

  1. Page strategy - Framework chosen, audience, goal, messaging hierarchy
  2. Full copy document - All sections with headlines, body copy, CTAs, and micro-copy
  3. Wireframe structure - Section order with Tailwind component code
  4. SEO metadata - Title, description, schema markup
  5. A/B test suggestions - 2-3 elements to test first (headline, CTA, social proof)

Important Notes

  • Every claim needs proof. "Best tool" needs a G2 ranking. "Fastest" needs a benchmark. Unsubstantiated claims reduce trust.
  • Write at a Grade 6-8 reading level. Simple words, short sentences, clear logic.
  • If the user provides brand guidelines or voice preferences, follow them. If not, default to: confident, clear, conversational, not salesy.
  • For SaaS: emphasize ease of setup, time to value, and integration ecosystem.
  • For e-commerce: emphasize product quality, shipping speed, return policy, and reviews.
  • For services: emphasize expertise, process, results, and risk reversal.

© OpenClaudia, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/write-landing of OpenClaudia/openclaudia-skills.

Open the folder on GitHubat commit 28bf209

Compare with similar skills

Write Landing next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Write Landing compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Write Landing this skillOpenClaudia/openclaudia-skills711—~5kAutomated safety check: PassMIT
Kill AI Slopyetone/kill-ai-slop1.3k—~1.4kAutomated safety check: PassApache-2.0
Landing Page Copywriterjulianromli/ai-skills1912 repos~1.4kAutomated safety check: PassNone
Refero Designreferodesign/refero_skill295—~5.3kAutomated safety check: PassMIT
Landing Page Generatorbuildfastwithai/gen-ai-experiments785—~1.5kAutomated safety check: PassMIT
Arabic Copy Localizergrowthack88/growth-marketing-os115—~1kAutomated safety check: PassMIT

Similar skills

  • Kill AI Slop

    yetone/kill-ai-slop

    Find and remove AI slop — the generic, machine-default visual and copy tics of vibe-coded products — from a web project.

    1.3k GitHub stars~1.4k tokensUpdated 23 days ago
    Frontend & DesignAuto-check passed
  • Landing Page Copywriter

    julianromli/ai-skills

    Write high-converting landing page copy using proven frameworks like PAS (Problem-Agitate-Solution), AIDA, and StoryBrand.

    191 GitHub starsUsed in 2 repos~1.4k tokens
    Frontend & DesignAuto-check passed
  • Refero Design

    referodesign/refero_skill

    Primary/default skill for UI design, product design, web design, landing pages, dashboards, product screens, redesigns, visual polish, frontend/CSS styling, design systems, components, responsive…

    295 GitHub stars~5.3k tokensUpdated 1 mo ago
    Frontend & DesignAuto-check passed
  • Landing Page Generator

    buildfastwithai/gen-ai-experiments

    Builds a single self-contained HTML landing page from a template with copy frameworks, four themes and SEO meta, then runs bundled audit scripts for conversion and speed.

    785 GitHub stars~1.5k tokensUpdated 16 days ago
    Frontend & DesignAuto-check passed
  • Arabic Copy Localizer

    growthack88/growth-marketing-os

    Marketing copy localization skill that converts English marketing copy (ads, landing pages, emails, CTAs) into native Egyptian Arabic عامية — or GCC dialect on request — with natural English…

    115 GitHub stars~1k tokensUpdated 6 days ago
    Frontend & DesignAuto-check passed
  • Landing Page

    emotixco/claude-skills-founder

    Write landing page copy section by section, from hero to final call to action, including FAQ and SEO metadata.

    517 GitHub stars~927 tokensUpdated yesterday
    Frontend & DesignAuto-check passed

More from OpenClaudia/openclaudia-skills

All 74 skills in this repo
  • Competitor Traffic Report

    OpenClaudia/openclaudia-skills

    Build an interactive competitive-traffic report for any company and its rivals — monthly visits (SimilarWeb), organic search traffic and Domain Rating (Ahrefs) — as one self-contained HTML page with…

    711 GitHub stars~1.2k tokensUpdated 20 days ago
    Auto-check passed
  • Geo Difficulty

    OpenClaudia/openclaudia-skills

    Score how hard a keyword is to rank for in the AI-search era — page-level URL Rating of real competitors (not just domain DR), Ahrefs keyword difficulty, and whether a given site already ranks or is…

    711 GitHub stars~694 tokensUpdated 20 days ago
    Auto-check passed
  • Gsc Portfolio Audit

    OpenClaudia/openclaudia-skills

    Audit EVERY Google Search Console property at once — rank all sites by clicks and impressions with period-over-period deltas, then diff keywords per site to surface what is newly ranking, rising…

    711 GitHub stars~1k tokensUpdated 20 days ago
    Auto-check passed
  • Similarweb Traffic

    OpenClaudia/openclaudia-skills

    Fetch website traffic estimates (monthly visits, traffic sources, top countries, keywords, engagement, ranks) for any domain from SimilarWeb.

    711 GitHub stars~882 tokensUpdated 20 days ago
    Auto-check passed
  • Ahrefs Python

    OpenClaudia/openclaudia-skills

    Manages Ahrefs API usage in Python using ahrefs-python library.

    711 GitHub stars~1.9k tokensUpdated 20 days ago
    Auto-check passed
  • Ab Test Setup

    OpenClaudia/openclaudia-skills

    Design, plan, and analyze A/B tests with statistical rigor. An agent skill from OpenClaudia/openclaudia-skills.

    711 GitHub stars~1.7k tokensUpdated 20 days ago
    Auto-check passed

Questions about Write Landing

What does Write Landing do?

Create high-converting landing page copy and structure. An agent skill from OpenClaudia/openclaudia-skills. Write Landing is an agent skill from OpenClaudia/openclaudia-skills. Create high-converting landing page copy and structure.

When should I use Write Landing?

Write Landing fits situations like: the user says landing page; create a landing page; landing page copy; conversion page.

How do I install Write Landing in Claude Code?

Run `npx skills add OpenClaudia/openclaudia-skills --skill write-landing -a claude-code`. Or copy the skill folder (skills/write-landing in OpenClaudia/openclaudia-skills) into .claude/skills/write-landing in your project. Claude Code loads it when a task matches its description.

How do I install Write Landing in Codex?

Run `npx skills add OpenClaudia/openclaudia-skills --skill write-landing -a codex`. Or copy the skill folder (skills/write-landing in OpenClaudia/openclaudia-skills) into .agents/skills/write-landing in your project. Codex loads it when a task matches its description.

Can I use Write Landing in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add OpenClaudia/openclaudia-skills --skill write-landing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/write-landing, .gemini/skills/write-landing, .github/skills/write-landing and .opencode/skills/write-landing in your project.

What does Write Landing need to run?

SKILL.md names no scripts, command-line tools or credentials: Write Landing is instructions for the agent only.

Does Write Landing access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Write Landing safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Write Landing use?

Write Landing is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Write Landing use?

About 5k tokens (SKILL.md is roughly 20k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Write Landing?

Skills that share tags, products or a category with Write Landing: Kill AI Slop (yetone/kill-ai-slop, 1.3k stars), Landing Page Copywriter (julianromli/ai-skills, 191 stars), Refero Design (referodesign/refero_skill, 295 stars) and Landing Page Generator (buildfastwithai/gen-ai-experiments, 785 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Write Landing?

OpenClaudia (a GitHub organization) maintains it in OpenClaudia/openclaudia-skills, which has 711 GitHub stars. The repository holds 74 skills in this directory. The repository was last updated on September 18, 2026.

Source: OpenClaudia/openclaudia-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.