solo-landing-gen
Generate landing page content from PRD — hero section, features, A/B headline variants, CTA, and SEO meta tags. Use when user says "create landing page", "write landing copy", "hero section", "A/B headlines", or "landing content". Can scaffold actual pages for astro-static. Do NOT use for SEO auditing (use /seo-audit).
Install via CLI (Recommended)
clawhub install openclaw/skills/skills/fortunto2/solo-landing-gen/landing-gen
Generate landing page content from a project's PRD. Produces hero section, features, social proof, CTA, SEO meta tags, and A/B headline variants. If astro-static stack detected, can scaffold actual page files.
MCP Tools (use if available)
kb_search(query)— find related methodology (conversion, copywriting)project_info(name)— get project stack and detailsweb_search(query)— competitor landing analysis
If MCP tools are not available, fall back to Glob + Grep + Read.
Steps
-
Parse project from
$ARGUMENTS.- Read PRD, README, or research.md for product info.
- If empty: ask via AskUserQuestion.
-
Detect stack:
- Check for
astro.config.*→ astro-static (can scaffold page) - Check for
next.config.*→ Next.js (can scaffold route) - Otherwise: generate content-only markdown
- Check for
-
Extract landing inputs from PRD/README:
- Problem: 1 sentence pain statement
- Solution: 1 sentence product description
- ICP: Target user persona
- Features: Top 3-4 differentiating features with descriptions
- Competitors: From research.md (if exists) — for positioning
- Pricing: If available
-
Competitor landing analysis (optional, if MCP/WebSearch available):
- Search for top 3 competitor landing pages
- Note: headline patterns, CTA language, social proof types
- Identify positioning gaps
-
Forced reasoning — conversion strategy: Before generating, write out:
- Primary conversion: What's the ONE action? (sign up / download / buy)
- Objections: Top 3 reasons someone wouldn't convert
- Trust signals: What overcomes each objection?
- Above the fold: Problem + Solution + CTA — nothing else
-
Generate landing content:
6a. Hero Section
- Headline: Problem-focused, benefit-driven (8-12 words)
- Subheadline: How the product solves it (15-25 words)
- CTA button: Action verb + outcome ("Start Free Trial", "Download Now")
- Visual: Describe what image/screenshot/demo should be shown
6b. A/B Headline Variants (5 options)
Generate 5 distinct headline approaches:
- Pain-focused: "Tired of {problem}?"
- Benefit-focused: "{Outcome} without {hassle}"
- Curiosity: "The {adjective} way to {action}"
- Social proof: "Join {N}+ {users} who {outcome}"
- Direct: "{Product}: {one-line value prop}"
6c. Features Section (3-4 features)
For each feature:
- Icon suggestion (emoji or icon name)
- Feature title (3-5 words)
- Feature description (1-2 sentences)
- Benefit framing (what user gains, not what product does)
6d. Social Proof Section
- Placeholder for testimonials (template with name, role, quote)
- Metrics placeholders ("X+ users", "Y% faster", "Z countries")
- Trust badges placeholder (App Store rating, awards, press)
Metadata
Not sure this is the right skill?
Describe what you want to build — we'll match you to the best skill from 16,000+ options.
Find the right skillPaste this into your clawhub.json to enable this plugin.
{
"plugins": {
"official-fortunto2-solo-landing-gen": {
"enabled": true,
"auto_update": true
}
}
}Related Skills
solo-swarm
Launch 3 parallel research agents (market, users, tech) to investigate an idea from multiple angles simultaneously. Use when user says "swarm research", "parallel research", "investigate fast", "3 agents", "team research", or wants faster alternative to /research. Produces research.md. Do NOT use for solo research (use /research) or idea scoring (use /validate).
solo-build
Execute implementation plan tasks with TDD workflow, auto-commit, and phase gates. Use when user says "build it", "start building", "execute plan", "implement tasks", "ship it", or references a track ID. Do NOT use for planning (use /plan) or scaffolding (use /scaffold).
solo-metrics-track
Set up PostHog metrics plan with event funnel, KPI benchmarks, and kill/iterate/scale decision thresholds. Use when user says "set up metrics", "track KPIs", "PostHog events", "funnel analysis", "when to kill or scale", or "success metrics". Do NOT use for SEO metrics (use /seo-audit).
solo-audit
Health check knowledge base for broken links, missing frontmatter, tag inconsistencies, and coverage gaps. Use when user says "audit KB", "check frontmatter", "find broken links", "tag cleanup", or "knowledge base quality". Do NOT use for SEO audits (use /seo-audit) or code reviews.
solo-seo-audit
SEO health check for any URL — analyzes meta tags, OG, JSON-LD, sitemap, robots.txt, SERP positions, and scores 0-100. Use when user says "check SEO", "audit this page", "SEO score", "check meta tags", or "SERP position". Do NOT use for generating landing content (use /landing-gen) or social media posts (use /content-gen).