SEO Keyword Clustering
AgriciDaniel/claude-seo
Clusters keywords by how much their search results overlap and designs a hub-and-spoke content plan with an internal link matrix and an interactive cluster map.
Map 50-200+ keywords into topical clusters for SEO domination.
$ npx skills add Affitor/affiliate-skills --skill keyword-cluster-architect -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Affitor/affiliate-skills keyword-cluster-architect --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/Affitor/affiliate-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/blog/keyword-cluster-architect .claude/skills/keyword-cluster-architect && 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 "keyword-cluster-architect" agent skill from https://github.com/Affitor/affiliate-skills/tree/main/skills/blog/keyword-cluster-architect into .claude/skills/keyword-cluster-architect/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "keyword-cluster-architect", 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/Affitor/affiliate-skills/tree/main/skills/blog/keyword-cluster-architectType 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 Affitor/affiliate-skills --skill keyword-cluster-architect -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Affitor/affiliate-skills keyword-cluster-architect --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Affitor/affiliate-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/blog/keyword-cluster-architect .agents/skills/keyword-cluster-architect && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "keyword-cluster-architect" agent skill from https://github.com/Affitor/affiliate-skills/tree/main/skills/blog/keyword-cluster-architect into .agents/skills/keyword-cluster-architect/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "keyword-cluster-architect", 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 Affitor/affiliate-skills --skill keyword-cluster-architect -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Affitor/affiliate-skills keyword-cluster-architect --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Affitor/affiliate-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/blog/keyword-cluster-architect .cursor/skills/keyword-cluster-architect && 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 "keyword-cluster-architect" agent skill from https://github.com/Affitor/affiliate-skills/tree/main/skills/blog/keyword-cluster-architect into .cursor/skills/keyword-cluster-architect/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "keyword-cluster-architect", 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/Affitor/affiliate-skills.git --path skills/blog/keyword-cluster-architect--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 Affitor/affiliate-skills --skill keyword-cluster-architect -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Affitor/affiliate-skills keyword-cluster-architect --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Affitor/affiliate-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/blog/keyword-cluster-architect .gemini/skills/keyword-cluster-architect && 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 "keyword-cluster-architect" agent skill from https://github.com/Affitor/affiliate-skills/tree/main/skills/blog/keyword-cluster-architect into .gemini/skills/keyword-cluster-architect/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "keyword-cluster-architect", 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 Affitor/affiliate-skills keyword-cluster-architectInstalls 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 Affitor/affiliate-skills --skill keyword-cluster-architect -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Affitor/affiliate-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/blog/keyword-cluster-architect .github/skills/keyword-cluster-architect && 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 "keyword-cluster-architect" agent skill from https://github.com/Affitor/affiliate-skills/tree/main/skills/blog/keyword-cluster-architect into .github/skills/keyword-cluster-architect/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "keyword-cluster-architect", 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 Affitor/affiliate-skills --skill keyword-cluster-architect -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Affitor/affiliate-skills keyword-cluster-architect --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Affitor/affiliate-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/blog/keyword-cluster-architect .opencode/skills/keyword-cluster-architect && 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 "keyword-cluster-architect" agent skill from https://github.com/Affitor/affiliate-skills/tree/main/skills/blog/keyword-cluster-architect into .opencode/skills/keyword-cluster-architect/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "keyword-cluster-architect", 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.
keyword-cluster-architectMap 50-200+ keywords into topical clusters for SEO domination.
Keyword Cluster Architect is an agent skill from Affitor/affiliate-skills. Map 50-200+ keywords into topical clusters for SEO domination. Build content roadmaps for topical authority. Triggers on: "keyword research", "keyword clustering", "topical authority", "keyword map", "keyword strategy", "content roadmap for SEO", "keyword grouping", "topic clusters", "SEO keyword plan", "map my keywords", "keyword cluster", "hub and spoke content", "build topical authority", "SEO content plan", "keyword universe".
Its SKILL.md is about 2.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts. Compatibility notes: Claude Code, ChatGPT, Gemini CLI, Cursor, Windsurf, OpenClaw, any AI agent
It sits in Marketing & SEO, covering Keyword research and Content strategy. The repository describes itself as: 50 AI agent skills for affiliate marketing. Research trending content, write data-backed posts, generate infographics, build landing pages, deploy — full flywheel with social… The licence is MIT.
6 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit e43bfae. It shows what the files ask for, not the result of running them.
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.
No scripts in the folder and no shell commands in SKILL.md (its code samples are yaml).
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Claude Code, ChatGPT, Gemini CLI, Cursor, Windsurf, OpenClaw, any AI agent
From compatibility in the SKILL.md frontmatter.
Keyword Cluster Architect loads about 2.4k tokens when it runs. Until then it costs about 115 tokens; SKILL.md has 741 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.
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.
The full file from Affitor/affiliate-skills at commit e43bfae, republished under its MIT licence (© Affitor). 741 words, ~2,376 tokens.
.claude/skills/keyword-cluster-architect/SKILL.md (or your agent's skills folder).Map 50-200+ keywords into topical clusters grouped by search intent. Build a content roadmap for dominating a topic with hub-and-spoke architecture. Google rewards topical authority — this skill builds the strategic map that tells you exactly what content to create and in what order.
S3: Blog & SEO — This is the strategic planning layer FOR blog content. Before writing individual posts, you need a map of the entire keyword landscape organized into clusters.
affiliate-blog-builder — to know WHICH articles to writemonopoly-niche-finder — to map the keyword universe for the winning nicheniche: string # REQUIRED — the topic to cluster
# e.g., "AI video tools", "email marketing for SaaS"
seed_keywords: string[] # OPTIONAL — starting keywords to expand from
# Default: auto-generated from niche
depth: string # OPTIONAL — "quick" (50 keywords) | "standard" (100) | "deep" (200+)
# Default: "standard"
affiliate_products: string[] # OPTIONAL — products you promote (to prioritize commercial keywords)
# Default: noneChaining from S1 monopoly-niche-finder: Use monopoly_niche.intersection as the niche input.
If not provided, generate 5-10 seed keywords from the niche:
For each seed, use web_search to discover related keywords:
"[seed keyword]" — note related searches, People Also Ask"[seed keyword] guide" OR "[seed keyword] tutorial" — informational variants"best [seed keyword]" OR "[seed keyword] review" — commercial variantsCollect 50-200+ unique keywords depending on depth.
Read shared/references/seo-strategy.md for clustering methodology.
Classify each keyword:
Group keywords that share the same search intent (would be answered by the same page):
Cluster: "[Main Topic]"
Type: [I/C/T]
Hub keyword: [highest volume keyword]
Supporting keywords:
- [keyword 1] — [est. volume]
- [keyword 2] — [est. volume]
Content type: [blog post / comparison / review / tutorial / landing page]
Priority: [1-5 based on volume × intent × competition]Organize clusters into a hub-and-spoke map:
output_schema_version: "1.0.0"
keyword_clusters:
niche: string
total_keywords: number
total_clusters: number
hub:
keyword: string
cluster_name: string
content_type: string
priority: number
clusters:
- name: string
intent: string # "informational" | "commercial" | "transactional"
hub_keyword: string
keywords: string[]
content_type: string # "blog" | "comparison" | "review" | "tutorial" | "landing"
priority: number # 1-5
estimated_volume: string
content_roadmap:
total_articles: number
publishing_cadence: string
priority_order: string[] # Cluster names in order to write
target_keywords: string[] # Flat list of all keywords for chaining
chain_metadata:
skill_slug: "keyword-cluster-architect"
stage: "blog"
timestamp: string
suggested_next:
- "affiliate-blog-builder"
- "content-moat-calculator"
- "comparison-post-writer"
- "landing-page-creator"## Keyword Cluster Map: [Niche]
### Overview
- **Total keywords:** XXX
- **Clusters:** XX
- **Hub topic:** [main hub]
- **Content pieces needed:** XX articles
### Hub & Spoke Map [HUB: Main Topic]
/ | | \
[Spoke] [Spoke] [Spoke] [Spoke]
| | | |
[Sub] [Sub] [Sub] [Sub]
### Clusters by Priority
#### Priority 1: [Cluster Name] (Commercial Intent)
- **Hub keyword:** [keyword] — [volume]
- **Content type:** [comparison / review]
- **Keywords:** [list]
- **Article idea:** [specific title]
#### Priority 2: [Cluster Name] (Informational Intent)
[same structure]
[Continue for all clusters]
### Content Roadmap
| Week | Cluster | Article | Intent | Priority |
|---|---|---|---|---|
| 1 | [cluster] | [title] | C | 1 |
| 2 | [cluster] | [title] | C | 1 |
| 3 | [cluster] | [title] | I | 2 |
### Next Steps
- Run `content-moat-calculator` to estimate effort for topical authority
- Run `affiliate-blog-builder` for Priority 1 articles
- Run `comparison-post-writer` for commercial clustersmonopoly-niche-finder first."Example 1: "Map keywords for AI video tools" → Seeds: "best AI video tools", "AI video generator", "HeyGen review". Expand to 100+ keywords. Cluster: "AI video reviews" (C), "how to make AI videos" (I), "AI video pricing" (T), "AI video vs traditional" (C). Hub: "Best AI Video Tools 2025".
Example 2: "Keyword strategy for my affiliate blog about email marketing" → Deep keyword research. Clusters: "email marketing platforms" (C), "email automation tutorials" (I), "email marketing pricing comparison" (T), "email deliverability guides" (I).
Example 3: "Plan my content roadmap" (after monopoly-niche-finder) → Pick up niche from chain. Map 100+ keywords in that intersection niche. Prioritize clusters by revenue potential.
affiliate-blog-builder (S3) — which articles to write and target keywordscomparison-post-writer (S3) — commercial clusters become comparison articlescontent-moat-calculator (S3) — keyword count informs moat estimationlanding-page-creator (S4) — transactional clusters become landing pagesinternal-linking-optimizer (S6) — cluster structure defines link architecturemonopoly-niche-finder (S1) — niche to cluster keywords forcontent-pillar-atomizer (S2) — content pillars suggest keyword areasseo-audit (S6) — current ranking data reveals keyword gapsseo-audit (S6) reveals ranking gaps in existing clusters → add keywords and new content to fill gapsBefore delivering output, verify:
Any NO → rewrite before delivering.
shared/references/seo-strategy.md — Topical authority, clustering methodology, hub-and-spokeshared/references/affiliate-glossary.md — Terminologyshared/references/flywheel-connections.md — Master connection map© Affitor, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in skills/blog/keyword-cluster-architect of Affitor/affiliate-skills.
Open the folder on GitHubat commit e43bfae
Keyword Cluster Architect 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 |
|---|---|---|---|---|---|---|
| Keyword Cluster Architect this skillAffitor/affiliate-skills | 700 | — | ~2.4k | Automated safety check: Pass | MIT | |
| SEO Keyword ClusteringAgriciDaniel/claude-seo | 19k | 2 repos | ~3.3k | Automated safety check: Pass | MIT | |
| SEO Content Brief GeneratorAgriciDaniel/claude-seo | 19k | 2 repos | ~2.6k | Automated safety check: Pass | MIT | |
| Strategic SEO PlanningAgriciDaniel/claude-seo | 19k | 5 repos | ~1.1k | Automated safety check: Pass | MIT | |
| Blog ClusterAgriciDaniel/claude-blog | 2.3k | 1 repos | ~4.9k | Automated safety check: Pass | MIT | |
| SEO Content Briefseranking/seo-skills | 160 | — | ~2.5k | Automated safety check: Pass | MIT |
AgriciDaniel/claude-seo
Clusters keywords by how much their search results overlap and designs a hub-and-spoke content plan with an internal link matrix and an interactive cluster map.
AgriciDaniel/claude-seo
Builds research-backed SEO content briefs with competitor scoring, per-section word counts and page-type templates, for new pages or improving existing ones.
AgriciDaniel/claude-seo
Builds an SEO strategy for a new or existing site: discovery, competitor analysis, site architecture, content plan, technical foundation and a four-phase roadmap.
AgriciDaniel/claude-blog
Semantic topic cluster planning and automated execution engine for claude-blog.
seranking/seo-skills
Generate a writer-ready SEO content brief from a target domain and topic.
Varnan-Tech/opendirectory
SEO keyword research workflow for blog generation using Google Trends data.
Affitor/affiliate-skills
Live affiliate program data from openaffiliate.dev. An agent skill from Affitor/affiliate-skills.
Affitor/affiliate-skills
Research and evaluate affiliate programs to find the best ones to promote.
Affitor/affiliate-skills
Create a Linktree-style bio link hub page as a single self-contained HTML file.
Affitor/affiliate-skills
Set up affiliate conversion tracking with UTM parameters and link tagging.
Affitor/affiliate-skills
Generate affiliate performance reports with KPIs and recommendations.
Affitor/affiliate-skills
Build a single-product deep-dive showcase page as a self-contained HTML file.
Categories
Map 50-200+ keywords into topical clusters for SEO domination. Keyword Cluster Architect is an agent skill from Affitor/affiliate-skills. Map 50-200+ keywords into topical clusters for SEO domination.
Keyword Cluster Architect fits situations like: : keyword research; keyword clustering; topical authority; keyword strategy.
Run `npx skills add Affitor/affiliate-skills --skill keyword-cluster-architect -a claude-code`. Or copy the skill folder (skills/blog/keyword-cluster-architect in Affitor/affiliate-skills) into .claude/skills/keyword-cluster-architect in your project. Claude Code loads it when a task matches its description.
Run `npx skills add Affitor/affiliate-skills --skill keyword-cluster-architect -a codex`. Or copy the skill folder (skills/blog/keyword-cluster-architect in Affitor/affiliate-skills) into .agents/skills/keyword-cluster-architect in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Affitor/affiliate-skills --skill keyword-cluster-architect -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/keyword-cluster-architect, .gemini/skills/keyword-cluster-architect, .github/skills/keyword-cluster-architect and .opencode/skills/keyword-cluster-architect in your project.
SKILL.md names no scripts, command-line tools or credentials: Keyword Cluster Architect is instructions for the agent only. Compatibility (from SKILL.md): Claude Code, ChatGPT, Gemini CLI, Cursor, Windsurf, OpenClaw, any AI agent.
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.
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.
Keyword Cluster Architect is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
About 2.4k tokens (SKILL.md is roughly 9.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Keyword Cluster Architect: SEO Keyword Clustering (AgriciDaniel/claude-seo, 19k stars), SEO Content Brief Generator (AgriciDaniel/claude-seo, 19k stars), Strategic SEO Planning (AgriciDaniel/claude-seo, 19k stars) and Blog Cluster (AgriciDaniel/claude-blog, 2.3k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Affitor (a GitHub organization) maintains it in Affitor/affiliate-skills, which has 700 GitHub stars. The repository holds 50 skills in this directory. The repository was last updated on September 15, 2026.
Source: Affitor/affiliate-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.