opencode-skills-collection 4.0.64 → 4.0.65

package/bundled-skills/seo-aeo-keyword-research/SKILL.md

@@ -1,118 +1,339 @@
 ---
 name: seo-aeo-keyword-research
-description: "Researches and prioritises SEO keywords with AEO question queries, difficulty tiers, cannibalization checks, and a content map. Activate when the user wants to find keywords, research search terms, or build a keyword strategy."
+description: "Researches and prioritises keywords from the site context and live search intent, including problem queries, question queries, difficulty tiers, and a content map."
 risk: safe
 source: community
 date_added: "2026-04-01"
 ---
 
-# SEO-AEO Keyword Research
+# Keyword Research Skill
 
-## Overview
+## Description
+Activate this skill when the user wants to research, identify, or
+prioritise keywords for a topic, niche, or website. Trigger phrases
+include: "keyword research", "find keywords for", "what should I
+rank for", "keyword analysis", "best keywords for [topic]",
+"keyword strategy", "what are people searching for about [topic]",
+"SEO keywords for [niche]".
 
-Identifies high-value SEO keywords and AEO question-based queries for a topic. Produces keyword tiers (easy wins to long-term goals), search intent classification, cannibalization checks, and a content production map — all from a single topic input.
+---
+
+## Input Format
+```json
+{
+  "topic": "string — the subject to research keywords for",
+  "business_type": "string — what the business or site does",
+  "target_audience": "string — who the content is for",
+  "content_goal": "rank | convert | educate | all",
+  "location": "string — optional, country or city for local SEO",
+  "intent_focus": "informational | transactional |
+                   commercial | navigational | all",
+  "competitor_urls": ["string — optional, up to 3 competitor URLs
+                       to inform keyword gaps"],
+  "user_keywords": ["string — optional keywords the owner already cares about"],
+  "site_context": "string — optional audit findings, page list, or product description",
+  "research_mode": "browser | api | both | unavailable — default both"
+}
+```
+
+Start by asking the owner which keywords, products, audiences, locations, and business outcomes matter. If they do not know, derive provisional candidates from the site, audit findings, competitor language, and observed search results. Do not silently replace owner-supplied priorities with guessed keywords.
+
+## Live search-intent research
+
+Use both browser research and available search/keyword APIs when the environment supports them. Prefer APIs for repeatable data and browser inspection for actual result-page intent, related questions, snippets, and current wording. If only one is available, state which source was used. If neither is available, perform semantic research only and mark volume, difficulty, rankings, and SERP observations as unverified.
+
+For each important query, record:
+
+- the exact query and market/device when known;
+- dominant result intent: learn, compare, evaluate, buy, navigate, or troubleshoot;
+- the problems and questions visible in results, related searches, and snippets;
+- the content formats ranking: landing page, guide, comparison, tool, forum, video, or documentation;
+- the conversion opportunity and the page that should own the query;
+- the date/source and confidence level.
+
+Prioritize problem-related queries that the product can genuinely solve. Search intent outranks attractive but irrelevant volume.
+
+---
+
+## Difficulty & Volume Rubric
+
+**Important:** This skill estimates difficulty and volume based on
+semantic analysis and competitive signals. It does not connect to
+live data APIs. All figures are directional estimates, not
+verified data. Always validate with a live tool
+(Ahrefs, SEMrush, Google Keyword Planner) before committing
+to a full content strategy.
+
+### Difficulty Scale
+
+| Score  | Label       | Meaning                                              |
+|--------|-------------|------------------------------------------------------|
+| 0–20   | Easy        | Low competition, newer or niche keyword              |
+| 21–40  | Moderate    | Some established content exists, beatable with quality |
+| 41–60  | Competitive | Strong content exists, needs solid authority         |
+| 61–80  | Hard        | Dominated by high-authority sites                    |
+| 81–100 | Very Hard   | Reserved for the biggest players — avoid early on   |
+
+### Volume Scale (Estimated Monthly Searches)
+
+| Label       | Range              |
+|-------------|--------------------|
+| Very High   | 100,000+           |
+| High        | 10,000–99,999      |
+| Medium      | 1,000–9,999        |
+| Low         | 100–999            |
+| Very Low    | Under 100          |
+
+### CPC Context
+
+CPC (Cost Per Click) signals commercial value even for
+organic content. Use it to prioritise keywords where
+advertisers are spending — this means the intent is
+likely transactional and conversions are valuable.
+
+| CPC Range   | Signal                                               |
+|-------------|------------------------------------------------------|
+| $0–$1       | Low commercial value, good for awareness content     |
+| $1–$5       | Moderate value, mix of info and commercial intent    |
+| $5–$15      | High commercial value, strong conversion potential   |
+| $15+        | Very high value — transactional, competitive space  |
+
+---
+
+## Output Structure
+
+The skill must always produce output in this exact format:
+```markdown
+# Keyword Research Report
+
+**Topic:** [topic]
+**Business Type:** [business_type]
+**Target Audience:** [target_audience]
+**Content Goal:** [content_goal]
+**Location:** [location or "Global"]
+**Note:** All volume and difficulty figures are estimates.
+Validate with a live keyword tool before final decisions.
+
+---
+
+## Seed Keywords
+
+Core terms that define the topic's search territory:
+
+| Seed Keyword         | Est. Volume | Difficulty | CPC Est. | Intent          |
+|----------------------|-------------|------------|----------|-----------------|
+| [keyword]            | [label]     | [score]    | [$x]     | [intent type]   |
+| [keyword]            | [label]     | [score]    | [$x]     | [intent type]   |
+| [keyword]            | [label]     | [score]    | [$x]     | [intent type]   |
+
+---
+
+## Priority Keyword Tiers
+
+### 🟢 Tier 1 — Target First (High Value, Achievable)
+Low-to-moderate difficulty. Should anchor your first
+wave of content.
+
+| Keyword              | Est. Volume | Difficulty | CPC Est. | Intent        | Content Type to Create  |
+|----------------------|-------------|------------|----------|---------------|-------------------------|
+| [keyword]            | [label]     | [score]    | [$x]     | [intent]      | [landing page / blog]   |
+| [keyword]            | [label]     | [score]    | [$x]     | [intent]      | [content type]          |
+| [keyword]            | [label]     | [score]    | [$x]     | [intent]      | [content type]          |
+
+---
+
+### 🟡 Tier 2 — Build Toward (Medium Difficulty)
+Competitive but winnable with topical authority.
+Target after Tier 1 content is live.
+
+| Keyword              | Est. Volume | Difficulty | CPC Est. | Intent        | Content Type to Create  |
+|----------------------|-------------|------------|----------|---------------|-------------------------|
+| [keyword]            | [label]     | [score]    | [$x]     | [intent]      | [content type]          |
+| [keyword]            | [label]     | [score]    | [$x]     | [intent]      | [content type]          |
 
-Part of the [SEO-AEO Engine](https://github.com/mrprewsh/seo-aeo-engine) — an open-source AI-powered content growth system.
+---
+
+### 🔴 Tier 3 — Long-Term Goals (High Difficulty)
+Dominated by high-authority sites. Do not target these
+until significant topical authority is established.
+
+| Keyword              | Est. Volume | Difficulty | CPC Est. | Intent        | Notes                   |
+|----------------------|-------------|------------|----------|---------------|-------------------------|
+| [keyword]            | [label]     | [score]    | [$x]     | [intent]      | [why it's hard]         |
+
+---
+
+## Long-Tail Keywords
+
+Lower volume, lower difficulty, higher conversion rate.
+These are your fastest wins.
+
+| Long-Tail Keyword                    | Est. Volume | Difficulty | Intent        | Best For              |
+|--------------------------------------|-------------|------------|---------------|-----------------------|
+| [keyword]                            | [label]     | [score]    | [intent]      | [blog / landing page] |
+| [keyword]                            | [label]     | [score]    | [intent]      | [content type]        |
+| [keyword]                            | [label]     | [score]    | [intent]      | [content type]        |
+| [keyword]                            | [label]     | [score]    | [intent]      | [content type]        |
+| [keyword]                            | [label]     | [score]    | [intent]      | [content type]        |
+
+---
+
+## AEO Keywords
+
+Question-based and conversational keywords that AI engines
+surface in direct answers, featured snippets, and
+People Also Ask boxes.
 
-## When to Use This Skill
+| AEO Keyword / Question                         | Est. Volume | Intent        | Answer Format to Use   |
+|------------------------------------------------|-------------|---------------|------------------------|
+| What is [topic]?                               | [label]     | informational | Definition sentence    |
+| How does [topic] work?                         | [label]     | informational | Numbered steps         |
+| What is the best [topic] for [audience]?       | [label]     | commercial    | Comparison table       |
+| How much does [topic] cost?                    | [label]     | transactional | Direct number + range  |
+| [topic] vs [alternative] — which is better?   | [label]     | commercial    | Comparison block       |
+| Is [topic] worth it?                           | [label]     | commercial    | FAQ answer block       |
+| [Common question your audience asks]           | [label]     | [intent]      | [format]               |
+| [Common question your audience asks]           | [label]     | [intent]      | [format]               |
 
-- Use when you need to build a keyword strategy for a new topic or niche
-- Use when you want to find AEO question queries for AI engine citation
-- Use when you need to prioritise which keywords to target first
-- Use when you want to check for keyword cannibalization before writing content
+---
+
+## LSI and Semantic Keywords
+
+Related terms that reinforce topical authority.
+Use these naturally throughout content —
+do not force them as primary targets.
+
+- [LSI term 1]
+- [LSI term 2]
+- [LSI term 3]
+- [LSI term 4]
+- [LSI term 5]
+- [LSI term 6]
+
+---
 
-## How It Works
+## Keywords to Avoid
 
-### Step 1: Extract Seed Keywords
-Identify 3–5 core terms that anchor the topic's search territory. Go beyond the obvious head term to include adjacent terms the audience actually uses.
+These keywords are flagged as high-risk or low-ROI
+for this topic and audience:
 
-### Step 2: Expand Into Tiers
-Sort all keywords into three tiers:
-- **Tier 1** — Low-to-moderate difficulty. Target first.
-- **Tier 2** — Medium difficulty. Build toward after Tier 1 content is live.
-- **Tier 3** — High difficulty. Long-term goals only.
+| Keyword              | Reason to Avoid                                        |
+|----------------------|--------------------------------------------------------|
+| [keyword]            | Wrong intent — attracts audience not looking to convert|
+| [keyword]            | Too broad — dominated by global brands                 |
+| [keyword]            | Cannibalises [other keyword] — similar enough to split traffic |
+| [keyword]            | Seasonal — only relevant [month/period]                |
 
-### Step 3: Generate AEO Keywords
-Produce question-based keywords that AI engines surface in direct answers and People Also Ask boxes. For each AEO keyword, specify the answer format to use (definition sentence, numbered steps, comparison table, direct number).
+---
 
-### Step 4: Run Cannibalization Check
-Flag any two keywords similar enough to split traffic if targeted on separate pages. Recommend which page should own which term.
+## Cannibalization Check
 
-### Step 5: Build Content Map
-Recommend content type and production order for all Tier 1 and Tier 2 keywords.
+Keywords with enough overlap that two pages targeting
+them would compete against each other:
 
-## Examples
+| Keyword A            | Keyword B            | Risk Level | Resolution                          |
+|----------------------|----------------------|------------|-------------------------------------|
+| [keyword]            | [keyword]            | High/Med   | [which page should own which term]  |
 
-### Example 1: SaaS Product
-Input: topic = "remote project management software"
-audience = "engineering managers and startup founders"
-goal = "convert"
-Output:
-Tier 1 Keywords:
+If none detected: ✅ No cannibalization risks found.
 
-"remote project management software" | Medium volume | Difficulty: 38
-"project management tool remote teams" | Low volume | Difficulty: 29
+---
 
-AEO Keywords:
+## Keyword → Content Map
 
-"What is the best project management software for remote teams?"
-→ Answer format: Comparison table
-"How does remote project management work?"
-→ Answer format: Numbered steps
+Recommended content to create based on this research,
+in production order:
 
-Content Map:
+| Priority | Content Title                    | Target Keyword    | Content Type     | Goal              |
+|----------|----------------------------------|-------------------|------------------|-------------------|
+| 1        | [title]                          | [keyword]         | Landing Page     | Convert           |
+| 2        | [title]                          | [keyword]         | Pillar Blog Post | Rank + Authority  |
+| 3        | [title]                          | [keyword]         | Cluster Article  | Topical Depth     |
+| 4        | [title]                          | [keyword]         | Cluster Article  | AEO / Snippet     |
+| 5        | [title]                          | [keyword]         | FAQ Page         | AEO / Long-tail   |
 
-Landing page → "remote project management software"
-Pillar blog → "complete guide to remote project management"
-Cluster article → "how to manage remote engineering teams"
+---
 
+## Quick Wins Summary
 
-### Example 2: Fintech App
-Input: topic = "automated budgeting app"
-audience = "millennials managing personal finances"
-goal = "all"
-Output:
-Tier 1 Keywords:
+The 3 keywords to act on immediately:
 
-"automated budgeting app" | Medium volume | Difficulty: 33
-"automatic savings app" | Low volume | Difficulty: 24
+1. **[keyword]** — [one sentence on why this is the best
+   first target]
+2. **[keyword]** — [one sentence on why]
+3. **[keyword]** — [one sentence on why]
+```
 
