agentleFS
kid7stkid7st/agenticseo/.agents/skills/keyword-research/SKILL.md

keyword-research

Skill2 starsChanged 53 days agoMITView on GitHub

Discover keyword opportunities for a website, evaluate their metrics and SERPs, and recommend what to target. Use when a user asks which search terms fit a product, page or topic, or wants keyword ideas with evidence.

  • Reads credentials

59 other projects use a version of this, 10 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use openseo-release-notes, openseo-review-web-content and 5 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • JwuthriSkill

    openseo-release-notes

    Cut an OpenSEO release — bump the version, draft user-facing release notes from commits since the last tag, run a review + subagent-verification pass, and open a "release: vX.X.X" PR. Use when the user asks to prepare a release, bump the version, or write release notes.

    Also in 6 projects that use this

  • JwuthriSkill

    openseo-review-web-content

    Write and review content for the OpenSEO website (web/) — blog posts, guides, feature pages, FAQs. Distills the philosophy for on-brand, useful, accurate content. Use whenever adding or editing user-facing prose in web/content or web/src.

    Also in 5 projects that use this

  • Ethan-paseyaSkill

    review-analysis

    Amazon review and VOC analysis using SellerSprite MCP. Use when the user runs `/review-analysis {ASIN} {SITE}` to analyze positive and negative reviews, identify product pain points, listing mismatch, service risks, and product improvement actions.

    Also in 6 projects that use this

  • Kungfookenny123Skill

    app-marketing-context

    When the user wants to create or update their app marketing context document. Also use when the user mentions "app context", "marketing brief", "app positioning", or when starting any ASO or app marketing project. This is the foundation skill — all other skills check for this context first.

    Also in 4 projects that use this

  • Kungfookenny123Skill

    metadata-optimization

    When the user wants to optimize App Store metadata — title, subtitle, keyword field, or description. Also use when the user mentions "optimize my title", "ASO metadata", "keyword field", "character limits", "app description", or "write my subtitle". For keyword discovery, see keyword-research. For full ASO audits, see aso-audit.

    Also in 4 projects that use this

  • OpenClaudiaSkill

    backlink-audit

    Audit a domain's backlink profile using the SemRush API. Use when the user says "audit backlinks", "check my backlinks", "backlink analysis", "link profile", "toxic links", "disavow", "link building opportunities", "referring domains", "anchor text", or asks about a site's link authority.

    Also in 4 projects that use this

  • +1 more from Jwuthri

The file

We split this skill into the rules it gives an agent

12 rules. 0 are common, 4 are distinctive, and 8 are very specific to this project.

  • 0

    Common

    Most of the 54 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 8

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use the installed agenticseo command.

    line 14
  2. Very specific:

    Before paying, check researchLog.

    line 20
  3. Very specific:

    Add --clickstream to research or keywords only when the user wants refined volumes.

    line 28
  4. Very specific:

    Add --location COUNTRY [--language CODE] to run one call in another country than the project's, for example to compare markets.

    line 29
  5. Very specific:

    Run agenticseo research for each exploratory seed.

    line 46
  6. Very specific:

    Run agenticseo keywords to hydrate a fixed list of candidates with volume, difficulty and intent before prioritizing.

    line 47
  7. Distinctive:

    Remove irrelevant, duplicate, branded-only and off-intent terms.

    line 48
  8. Very specific:

    Run agenticseo serp for high-potential or ambiguous keywords when the SERP would change the recommendation.

    line 50
  9. Distinctive:

    Ask before saving keywords.

    line 52
  10. Very specific:

    Do not invent metrics. If a value is missing, write unknown.

    line 68
  11. Distinctive:

    Search volume is a provider estimate, not visits, and does not show Google rankings.

    line 69
  12. Distinctive:

    Prefer business fit and intent fit over the largest volume term.

    line 70

