본문으로 건너뛰기
cccskills
무료GitHub에 공개

openseo-keyword-clustering

Cluster keywords by search intent and map each cluster to an existing or proposed page, with cannibalization detection from Search Console. Use this skill when the user has a keyword list (saved set, brand/keyword-plan.md, GSC export, or seed topic) and needs page targets, content briefs, or a site map for SEO pages — especially before seo-content or seo-machine page generation. Triggers: "cluster keywords", "keyword mapping", "map keywords to pages", "keyword cannibalization", "which page should target".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

연동 도구Search Console
설치 방법 보기

포함된 파일(1)

  • SKILL.md5.0 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

OpenSEO Keyword Clustering

Group keywords into page-level clusters and assign each to an existing URL, a new page proposal, or a do-not-target bucket. Output lands in marketing/seo/clusters/*.md (per-cluster briefs) and feeds seo-content / seo-machine with measured page targets.

On Activation

  1. Readiness + binding: mktg seo status --json --fields readiness,catalog.endpointError,project. No binding → openseo-project-setup first. not_configured → do lexical clustering with Exa context but label every cluster "SERP-unvalidated." For a ready state, verify live access with the free whoami MCP tool before paid calls.
  2. Keyword source: prefer (a) brand/keyword-plan.md populated sections, (b) list_saved_keywords with a tag, (c) GSC live data, (d) seed discovery via research_keywords. Under 10 usable terms → simple map, no clustering ceremony.

OpenSEO MCP Tools

  • get_search_console_performance with dimensions: ["query","page"]: the cannibalization truth source — one query splitting impressions across multiple URLs means existing cannibalization, not theoretical risk.
  • get_ranked_keywords: domain/page-driven clustering from exact ranking rows + URLs.
  • get_serp_results: SERP-overlap validation for borderline terms (small batches, ≤10).
  • list_saved_keywords / research_keywords: source sets.
  • save_keywords: apply cluster tags ONLY after confirmation.

Workflow

  1. Assemble the candidate set from the source hierarchy above; dedupe and drop off-strategy terms.
  2. Cluster by intent and page type: same SERP intent + similar ranking pages belong together; different intent/buyer stage/SERP format splits. Lexical similarity is NOT evidence of same-page fit.
  3. Borderline terms: small get_serp_results overlap check.
  4. Assign each cluster: existing URL (if supplied and fitting), new-page proposal, or do-not-target/later.
  5. Cannibalization check: GSC query+page data first; otherwise flag where two proposed pages share one intent.
  6. Write per-cluster briefs to marketing/seo/clusters/<cluster-slug>.md: page type, searcher problem, required sections, internal-link targets, priority.
  7. Optionally tag clusters with save_keywords after confirmation.
  8. Hand off: seo-content for single pages, seo-machine for programmatic batches — both now have measured targets instead of vibes.

Output Format

Summary first: cluster count, pages to create, pages to update, cannibalization issues. Then:

ClusterPrimary keywordSecondary keywordsIntentTarget pagePriorityNotes

Anti-Patterns

  • Clustering by word similarity alone — because "best crm for dentists" and "crm pricing dentists" share words but not intent, and forcing them onto one page guarantees neither ranks. SERP intent wins; check overlap when unsure.
  • Clustering tiny sets — because 6 keywords don't need a clustering framework, they need a paragraph. Under 10 terms, write a simple map.
  • Theoretical cannibalization warnings without data — because crying cannibalization on every overlapping term freezes page production; GSC query+page splits are the only proof. No GSC → label it "potential," not "confirmed."
  • Retagging saved keywords without confirmation — because tags are shared account state; a bulk retag can destroy someone else's organization. Confirm first.
  • Producing clusters with no page assignment — because a cluster without a target page is trivia. Every cluster ends in an existing URL, a new proposal, or an explicit do-not-target decision.

Close the loop

After writing files, log completion so mktg plan / mktg status count the work (bare mktg run only logs loaded):

mktg run openseo-keyword-clustering --complete --writes <paths written> --result success --json

Adapted from every-app/open-seo .agents/skills/keyword-clustering (MIT). Workflow upstream; mktg artifact paths, brand-memory reads, and handoff wiring added here.

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

Add a new expert to the Remotion experts page

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

MoizIbnYousaf/marketing-cli322026년 10월 20일 업데이트

add-sfx

무료

Add a new sound effect to @remotion/sfx

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

MoizIbnYousaf/marketing-cli322026년 10월 20일 업데이트

Use when setting up a secure email inbox for any AI agent — configuring inbound email via Resend, webhooks, tunneling for local development, and implementing security measures to prevent prompt injection attacks. Also use when someone mentions 'agent email', 'bot inbox', 'receive emails for agent', 'agent webhook', 'email security for AI', 'prompt injection via email', 'inbound email for bot', or wants their AI agent to receive and respond to emails securely.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

MoizIbnYousaf/marketing-cli322026년 10월 20일 업데이트

ai-seo

무료

Builds, measures, and improves an Answer Engine Optimization program across ChatGPT, Perplexity, Claude, Gemini, Google AI Overviews, and Copilot. Use for AEO, GEO, LLMO, AI search visibility, AI citations, brand mentions, answer-engine monitoring, llms.txt, AI crawler audits, or questions like 'what does AI say about us?' and 'why are competitors cited instead of us?'. Produces a durable evidence report and prioritized gameplan, not a one-shot content checklist.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

MoizIbnYousaf/marketing-cli322026년 10월 20일 업데이트

Generate Apple App Store screenshot pages as a Next.js app with html-to-image export at required resolutions. Screenshots are advertisements, not documentation — every screenshot sells one idea. Use when building App Store screenshots, generating exportable marketing screenshots for iOS apps, or creating programmatic screenshot generators. Triggers on 'app store screenshots', 'App Store', 'screenshot generator', 'iOS screenshots', 'marketing screenshots', 'phone mockup', 'ASO screenshots', 'app store assets', 'app listing', 'app store page', or 'app preview images'. Also use when someone is about to submit an app and needs store assets, or when they say 'make my app store page look good'. Includes iPhone and iPad mockup components with pre-measured dimensions.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

MoizIbnYousaf/marketing-cli322026년 10월 20일 업데이트

Build detailed buyer personas and audience profiles from research. Use this skill whenever the user mentions audience, buyer persona, ideal customer, target market, ICP, watering holes, 'who am I selling to', customer research, or audience profile. Also use when content feels unfocused or generic (that's an audience problem), when conversion is low because messaging doesn't resonate, when starting any new project (audience should be first), or when any downstream skill needs audience.md but it doesn't exist yet. Even if the user doesn't explicitly ask for audience research, trigger this if they're writing copy or building a landing page without a clear audience defined. Three approaches: Quick Profile, Persona Build, Community Mining.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

MoizIbnYousaf/marketing-cli322026년 10월 20일 업데이트

MoizIbnYousaf의 스킬 모두 보기

이 스킬의 문제 신고