本文へ移動
cccskills
無料GitHub で公開

seo-keyword

Run keyword research, classify by search intent, cluster into topical groups, and prioritize for content production. Use this skill whenever the user asks to do keyword research, find target keywords, identify ranking opportunities, classify search intent, build a topical map, or plan a content strategy around what people search for. Triggers on keyword research, keyword strategy, search intent, keyword clustering, topic clusters, keyword difficulty, search volume, ranking opportunity, content gap, what should I write about, target keyword, primary keyword, secondary keyword, long-tail. Also triggers when planning a content calendar or new site without keywords yet defined.

インストール方法を見る

含まれるファイル(4)

  • SKILL.md7.8 KB
  • README.md352 B
  • references/intent-classification-guide.md10.6 KB
  • references/keyword-research-template.md3.0 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Keyword Research

Find the queries worth ranking for, classify them by intent, cluster them into topics, and prioritize what to produce. Stack-agnostic. Tool-agnostic (works with any keyword tool).


When to use

  • Starting a new site or content section
  • Planning a content calendar
  • Looking for ranking opportunities on an existing site
  • Understanding search intent before writing
  • Building topic clusters for internal linking
  • Identifying content gaps vs competitors

When NOT to use

  • Optimizing a single page where the target query is already known (use seo-onpage)
  • Comparing your site to a competitor across many dimensions (use seo-competitor)
  • Auditing existing content for performance (use seo-content-audit)

Required inputs

  • The site or topic area
  • The target audience and what they need
  • A keyword tool (Ahrefs, Semrush, Moz, Google Keyword Planner, or similar) OR access to search console for an existing site
  • Optional: 3 to 5 known competitors to seed the research

If no tool is available, the skill still works using SERP inspection and search console data alone, but the volume estimates will be rough.


The framework: 4 stages

Stage 1: Discover

Cast a wide net. Sources:

  • Seed terms from the brief or the user's vocabulary
  • Competitor keywords (any keyword tool will export these)
  • Search console queries for an existing site (find the page-1 and page-2 queries)
  • Related searches and "People also ask" in actual SERPs
  • Customer language (support tickets, sales calls, reviews)
  • Forum and community language (Reddit, niche forums, Stack Overflow)

Goal: 200 to 500 candidate keywords for a typical content sprint. More if planning a year of content.

Stage 2: Classify by intent

Every keyword maps to one of four intents. Get this right or the rest is noise.

IntentSignalPage type that wins
Informational"how to," "what is," "why," "best way to"Article, guide, tutorial
Navigationalbrand or product name + modifierBrand homepage, product page
Commercial"best," "review," "vs," "comparison," "alternatives"Listicle, comparison, review
Transactional"buy," "price," "deal," "near me," "for sale"Product page, category page

A keyword tool's volume tells you the demand. The SERP tells you the intent. When in doubt, look at what's actually ranking. If page 1 is articles, the query is informational. If page 1 is product pages, it's transactional.

Hybrid intents exist. "Best running shoes" is commercial-investigational. "Best running shoes under $100" is the same intent narrowed by a budget filter. Treat hybrids as their dominant intent and note the modifier.

Stage 3: Cluster

Group keywords that should target the same page (or topic cluster).

Two clustering approaches:

Approach A: SERP overlap. If two keywords share at least 3 of the top 10 results, they target the same page. This is mechanical and reliable.

Approach B: Topical relevance. Group keywords by the underlying topic, not just word overlap. "How to start a podcast" and "podcast equipment for beginners" are the same topic, different facets.

Use both. A typical cluster has:

  • 1 primary keyword (highest volume, broadest intent)
  • 5 to 15 secondary keywords (variations and long-tails)
  • 1 page that targets them all

Stage 4: Prioritize

For each cluster, score on three dimensions:

Opportunity (1 to 5):

  • Volume (raw search demand)
  • Click potential (some queries answer themselves in the SERP, lowering CTR)
  • Conversion potential (does this query attract buyers or browsers?)

Difficulty (1 to 5):

  • Domain authority of top results
  • Backlink count of top results
  • Content depth and freshness of top results
  • Whether the SERP has features (featured snippets, AI overview, video carousel) that compete with organic

Strategic fit (1 to 5):

  • Does it serve our audience?
  • Does it support our positioning?
  • Does it link to commercial pages naturally?

Priority score = Opportunity + Strategic fit - Difficulty.

Rank the clusters. Top 20 percent get produced first.


Workflow

  1. Define the scope. What site, what topic area, what audience.
  2. Run discovery. Pull seeds, competitor exports, search console data, SERP inspections. Aim for 200 to 500 candidates.
  3. Deduplicate and clean. Remove obvious junk, brand misspellings, irrelevant terms.
  4. Classify by intent. Mark each keyword.
  5. Cluster. Group into topical clusters. Aim for 20 to 50 clusters.
  6. Score each cluster on opportunity, difficulty, and strategic fit.
  7. Prioritize. Rank by composite score. Identify the top 10 to 20 clusters to produce first.
  8. Output. Use the template in references/keyword-research-template.md.

