seo-aeo-content-cluster
Builds a topical authority map with a pillar page, prioritised cluster articles, content types, internal link map, and content gap analysis. Activate when the user wants to build a content cluster, topic map, or content strategy.
- License 许可
- MIT
- 最近更新
- 2026-11-10
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- seo-aeo-content-cluster
- risk
- safe
- source
- community
- date_added
- 2026-04-01
- description
- Builds a topical authority map with a pillar page, prioritised cluster articles, content types, internal link map, and content gap analysis. Activate when the user wants to build a content cluster, topic map, or content strategy.
03 SKILL.md 正文
SEO-AEO Content Cluster
Overview
Maps out a complete topical authority structure around a pillar keyword. Produces a pillar page definition, 8–15 cluster articles sorted into Priority 1/2/3 tiers, a content type for each, an internal link map, and a content gap analysis identifying AEO opportunities competitors are missing.
Part of the SEO-AEO Engine.
When to Use This Skill
- Use when building topical authority around a new subject
- Use when you need to know what to write next to support a pillar page
- Use when planning a content calendar for a niche
- Use when you want to identify AEO content gaps competitors are missing
How It Works
Step 1: Define the Pillar Page
Set the primary keyword, target audience, and word count target (2500–4000 words) for the pillar page that anchors the cluster.
Step 2: Generate Cluster Articles
Produce 8–15 subtopics sorted into three priority tiers:
- Priority 1 — High volume, clear intent. Write these first.
- Priority 2 — Medium volume, long-tail focus. Write second.
- Priority 3 — Low volume, high conversion intent. Write last.
Assign each article a unique keyword, content type, search intent, and link map.
Step 3: Build Internal Link Map
Every cluster article must link back to the pillar page. No orphan articles. Show the full tree of relationships.
Step 4: Run Content Gap Analysis
Identify angles that competitors likely miss — especially question-based AEO opportunities that AI engines commonly surface.
Examples
Example: Automated Budgeting Cluster
Pillar: The Complete Guide to Automated Budgeting Priority 1:
How to Build a Budget That Actually Works | how-to guide Best Budgeting Apps Compared | comparison What Is Zero-Based Budgeting? | explainer ← AEO priority
Priority 2: 4. How to Automate Your Savings in 3 Steps | how-to guide 5. Budgeting for Millennials: What Nobody Tells You | opinion Link Map: Pillar ← Article 1, 2, 3, 4, 5 Article 1 ↔ Article 4 Article 2 → Article 3 AEO Priority: ★ Article 3 — "What Is" format has highest AI extraction probability ★ Article 2 — comparison table will be lifted for product queries
Best Practices
- ✅ Do: Assign every cluster article a unique target keyword — no overlap
- ✅ Do: Include at least one FAQ page and one comparison article in every cluster
- ✅ Do: Flag the 2 highest AEO-opportunity articles for priority writing
- ❌ Don't: Let any article become an orphan — every article links to at least one other
- ❌ Don't: Target the same keyword on both the pillar and a cluster article
Common Pitfalls
-
Problem: Cluster articles all target similar keywords and cannibalise each other Solution: Run a uniqueness check — every article needs a distinct keyword with no semantic overlap.
-
Problem: No AEO content in the cluster Solution: At least 2 articles must be structured as direct-answer pages (FAQ or "What Is" explainer).
Related Skills
@seo-aeo-keyword-research— provides the keyword foundation for the cluster@seo-aeo-blog-writer— writes the Priority 1 cluster articles@seo-aeo-internal-linking— builds the detailed link map from cluster output
Additional Resources
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.
04 同仓库更多 Skills
vercel-sandbox
Run agent-browser + Chrome inside Vercel Sandbox microVMs for browser automation from any Vercel-deployed app. Use when the user needs browser automation in a Vercel app (Next.js, SvelteKit, Nuxt, Remix, Astro, etc.), wants to run headless Chrome without binary size limits, needs persistent browser sessions across commands, or wants ephemeral isolated browser environments. Triggers include "Vercel Sandbox browser", "microVM Chrome", "agent-browser in sandbox", "browser automation on Vercel", or any task requiring Chrome in a Vercel Sandbox.
slack
Interact with Slack workspaces using browser automation. Use when the user needs to check unread channels, navigate Slack, send messages, extract data, find information, search conversations, or automate any Slack task. Triggers include "check my Slack", "what channels have unreads", "send a message to", "search Slack for", "extract from Slack", "find who said", or any task requiring programmatic Slack interaction.
electron
Automate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) using agent-browser via Chrome DevTools Protocol. Use when the user needs to interact with an Electron app, automate a desktop app, connect to a running app, control a native app, or test an Electron application. Triggers include "automate Slack app", "control VS Code", "interact with Discord app", "test this Electron app", "connect to desktop app", or any task requiring automation of a native Electron application.
dogfood
Systematically explore and test a web application to find bugs, UX issues, and other problems. Use when asked to "dogfood", "QA", "exploratory test", "find issues", "bug hunt", "test this app/site/platform", or review the quality of a web application. Produces a structured report with full reproduction evidence -- step-by-step screenshots, repro videos, and detailed repro steps for every issue -- so findings can be handed directly to the responsible teams.
agent-browser
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.
shadcn
Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI, including chat interfaces. Provides project context, component docs, and usage examples. Applies when working with shadcn/ui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for "shadcn init", "create an app with --preset", "switch to --preset", and for building a design system or applying a DESIGN.md or brand spec to shadcn/ui.