-AEO Keywords:
+## Foundational Content Plan
 
-"What is the best budgeting app for millennials?"
-→ Answer format: Comparison table
-"How does automated budgeting work?"
-→ Answer format: Numbered steps
+Recommend between 5 and 10 foundational pages, defaulting to 10 when the topic has enough distinct intent. Include the landing page when it is a target page, then assign each page a problem, query, intent, conversion path, supporting evidence, and internal-link targets.
 
+| # | Page / Article | Primary Query | Problem Solved | Intent | Conversion Path | Evidence |
+|---|----------------|---------------|----------------|--------|-----------------|----------|
+| 1 | [title] | [query] | [problem] | [intent] | [CTA/product page] | [source/confidence] |
 
-## Best Practices
+Do not fill the table with near-duplicates to reach ten. If fewer than five distinct intents are defensible, explain why and ask whether the owner prefers a smaller foundation or broader adjacent topics.
 
-- ✅ **Do:** Target Tier 1 keywords first — build authority before going after competitive terms
-- ✅ **Do:** Use AEO keywords in FAQ sections and definition blocks for AI engine citation
-- ✅ **Do:** Validate estimated volume and difficulty with a live tool (Ahrefs, SEMrush) before committing
-- ❌ **Don't:** Target two keywords on the same page if cannibalization is flagged
-- ❌ **Don't:** Use volume as the only prioritisation signal — difficulty and intent matter more
+## Search-Intent Evidence
 
