SEO Aeo Landing Page Writer
henryalouf/ruflow
Writes complete, structured landing pages optimized for SEO ranking, AEO citation, and visitor conversion.
Writes or improves conversion-focused landing pages for products, services, and offers with practical SEO and AEO structure.
Install SEO Aeo Landing Page Writer
$ npx skills add sickn33/agentic-awesome-skills --skill seo-aeo-landing-page-writer -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install sickn33/agentic-awesome-skills seo-aeo-landing-page-writer --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/seo-aeo-landing-page-writer .claude/skills/seo-aeo-landing-page-writer && rm -rf skills-srcUse ~/.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/
Install the "seo-aeo-landing-page-writer" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/seo-aeo-landing-page-writer into .claude/skills/seo-aeo-landing-page-writer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "seo-aeo-landing-page-writer", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/seo-aeo-landing-page-writerType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add sickn33/agentic-awesome-skills --skill seo-aeo-landing-page-writer -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install sickn33/agentic-awesome-skills seo-aeo-landing-page-writer --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/seo-aeo-landing-page-writer .agents/skills/seo-aeo-landing-page-writer && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "seo-aeo-landing-page-writer" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/seo-aeo-landing-page-writer into .agents/skills/seo-aeo-landing-page-writer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "seo-aeo-landing-page-writer", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add sickn33/agentic-awesome-skills --skill seo-aeo-landing-page-writer -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install sickn33/agentic-awesome-skills seo-aeo-landing-page-writer --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/seo-aeo-landing-page-writer .cursor/skills/seo-aeo-landing-page-writer && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "seo-aeo-landing-page-writer" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/seo-aeo-landing-page-writer into .cursor/skills/seo-aeo-landing-page-writer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "seo-aeo-landing-page-writer", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/sickn33/agentic-awesome-skills.git --path skills/seo-aeo-landing-page-writer--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add sickn33/agentic-awesome-skills --skill seo-aeo-landing-page-writer -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install sickn33/agentic-awesome-skills seo-aeo-landing-page-writer --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/seo-aeo-landing-page-writer .gemini/skills/seo-aeo-landing-page-writer && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "seo-aeo-landing-page-writer" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/seo-aeo-landing-page-writer into .gemini/skills/seo-aeo-landing-page-writer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "seo-aeo-landing-page-writer", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install sickn33/agentic-awesome-skills seo-aeo-landing-page-writerInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add sickn33/agentic-awesome-skills --skill seo-aeo-landing-page-writer -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/seo-aeo-landing-page-writer .github/skills/seo-aeo-landing-page-writer && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "seo-aeo-landing-page-writer" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/seo-aeo-landing-page-writer into .github/skills/seo-aeo-landing-page-writer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "seo-aeo-landing-page-writer", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add sickn33/agentic-awesome-skills --skill seo-aeo-landing-page-writer -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install sickn33/agentic-awesome-skills seo-aeo-landing-page-writer --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/seo-aeo-landing-page-writer .opencode/skills/seo-aeo-landing-page-writer && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "seo-aeo-landing-page-writer" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/seo-aeo-landing-page-writer into .opencode/skills/seo-aeo-landing-page-writer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "seo-aeo-landing-page-writer", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
seo-aeo-landing-page-writer- GitHub stars
- 47k
- Used in
- 1 other repo
- Token cost
- ~1.5k tokens
- SKILL.md length
- 580 words
- Files
- 1
- Skills in repo
- 1,497
- Repo updated
- First seen
- Licence
- MIT
At a glance
Writes or improves conversion-focused landing pages for products, services, and offers with practical SEO and AEO structure.
- Works in 12 steps: SEO metadata → Hero and direct-answer block → Problem → …
- Tasks that involve Landing pages
- SKILL.md covers Inputs, Decision rules, Required page flow and Output format, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
SEO Aeo Landing Page Writer is an agent skill from sickn33/agentic-awesome-skills. Writes or improves conversion-focused landing pages for products, services, and offers with practical SEO and AEO structure.
Its SKILL.md is about 1.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 AI search optimization. The repository describes itself as: AAS Core is the local, agent-first control plane for complete catalog discovery, agent-owned selection, stack validation, and planning, backed by 2,400+ agentic skills. Includes… The licence is MIT.
When your agent uses it
- Tasks that involve Landing pages
- Tasks that involve AI search optimization
Example prompts
- “Use the seo-aeo-landing-page-writer skill to write or improves conversion-focused landing pages for products, services, and offers with practical…”
- “/seo-aeo-landing-page-writer”
Workflow steps
12 steps, taken from the first numbered list in SKILL.md.
- SEO metadata
- Hero and direct-answer block
- Problem
- Solution
- Features and benefits
- Social proof or trust evidence
- Mid-page CTA
- How it works
- Comparison or alternatives
- FAQ
- Trust and risk-reversal signals
- Final CTA
What it can do on your machine
Read from SKILL.md and the folder at commit b84d35a. 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 json and markdown).
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
SEO Aeo Landing Page Writer loads about 1.5k tokens when it runs. Until then it costs about 38 tokens; SKILL.md has 580 words of instructions outside code blocks.
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 sickn33/agentic-awesome-skills at commit b84d35a, republished under its MIT licence (© sickn33). 580 words, ~1,472 tokens.
Download SKILL.mdSave it as
.claude/skills/seo-aeo-landing-page-writer/SKILL.md (or your agent's skills folder).- name
- seo-aeo-landing-page-writer
- description
- Writes or improves conversion-focused landing pages for products, services, and offers with practical SEO and AEO structure.
- risk
- safe
- source
- community
- date_added
- 2026-04-01
Landing Page Writer Skill
Write a publishable landing-page draft that helps the intended visitor understand the offer, trust it, and take the next step. Optimize for humans first, then make the page easy for search engines and answer engines to parse.
Inputs
Use these fields when supplied. Infer only what is obvious; otherwise list missing assumptions before the draft.
{
"product_name": "string",
"business_type": "string — what the product or service does",
"target_audience": "string",
"primary_keyword": "string — exact target phrase, if known",
"secondary_keywords": ["string"],
"usp": ["string — differentiators, up to 5"],
"pain_points": ["string"],
"features": ["string"],
"benefits": ["string — user outcomes mapped to features"],
"social_proof": {"testimonials": ["string"], "logos": ["string"], "stats": ["string"]},
"cta_primary": "string",
"cta_secondary": "string",
"offer": "string — optional and factual",
"keyword_data": "string — optional seo-aeo-keyword-research output",
"competitor": "string — optional named alternative",
"tone": "professional | conversational | bold | empathetic | authoritative"
}If critical inputs are missing, proceed with clearly marked placeholders rather than inventing product facts. Never invent customers, reviews, logos, performance claims, prices, guarantees, awards, security claims, or compliance certifications. If a comparison lacks reliable competitor facts, compare against a generic alternative such as “doing this manually” and label it as a positioning draft.
Decision rules
- Follow the visitor’s search intent and requested conversion goal; do not force a sales structure onto an informational request.
- Choose one emotional anchor from the pain points and one central outcome from the benefits.
- Map every included feature to a concrete user benefit. Omit features with no clear outcome.
- Keep the product out of the opening problem section so the reader’s situation is established before the pitch.
- Use the primary keyword naturally in the H1, opening copy, one relevant H2, and at least one FAQ answer when provided. Do not use arbitrary density targets.
- Make claims proportional to the evidence supplied. Use placeholders such as
[verified customer quote]where proof is missing. - Prefer short paragraphs, descriptive headings, scannable lists, and direct answers.
Required page flow
Use this order unless the user requests another structure:
- SEO metadata
- Hero and direct-answer block
- Problem
- Solution
- Features and benefits
- Social proof or trust evidence
- Mid-page CTA
- How it works
- Comparison or alternatives
- FAQ
- Trust and risk-reversal signals
- Final CTA
- Internal-link suggestions
The problem section must not mention the product. The hero must state what the product is, who it is for, and the primary outcome in one standalone sentence of roughly 25–40 words. Keep this AEO extraction block factual and free of hype.
Output format
Return Markdown in the exact section order above. Include:
## SEO Metadata
H1: [one H1, normally 6–10 words]
Meta Title: [50–60 characters where practical, keyword-led]
Meta Description: [draft only; hand off to seo-aeo-meta-description-generator when available]
URL Slug: /[short lowercase hyphenated slug]
## Hero
# [H1]
> [standalone definition and audience/outcome sentence]
[sub-headline]
[primary CTA] [secondary CTA]
## Problem
## Solution
## Features and Benefits
| Feature | User outcome |
|---|---|
## Social Proof
## Mid-page CTA
## How It Works
1. **Step** — [short description]
## Comparison or Alternatives
| Dimension | Product | Alternative |
|---|---|---|
## Frequently Asked Questions
**Q: [question]**
A: [standalone answer]
## Trust and Risk Reversal
## Final CTA
## Internal-Link SuggestionsShow full SKILL.md (232 more words)Show less
Quality checks before returning
- Exactly one H1; headings are hierarchical and descriptive.
- The first paragraph explains the offer and audience without unexplained jargon.
- The hero contains one direct-answer block and a clear primary CTA.
- Include at least three useful FAQ entries when context allows; use six only when the audience has six genuine questions. The first FAQ should define the product when relevant.
- FAQ answers are standalone and normally under 50 words; never add FAQ schema for content that is not visible on the page.
- Features are rewritten as outcomes in a table, and every major pain point has a corresponding benefit or explanation.
- Comparison claims are fair and evidence-based; include a dimension where the alternative may be better when applicable.
- Metadata is concise, unique, and free of keyword stuffing. Do not fabricate character-perfect results.
- Suggest internal links only to supplied or clearly named related pages, using descriptive anchors rather than “click here”.
- End with
Assumptions and verification notesonly when placeholders, unsupported claims, or missing inputs remain.
Connected skills
- Receives optional context from
seo-aeo-keyword-researchandseo-aeo-content-cluster. - Hand off the completed page to
seo-aeo-meta-description-generator,seo-aeo-content-quality-auditor,seo-aeo-internal-linking, andseo-aeo-schema-generatorwhen available or requested.
When to Use
Use when creating or improving a conversion-focused product, service, offer, or homepage while preserving clear search and answer-engine structure.
Limitations
- Draft copy cannot validate legal claims, product capabilities, accessibility, performance, or actual conversion results without project-specific review.
© sickn33, 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/seo-aeo-landing-page-writer of sickn33/agentic-awesome-skills.
Open the folder on GitHubat commit b84d35a
Used in 1 other repository
We found 5 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in sickn33/agentic-awesome-skills, which our catalogue first saw on October 7, 2026.
Compare with similar skills
SEO Aeo Landing Page Writer 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| SEO Aeo Landing Page Writer this skillsickn33/agentic-awesome-skills | 47k | 1 repos | ~1.5k | Automated safety check: Pass | MIT | |
| SEO Aeo Landing Page Writerhenryalouf/ruflow | 157 | — | ~1.1k | Automated safety check: Pass | MIT | |
| Landing Page AuditorInfrasity-Labs/dev-gtm-claude-skills | 136 | — | ~6.7k | Automated safety check: Pass | MIT | |
| Landing Pageboraoztunc/skills | 398 | 2 repos | ~1.3k | Automated safety check: Pass | Apache-2.0 | |
| Bio Link DeployerAffitor/affiliate-skills | 701 | — | ~3k | Automated safety check: Pass | MIT | |
| Arabic Copy Localizergrowthack88/growth-marketing-os | 116 | — | ~1k | Automated safety check: Pass | MIT |
Similar skills
Landing Page Auditor
Infrasity-Labs/dev-gtm-claude-skills
Audits any landing or service page across 48 checks in 10 categories for LLM/AI discoverability, GEO readiness, content clarity, schema markup, internal linking, freshness signals, and technical…
Landing Page
boraoztunc/skills
A skill your agent uses when designing or rewriting a high-converting landing page (single-offer page) for SaaS/apps/services.
Bio Link Deployer
Affitor/affiliate-skills
Create a Linktree-style bio link hub page as a single self-contained HTML file.
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…
Content Writer
aaron-he-zhu/aaron-marketing-skills
A skill your agent uses when the user asks to "write SEO content", "draft a blog post / landing page", "update outdated content", or "fix traffic/ranking decay"; two modes — new drafts pages with…
More from sickn33/agentic-awesome-skills
All 1,497 skills in this repoLiuguang Banlan UI
sickn33/agentic-awesome-skills
Implements an interface in one of two named color modes, iridescent white or colorful black, from a parameterized starter that reports measured color intensity.
User Thoughts Memory
sickn33/agentic-awesome-skills
Saves a user's project decisions, rules and preferences into a project-local mdbase so later sessions and other agents can recover the intent.
Using LWC Memory and Graphs
sickn33/agentic-awesome-skills
Keeps project decisions, research and verified results available across coding-agent sessions through LWC memory, a document Wiki graph and a CodeGraph code index.
Find Complementary Founders
sickn33/agentic-awesome-skills
Guides an agent through assessing its own owner for cofounder fit, publishing an approved profile, and ranking complementary profiles other agents published for their owners.
Whatsapp Cloud API
sickn33/agentic-awesome-skills
Integracao com WhatsApp Business Cloud API (Meta). An agent skill from sickn33/agentic-awesome-skills.
Cline Pilot
sickn33/agentic-awesome-skills
Acts as a proxy for the Cline CLI, dispatching coding tasks one at a time, monitoring runs by hard evidence, relaying decisions to you and learning per-project preferences.
Related
Categories
Questions about SEO Aeo Landing Page Writer
What does SEO Aeo Landing Page Writer do?
Writes or improves conversion-focused landing pages for products, services, and offers with practical SEO and AEO structure. SEO Aeo Landing Page Writer is an agent skill from sickn33/agentic-awesome-skills. Writes or improves conversion-focused landing pages for products, services, and offers with practical SEO and AEO structure.
When should I use SEO Aeo Landing Page Writer?
SEO Aeo Landing Page Writer fits situations like: tasks that involve Landing pages; tasks that involve AI search optimization.
How do I install SEO Aeo Landing Page Writer in Claude Code?
Run `npx skills add sickn33/agentic-awesome-skills --skill seo-aeo-landing-page-writer -a claude-code`. Or copy the skill folder (skills/seo-aeo-landing-page-writer in sickn33/agentic-awesome-skills) into .claude/skills/seo-aeo-landing-page-writer in your project. Claude Code loads it when a task matches its description.
How do I install SEO Aeo Landing Page Writer in Codex?
Run `npx skills add sickn33/agentic-awesome-skills --skill seo-aeo-landing-page-writer -a codex`. Or copy the skill folder (skills/seo-aeo-landing-page-writer in sickn33/agentic-awesome-skills) into .agents/skills/seo-aeo-landing-page-writer in your project. Codex loads it when a task matches its description.
Can I use SEO Aeo Landing Page Writer 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 sickn33/agentic-awesome-skills --skill seo-aeo-landing-page-writer -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/seo-aeo-landing-page-writer, .gemini/skills/seo-aeo-landing-page-writer, .github/skills/seo-aeo-landing-page-writer and .opencode/skills/seo-aeo-landing-page-writer in your project.
What does SEO Aeo Landing Page Writer need to run?
SKILL.md names no scripts, command-line tools or credentials: SEO Aeo Landing Page Writer is instructions for the agent only.
Does SEO Aeo Landing Page Writer 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 SEO Aeo Landing Page Writer 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 SEO Aeo Landing Page Writer use?
SEO Aeo Landing Page Writer 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 SEO Aeo Landing Page Writer use?
About 1.5k tokens (SKILL.md is roughly 5.9k 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 SEO Aeo Landing Page Writer?
Skills that share tags, products or a category with SEO Aeo Landing Page Writer: SEO Aeo Landing Page Writer (henryalouf/ruflow, 157 stars), Landing Page Auditor (Infrasity-Labs/dev-gtm-claude-skills, 136 stars), Landing Page (boraoztunc/skills, 398 stars) and Bio Link Deployer (Affitor/affiliate-skills, 701 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains SEO Aeo Landing Page Writer?
sickn33 (a GitHub user) maintains it in sickn33/agentic-awesome-skills, which has 47,405 GitHub stars. The repository holds 1,497 skills in this directory. The repository was last updated on October 9, 2026.
Source: sickn33/agentic-awesome-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.