“Common” is measured: kept by at least 6 in 10 of the 54 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md
<!-- Adapted from OpenSEO plugins/openseo/skills/keyword-research/SKILL.md (https://github.com/every-app/open-seo, MIT, Copyright (c) 2026 Ben Senescu) for the AgenticSEO CLI. -->

Keyword research

Goal

Turn seed topics into a prioritized keyword opportunity set. The output should help the user decide what to target and what to research next.

Use the installed agenticseo command. If it is not on PATH, tell the user how to install it from the AgenticSEO repository; do not invent metrics. Paid commands need DATAFORSEO_API_KEY (base64 of DataForSEO login:password).

Project context

  1. Run agenticseo context first and ground the research in it: the business, the goal, the market in project.json, and the competitors and key pages already recorded. If it exits with code 2 because no project exists, ask for the site and market and run agenticseo init --domain DOMAIN --location COUNTRY (a two-letter country code such as US, or a DataForSEO location code; add --language only when the user targets a non-default language). Never guess the market.
  2. This skill needs sections.business_overview and sections.current_goal. If either is empty, ask the user (or infer from the site and confirm) just enough to fill them in .agenticseo/context.json, then continue. Suggest seo-project-setup at the end for the rest.
  3. Before paying, check researchLog. If the same research ran within the last 30 days, reuse its evidence file and say so instead of buying it again.
  4. On finish, write back what is durable: a sharpened current_goal, competitors that kept appearing in the SERPs in competitors, pages the keywords should land on in keyPages ({ "url", "role"?: "hub" | "spoke" | "money" | "other", "topic"?, "notes"? }), and one researchLog entry: { "entryDate": "<today from agenticseo context>", "summary": "Keyword research: <seeds>, <market>. Verdict: <conclusion>. Evidence: <paths>" }. Run agenticseo context to validate.

Commands

  • agenticseo research "SEED"... [--limit 150|300|500]: primary discovery, 1–5 seeds per call, each researched on its own; run a few distinct seeds rather than many near-duplicates. A seed that fails is reported with ok: false without failing the others. It returns each seed's first rows (25 for one seed, 10 each for several) and saves all rows with monthly trends as evidence. A repeat within 24 hours is served from the project cache at no cost (cached: true).
  • agenticseo keywords TERM...: volume, difficulty, intent, CPC and competition for up to 700 known terms in one call. Use it to score a fixed candidate list. Terms with no data are listed in missingKeywords.
  • agenticseo serp "QUERY"... [--depth 10-100]: live Google results for 1–10 queries, each billed. Use it when intent is ambiguous or you need to see who ranks; keep checks few, since each is billed.
  • Add --clickstream to research or keywords only when the user wants refined volumes; it doubles the cost.
  • Add --location COUNTRY [--language CODE] to run one call in another country than the project's, for example to compare markets. Report which market each number comes from.

Every result states source, date, market and costUsd, and points to an evidence file; read rows from that file (for example with jq) instead of rerunning a paid command. When source is google_ads, the market is not covered by DataForSEO Labs, so difficulty and intent are unavailable.

  • agenticseo ranked TARGET [--scope ...] [--max-rank N] [--min-volume N] [--exclude BRAND,...]: the keywords a domain or page already ranks for, when a target site or competitor is part of the brief. Use it for near-miss terms (for example --max-rank 20 on the user's own site) and competitor-owned terms.
  • agenticseo competitors KEYWORD...: which domains compete across the candidate terms' SERPs.
  • agenticseo saved list [--tags TAG,...]: keywords the project already saved, with their latest metrics and tags. Check it first to avoid redoing work, and use existing tags as context.
  • agenticseo saved add KEYWORD... --tags TAG,...: save chosen keywords only after the user explicitly confirms. Suggest short tags such as topic:<topic>, intent:<intent> or page:<slug>, and confirm new tag names. Researched keywords keep their metrics; agenticseo saved refresh re-fetches all saved keywords and is billed, so ask first.
  • agenticseo rank create, then agenticseo rank add TRACKER_ID KEYWORD...: track the chosen keywords' Google positions for the project domain, when the user wants to follow them over time. Run agenticseo rank estimate TRACKER_ID and show the cost before agenticseo rank run or before setting --schedule daily|weekly|monthly. A schedule only runs once the user adds the line from agenticseo rank schedule to their system scheduler. Read results with agenticseo rank show TRACKER_ID.
  • agenticseo query "SELECT ...": read-only SQL over saved keywords and stored metrics when a question needs a join or aggregate, for example the highest-volume saved keywords per tag. Select only the columns and rows you need.
  • agenticseo gsc performance --dimensions query,page --min-position 5 --max-position 20 --min-impressions 50: when Search Console is connected for the project, start from its real first-party demand: queries already earning impressions whose best page sits in "striking distance". Then run agenticseo keywords on those queries to attach difficulty and intent; that ranked list is the fastest opportunity set, so work it before broad discovery. Exit code 2 means it is not connected (skip it and say so); 3 means the Google grant needs reconnecting.

Workflow

  1. Normalize seeds into a small set of distinct research angles.
  2. Run agenticseo research for each exploratory seed.
  3. Run agenticseo keywords to hydrate a fixed list of candidates with volume, difficulty and intent before prioritizing.
  4. Remove irrelevant, duplicate, branded-only and off-intent terms.
  5. Prioritize by practical opportunity, not volume alone: fit with the product, page or topic; clear intent; reasonable difficulty; useful volume or CPC; a SERP the site can plausibly compete in.
  6. Run agenticseo serp for high-potential or ambiguous keywords when the SERP would change the recommendation.
  7. Present a shortlist and a longer opportunity table.
  8. Ask before saving keywords. When the user agrees, save them with tags and say which tags you used.

Output

Deliver through the seo-report skill. If a report template applies, its sections and tone replace this list. Otherwise, after the # <site or topic> — <date> title and the summary:

  1. The opportunity: the best theme and why the site can win it now.
  2. Target these now: a table of keyword, intent, volume, difficulty, CPC and the page to make. Add a bar chart comparing the volumes of the shortlist.
  3. Why these: one finding per keyword that needs justifying, with the SERP or metric evidence and the page to build.
  4. The longer opportunity list: a second table with the same columns.
  5. Risks and caveats: SERP intent that would change the recommendation, missing metrics written as unknown, close-variant volumes that are one bucket rather than several.
  6. What to do next: an ordered list, including whether to run keyword-clustering, write a content brief, or save the chosen keywords.
  7. How this report was made: opens with the skill link line from seo-report, pointing at https://github.com/kid7st/agenticseo/blob/main/.agents/skills/keyword-research/SKILL.md ("AgenticSEO Keyword Research skill"), then the commands run, the market, the dates, the costs and the evidence paths.

Guardrails

  • Do not invent metrics. If a value is missing, write unknown; never write 0 for it.
  • Search volume is a provider estimate, not visits, and does not show Google rankings.
  • Prefer business fit and intent fit over the largest volume term.
  • On exit code 3, ask the user to fix the key. On exit code 4, report the error and any charged cost, and do not retry in a loop.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.