Failure patterns

  • Chasing volume without intent. A 10,000-volume informational keyword does not drive purchases. Match query to commercial outcome.
  • Targeting impossibly competitive keywords. New sites cannot rank for "credit cards." Find the underserved long-tail variant.
  • Ignoring search console. Existing sites already rank for queries they did not target. These are the easiest wins.
  • Treating clusters as one-keyword-per-page. A page can target 10 to 30 related keywords. One-keyword-per-page leads to thin, cannibalized content.
  • Ignoring SERP features. A query with a featured snippet, AI overview, and a video carousel above the organic results may not be worth pursuing.
  • Static keyword research. Search demand shifts. Refresh the research at least annually for evergreen sites, quarterly for fast-moving topics.

Output format

Default output: a spreadsheet (CSV or sheet) with one row per keyword and one row per cluster, plus a markdown summary with the top 10 to 20 clusters detailed.

Recommended columns for the keyword sheet:

ColumnSource
KeywordDiscovery
VolumeTool
DifficultyTool
IntentManual classification
SERP featuresManual or tool
ClusterStage 3
Cluster role (primary/secondary)Stage 3
Opportunity scoreStage 4
Strategic fitStage 4
PriorityComposite
NotesFree text

If required data is unavailable

This skill's output depends on data, measurements, or tool results it cannot generate on its own. When a required input, tool, or data source is unavailable or unverifiable, the sanctioned output is the deliverable with the gap stated: what was needed, what was actually obtained or verified, and which parts of the output are affected. Fabricating, estimating, or interpolating a required number to complete the deliverable is never sanctioned. A stated gap is a complete answer.


Reference files

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Run a comprehensive WCAG accessibility audit covering perceivable, operable, understandable, and robust principles. Use this skill whenever the user wants to audit accessibility, review WCAG compliance, fix accessibility issues, prepare for accessibility certification, address an accessibility lawsuit risk, or systematically improve a site's accessibility. Triggers on accessibility audit, WCAG audit, a11y audit, accessibility compliance, ADA compliance, screen reader test, keyboard navigation, accessibility report, fix accessibility, axe scan. Also triggers when accessibility issues have been reported and need systematic remediation.

日本語の概要は準備中です。原文の説明を表示しています。

rampstackco/claude-skills9532026年10月7日 更新

How to produce ad creative that converts at performance scale. Hook patterns, format selection, video pacing, variation systems, sequential testing methodology, fatigue detection, brand-voice alignment without conversion dilution, and platform-specific creative norms. Triggers on ad creative, ad design, hook patterns, ad video pacing, creative testing, ad variations, creative refresh, creative fatigue, refresh ad creative, video ads for Meta, TikTok creative, LinkedIn ad creative, ad asset library. Also triggers when a team is producing creative at scale, planning a creative test cycle, or auditing why creative is not converting.

日本語の概要は準備中です。原文の説明を表示しています。

rampstackco/claude-skills9532026年10月7日 更新

How to read paid media dashboards without fooling yourself. Attribution models, platform reporting quirks, multi-platform reconciliation, ROAS vs LTV horizon traps, statistical noise in performance metrics, incrementality testing, and the failure modes that produce expensive lessons. Triggers on read paid media dashboard, attribution analysis, ROAS vs LTV, multi-platform reconciliation, ad incrementality, geo holdout, conversion lift study, ghost bidding, paid media reporting, board-deck paid media metrics, blended CAC, MMM, MTA, last-click attribution. Also triggers when a marketer is about to scale, kill, or rebudget a campaign based on platform metrics, or when reconciling platform reports against warehouse revenue.

日本語の概要は準備中です。原文の説明を表示しています。

rampstackco/claude-skills9532026年10月7日 更新

Run a structured after-action review (postmortem, retrospective) on a launch, incident, or completed project to capture timeline, root cause analysis, contributing factors, and actionable lessons. Use this skill whenever the user wants to run a postmortem, retrospective, AAR, or after-action review on any past event. Triggers on after-action report, AAR, postmortem, retrospective, retro, post-incident review, what went well what didn't, lessons learned, blameless postmortem, root cause analysis, RCA, five whys. Also triggers when the user has just shipped something or just resolved an incident and wants to capture learnings.

日本語の概要は準備中です。原文の説明を表示しています。

rampstackco/claude-skills9532026年10月7日 更新

How humans and AI compose in content workflows. Where AI legitimately participates, where humans must own, hybrid workflow patterns, voice ownership preservation, the AI slop problem, disclosure and transparency, team calibration, and the ethics of intellectually honest AI-assisted content production. Triggers on AI content workflow, AI-assisted writing, hybrid content production, AI in editorial, AI slop, AI disclosure, AI usage policy, AI content ethics, voice preservation with AI, team AI calibration. Also triggers when content feels generic despite quality tools, when team AI usage has drifted into inconsistency, or when a regulated or trust-sensitive context requires explicit AI policy.

日本語の概要は準備中です。原文の説明を表示しています。

rampstackco/claude-skills9532026年10月7日 更新

Design measurement frameworks including event taxonomy, KPI hierarchy, dashboard architecture, attribution models, and analytics implementation strategy. Use this skill whenever the user wants to plan analytics, design dashboards, build event taxonomies, define KPIs, set up tracking, or audit existing measurement. Triggers on analytics strategy, measurement plan, event taxonomy, tracking plan, KPI framework, dashboard design, north star metric, attribution model, conversion tracking, GA4 setup, Mixpanel setup, analytics audit. Also triggers when the user has data but no clear way to use it, or wants to make decisions but doesn't know what to track.

日本語の概要は準備中です。原文の説明を表示しています。

rampstackco/claude-skills9532026年10月7日 更新

rampstackco のスキルをすべて見る

このスキルの問題を報告する