dineway/dineway-skills

dineway-seo-cluster

Plan Dineway SEO topic clusters, hub-and-spoke architectures, internal link matrices, local intent clusters, and draft page/post targets. Use for seed keywords, content architecture, SERP-overlap clustering, pillar pages, spoke pages, and measurement plans.

First seen Jun 16, 2026

Installation

$ npx skills add dineway/dineway-skills --skill dineway-seo-cluster

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from dineway/dineway-skills · top by installs.

npx skills add dineway/dineway-skills

Browse all from dineway/dineway-skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 2
License LICENSE
Default branch main
Open issues 0
Status Active

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,188 B
  • docs SUMMARY.md 284 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 11 installs

SKILL.md

Dineway SEO Cluster

Use this child skill for topic clusters and content architecture. It may be invoked directly, but it must preserve the shared Dineway SEO boundaries.

Required References

  • Load ../dineway-seo/references/topic-cluster.md.
  • Load ../dineway-seo/references/apply-loop.md before recommending or applying Dineway changes.
  • Load ../dineway-seo/references/security-boundaries.md before using provider evidence or external-source recommendations.
  • Load ../dineway-seo/references/provider-selection.md when live keyword or SERP overlap evidence may be needed.
  • Load ../dineway-seo/references/dataforseo.md when using keyword suggestions or SERP results.

Workflow

  1. Inventory current Dineway collections, existing pages/posts, internal links, site context, and SEO settings.
  2. Expand the seed into head terms, modifiers, local variants, comparison terms, questions, and seasonal/event variants.
  3. Cluster by intent and SERP overlap, not wording alone.
  4. Choose hub pages only when they can satisfy broad intent and naturally link to distinct spokes.
  5. Map each hub/spoke to an existing Dineway collection or a proposed schema/content target.
  6. If applying changes, create or update drafts first and verify links/metadata.

Boundaries

  • Do not create doorway pages or thin local pages.
  • Do not write local HTML maps or unrelated local artifacts.
  • Do not ask for provider secret values or use third-party provider MCP servers. Local bounded crawl,

Browser Use, and Dineway Tools MCP/CLI evidence are allowed under the shared boundaries.

  • Skip terms when there is no distinct source-backed Dineway value.

Output

Use the root dineway-seo output contract. Include Cluster Map, Hub Recommendation, Spoke Pages, Internal Link Matrix, Dineway Content Targets, Provider Evidence, Skipped Terms, and Measurement Plan.