-## Common Pitfalls
+| Query | Market / Date | Dominant SERP Intent | Ranking Formats | User Problem | Source | Confidence |
+|-------|---------------|----------------------|-----------------|--------------|--------|------------|
+| [query] | [market/date] | [intent] | [formats] | [problem] | [browser/API/semantic] | High/Med/Low |
 
-- **Problem:** High-volume keyword chosen but impossible to rank for early on
-  **Solution:** Always cross-check volume with difficulty. Tier 1 should have difficulty under 45.
+---
 
-- **Problem:** AEO keywords ignored in favour of traditional search terms
-  **Solution:** AEO keywords drive AI engine citation — include at least 5 in every research run.
+## Execution Steps
+
+1. Parse `topic`, `business_type`, `site_context`, and any
+   `user_keywords` together to define
+   the full semantic territory — not just the obvious
+   head term but adjacent terms the audience uses
+2. Generate seed keywords — 3–5 core terms that
+   anchor the topic
+3. Expand each seed keyword into long-tail variations
+   using question formats, modifier patterns
+   ("best", "how to", "for [audience]", "vs"),
+   and location modifiers if `location` is provided
+4. Generate AEO keyword list — convert the most common
+   audience questions into direct-answer keyword targets
+5. Generate LSI terms — identify semantically related
+   vocabulary that reinforces topical authority
+   without targeting directly
+6. If live browser or API research is available, collect
+   current search-intent evidence before estimating difficulty.
+   Base any remaining estimate on
+   keyword length, specificity, and likely
+   competitive landscape
+7. Estimate volume using the volume scale —
+   shorter, broader terms get higher volume labels;
+   longer, more specific terms get lower
+8. Assign intent category to every keyword
+9. Sort all keywords into Tier 1, 2, and 3
+   based on difficulty and estimated volume
+10. Run cannibalization check — flag any two keywords
+    that are similar enough to split traffic if
+    targeted on separate pages
+11. Build Keywords to Avoid list — flag wrong-intent,
+    too-broad, cannibalistic, and seasonal keywords
+12. Build the Keyword → Content Map — recommend the landing page,
+    5–10 foundational pages (default 10), supporting articles,
+    and production order. Every page must own a distinct intent.
+13. Mark which keyword choices require owner confirmation before
+    content production and which are safe provisional fallbacks.
+14. Verify keyword choices against the observed result pages, related searches, and the business context. Treat any difficulty estimate as directional unless it comes from an identified data source; do not present a heuristic as measured search volume or competition.
 
