agentsclimarketplace

Keyword cluster architect

Skill Gingg7260/affiliate-skills/skills/blog/keyword-cluster-architect

Automate affiliate marketing with 45 AI skills for research, content, pages, tracking, and optimization across any AI agent

Install
npx -y skills add Gingg7260/affiliate-skills --skill keyword-cluster-architect

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 5 stars5 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

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".

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

9.4 KB, ~2.1k tokens by cl100k_base, as published. Nobody here has run it

Keyword Cluster Architect

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.

Stage

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.

When to Use

  • User wants to plan SEO content strategy for a niche
  • User asks about keyword research, clustering, or topical authority
  • User says "keyword", "SEO plan", "content roadmap", "topic cluster", "hub and spoke"
  • Before running affiliate-blog-builder — to know WHICH articles to write
  • After monopoly-niche-finder — to map the keyword universe for the winning niche

Input Schema

niche: 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: none

Chaining from S1 monopoly-niche-finder: Use monopoly_niche.intersection as the niche input.

Workflow

Step 1: Generate Seed Keywords

If not provided, generate 5-10 seed keywords from the niche:

  • Product-focused: "[product] review", "best [category]"
  • Problem-focused: "how to [solve problem]", "[problem] solution"
  • Comparison: "[product A] vs [product B]", "alternatives to [product]"
  • Tutorial: "how to use [product]", "[product] tutorial"

Step 2: Expand Keywords

For each seed, use web_search to discover related keywords:

  1. Search: "[seed keyword]" — note related searches, People Also Ask
  2. Search: "[seed keyword] guide" OR "[seed keyword] tutorial" — informational variants
  3. Search: "best [seed keyword]" OR "[seed keyword] review" — commercial variants

Collect 50-200+ unique keywords depending on depth.

Step 3: Classify by Intent

Read shared/references/seo-strategy.md for clustering methodology.

Classify each keyword:

  • Informational (I): Learning, how-to, what-is → blog posts, tutorials
  • Commercial (C): Comparing, evaluating, reviewing → comparison posts, reviews
  • Transactional (T): Ready to buy, pricing, discount → landing pages, deal pages
  • Navigational (N): Brand-specific, login → skip (not your traffic to capture)

Step 4: Cluster by Topic

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]

Step 5: Build Content Roadmap

Organize clusters into a hub-and-spoke map:

  1. Identify the hub page (broadest, highest-volume cluster)
  2. Connect spoke pages (specific clusters that link back to hub)
  3. Prioritize by: commercial intent first (revenue), then informational (traffic)
  4. Estimate effort: number of articles needed, suggested publishing cadence

Step 6: Self-Validation

  • Clusters are based on actual search data, not guesses
  • Each cluster has a clear search intent (I, C, or T)
  • Hub-and-spoke structure is logical (hub is broad, spokes are specific)
  • Priority ordering makes business sense (revenue-driving content first)
  • Total content pieces are realistic for user's capacity

Output Schema

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"

Output Format

## 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 clusters

Error Handling

  • Niche too broad: "This niche is very broad. Let me narrow to a sub-niche for more actionable clusters. Or run monopoly-niche-finder first."
  • No search volume: "This niche may be too narrow for significant search traffic. Consider broadening slightly."
  • Too many keywords: Group aggressively into fewer clusters. Quality of clustering > quantity of keywords.
  • No commercial intent keywords: Flag as concern — hard to monetize through affiliate without commercial intent. Suggest adjacent niches.

Examples

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.

Flywheel Connections

Feeds Into

  • affiliate-blog-builder (S3) — which articles to write and target keywords
  • comparison-post-writer (S3) — commercial clusters become comparison articles
  • content-moat-calculator (S3) — keyword count informs moat estimation
  • landing-page-creator (S4) — transactional clusters become landing pages
  • internal-linking-optimizer (S6) — cluster structure defines link architecture

Fed By

  • monopoly-niche-finder (S1) — niche to cluster keywords for
  • content-pillar-atomizer (S2) — content pillars suggest keyword areas
  • seo-audit (S6) — current ranking data reveals keyword gaps

Feedback Loop

  • seo-audit (S6) reveals ranking gaps in existing clusters → add keywords and new content to fill gaps

Quality Gate

Before delivering output, verify:

  1. Would I share this on MY personal social?
  2. Contains specific, surprising detail? (not generic)
  3. Respects reader's intelligence?
  4. Remarkable enough to share? (Purple Cow test)
  5. Irresistible offer framing? (roadmap feels actionable)

Any NO → rewrite before delivering.

References

  • shared/references/seo-strategy.md — Topical authority, clustering methodology, hub-and-spoke
  • shared/references/affiliate-glossary.md — Terminology
  • shared/references/flywheel-connections.md — Master connection map

Gives 0 of the 12 instructions most architecture codebase skills give in ~2.1k tokens

Counted across 811 of the 1,134 authors here whose files we hold, read 2026-08-06

  • ask the user which candidate to explorein 46 of 811, across 16 files
  • apply the deletion test to suspected shallow modulesin 43 of 811, across 15 files
  • read any relevant architecture decision records firstin 31 of 811, across 7 files
  • use exact glossary terms in every suggestionin 29 of 811, across 9 files
  • accept dependencies instead of creating themin 24 of 811, across 5 files
  • include before and after visualisations for each candidatein 24 of 811, across 5 files
  • read the domain glossary before exploringin 24 of 811, across 6 files
  • return results instead of producing side effectsin 23 of 811, across 4 files
  • explore the codebase for shallow modules and frictionin 23 of 811, across 3 files
  • introduce seams only where things varyin 22 of 811, across 3 files
  • reduce the number of methodsin 21 of 811, across 2 files
  • design deep modules with small interfacesin 21 of 811, across 2 files

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.