-## Related Skills
+---
 
-- `@seo-aeo-content-cluster` — uses keyword research output to build topic cluster
-- `@seo-aeo-landing-page-writer` — consumes primary keyword to generate landing page
-- `@seo-aeo-blog-writer` — uses secondary keywords for cluster article targeting
+## Connected Skills
+- Receives output from: orchestrator workflow input
+- Feeds output to: `seo-aeo-content-cluster`,
+  `seo-aeo-landing-page-writer`, `seo-aeo-blog-writer`,
+  `seo-aeo-meta-description-generator`
 
-## Additional Resources
+## When to Use
 
-- [SEO-AEO Engine Repository](https://github.com/mrprewsh/seo-aeo-engine)
-- [Full Keyword Research SKILL.md](https://github.com/mrprewsh/seo-aeo-engine/blob/main/.agent/skills/keyword-research/SKILL.md)
+Use when selecting target queries, understanding search intent, or turning a business goal into a prioritised content map.
 
 ## Limitations
-- Use this skill only when the task clearly matches the scope described above.
-- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
-- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
+
+- Search intent and competition change over time; directional research must be validated against current result pages and available first-party data.

package/bundled-skills/seo-aeo-landing-page-writer/SKILL.md

@@ -1,103 +1,136 @@
 ---
 name: seo-aeo-landing-page-writer
-description: "Writes complete, structured landing pages optimized for SEO ranking, AEO citation, and visitor conversion. Activate when the user wants to write or generate a landing page for a product, service, or offer."
+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"
 ---
 
-# SEO-AEO Landing Page Writer
-
-## Overview
-
-Generates a full, publish-ready landing page following a defined section order with SEO heading structure, AEO extraction blocks, FAQ section, comparison table, social proof, and conversion-focused CTAs. Every section serves a specific purpose in a narrative arc that moves the visitor from awareness to action.
-
-Part of the [SEO-AEO Engine](https://github.com/mrprewsh/seo-aeo-engine).
-
-## When to Use This Skill
-
-- Use when building a landing page for a new product or service
-- Use when an existing landing page needs a full SEO and AEO rewrite
-- Use when you need a page that can be cited by AI engines like Perplexity or ChatGPT
-- Use when you want conversion copy that leads with pain before pitching the product
 
+# 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.
+
+```json
+{
+  "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:
+
+1. SEO metadata
+2. Hero and direct-answer block
+3. Problem
+4. Solution
+5. Features and benefits
+6. Social proof or trust evidence
+7. Mid-page CTA
+8. How it works
+9. Comparison or alternatives
+10. FAQ
+11. Trust and risk-reversal signals
+12. Final CTA
+13. 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:
+
+```markdown
+## 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]
 
-### Step 1: Map Inputs
-Extract product name, audience, primary keyword, pain points, features, benefits, USPs, social proof, and CTAs. Map every feature to a user outcome before writing any copy.
-
-### Step 2: Write AEO Extraction Sentence
-Write one 25–40 word sentence that answers "What is [product]?" — standalone, no jargon, placed in a blockquote immediately after the H1. This is the sentence AI engines extract.
-
-### Step 3: Follow the Narrative Arc
-Write sections in this exact order:
-1. Hero — H1 + AEO sentence + CTA
-2. Problem — audience pain, no product mention yet
-3. Solution — introduce product as the answer
-4. Features as Benefits — table format
-5. Social Proof — testimonials, logos, stats
-6. Mid-page CTA
-7. How It Works — numbered steps
-8. Comparison — table with honest competitor comparison
-9. FAQ — minimum 6 entries, each under 50 words
-10. Trust Signals
-11. Final CTA
-
-### Step 4: Run SEO and AEO Checklists
-Verify keyword placement, heading hierarchy, FAQ count, AEO block presence, and meta description placeholder before outputting.
+## Comparison or Alternatives
+| Dimension | Product | Alternative |
+|---|---|---|
 
-## Examples
+## Frequently Asked Questions
+**Q: [question]**
+A: [standalone answer]
 
-### Example 1: Hero Section Output
-Ship Faster With Your Remote Team
+## Trust and Risk Reversal
+## Final CTA
+## Internal-Link Suggestions
+```
 
-Syncro is a remote-first project management platform that helps
-distributed engineering teams track work, communicate
-asynchronously, and ship without the chaos of email and
-scattered spreadsheets.
+## Quality checks before returning
 
-[Start Free Trial]  [See How It Works]
-"4,000+ remote teams" · "40% fewer status meetings" · "4.8/5 on G2"
+- 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 notes` only when placeholders, unsupported claims, or missing inputs remain.
 
-### Example 2: FAQ Section Output
-Q: What is Syncro?
-A: Syncro is a remote-first project management platform for
-distributed engineering teams. It centralises task tracking,
-async communication, and sprint planning in one tool.
-Q: How much does Syncro cost?
-A: Syncro offers a flat-rate plan at $49/month for unlimited
-users. A 14-day free trial is available — no credit card required.
+## Connected skills
 
-## Best Practices
+- Receives optional context from `seo-aeo-keyword-research` and `seo-aeo-content-cluster`.
+- Hand off the completed page to `seo-aeo-meta-description-generator`, `seo-aeo-content-quality-auditor`, `seo-aeo-internal-linking`, and `seo-aeo-schema-generator` when available or requested.
 
-- ✅ **Do:** Write the problem section before mentioning the product — empathy first
-- ✅ **Do:** Place the AEO extraction sentence in a blockquote immediately after H1
-- ✅ **Do:** Write FAQ answers as standalone — each must make sense without context
-- ✅ **Do:** Include at least one honest point in the comparison table where the alternative wins
-- ❌ **Don't:** Use "revolutionary", "game-changing", or "best-in-class" anywhere
-- ❌ **Don't:** Use "Submit" or "Click Here" as CTA button text
-- ❌ **Don't:** Write paragraphs longer than 4 lines
+## When to Use
 
-## Common Pitfalls
-
-- **Problem:** Product mentioned in the pain section
-  **Solution:** The pain section exists to build empathy. Save the product introduction for the solution section.
-
-- **Problem:** FAQ answers are too long to be extracted by AI engines
-  **Solution:** Every FAQ answer must be under 50 words and self-contained.
-
-## Related Skills
-
-- `@seo-aeo-keyword-research` — provides the primary keyword and AEO queries
-- `@seo-aeo-meta-description-generator` — writes title and meta description from page output
-- `@seo-aeo-content-quality-auditor` — audits the completed landing page
-
-## Additional Resources
-
-- [SEO-AEO Engine Repository](https://github.com/mrprewsh/seo-aeo-engine)
-- [Full Landing Page Writer SKILL.md](https://github.com/mrprewsh/seo-aeo-engine/blob/main/.agent/skills/landing-page-writer/SKILL.md)
+Use when creating or improving a conversion-focused product, service, offer, or homepage while preserving clear search and answer-engine structure.
 
 ## Limitations
-- Use this skill only when the task clearly matches the scope described above.
-- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
-- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
+
+- Draft copy cannot validate legal claims, product capabilities, accessibility, performance, or actual conversion results without project-specific review.