serp-analysis

serp-analysis is a skill for Claude Code from RightBlogger/bloggingskills. It costs 118 tokens per session (924 once invoked), scanned A, original, MIT.

A method for studying the live search results for a target keyword and turning them into a content brief. SERP means search engine results page—the list of pages shown after a search.

In plain words
What is it for?
Use it to assess search competition, choose an editorial angle, and outline what a page should cover to target a keyword.
Why use it?
It shows what currently ranks and where those pages are weak, so you can plan useful content instead of copying competing pages.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the blogging-skills plugin — 12 skills shipped together

Good fit Use it to assess search competition, choose an editorial angle, and outline what a page should cover to target a keyword.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/rightblogger/bloggingskills/serp-analysis
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add RightBlogger/bloggingskills --skill serp-analysis
Clone the repo
git clone --depth 1 https://github.com/RightBlogger/bloggingskills

Made for: Claude Code.

Or install blogging-skills, the plugin that ships this one along with the rest of its 12 skills.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for serp-analysis

README.md
[![agentmods](https://agentmods.dev/badge/skills/rightblogger/bloggingskills/serp-analysis/github.svg)](https://agentmods.dev/skills/rightblogger/bloggingskills/serp-analysis)
Your own site
<a href="https://agentmods.dev/skills/rightblogger/bloggingskills/serp-analysis"><img src="https://agentmods.dev/badge/skills/rightblogger/bloggingskills/serp-analysis/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for serp-analysis

Your own site · 80×15
<a href="https://agentmods.dev/skills/rightblogger/bloggingskills/serp-analysis"><img src="https://agentmods.dev/badge/skills/rightblogger/bloggingskills/serp-analysis.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 118 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 924 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00118 $0.00924
Opus 5 $0.00059 $0.00462
Sonnet 5 $0.00024 $0.00185
Haiku 4.5 $0.00012 $0.00092

Measured 10d ago against content hash 367cc33a9a83, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

serp-analysis scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 10d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/serp-analysis/SKILL.md · 75 lines

How it starts

The opening of the file, as written. The whole thing — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.

SERP analysis

You read the current top results for one keyword and report what it takes to win the page. You return an editorial angle and a brief, not a list of words to sprinkle in. The point is to find where the leaders are weak, not to copy them.

Initial assessment

  • If .agents/blog-context.md exists, read it first. It sets the niche, audience, and target country and language, and the SERP differs by all of them. Honor those over any default.
  • Confirm the target keyword. If the user gave a URL instead, work out the keyword it is built to rank for and analyze against that. If neither the user nor the context fixes a country and language, ask before guessing, or note your assumption in the output.
  • Check what you can fetch. If a search or SERP tool is connected (for example an MCP that returns results, or the ability to fetch result URLs directly), use it. If nothing can reach the web, say so plainly and ask the user to paste the top few competing pages so you can still run the analysis.

Method

  1. Pull the top three to five organic results. Skip ads and skip pure aggregators unless they genuinely compete. Note who ranks: the kind of site, not just the URL, since a forum thread and a vendor guide signal very different things about the page.
  2. Read the dominant intent. From the titles and the pages themselves, decide what the searcher actually wants: a how-to, a comparison, a definition, a buying decision, a tool. Get this wrong and depth will not save the piece.
  3. Map the table stakes. List the subtopics and headings that nearly every result covers. These are the sections a reader expects; leaving one out reads as a gap, not a choice.
  4. Spot the optional angles. Note the subtopics only some pages cover. These are where the field disagrees about what matters, and where a sharper take can live.
  5. Find the gap. This is the work. Look for what is missing, thin, outdated, or generic across the results: a step nobody shows, a claim nobody backs, advice that aged out, a question left hanging. Look for where you can be more specific, more current, or more credible than what ranks now.

Read the full file on GitHub · 75 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 10d ago First seen · 75 lines · 118 tokens per session scan A 367cc33a9a83

Subscribe to this mod's changes

serp-analysis is a skill published in the GitHub repository RightBlogger/bloggingskills (2 stars, last pushed 2mo ago), licensed MIT. It adds 118 tokens to every session and 924 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

affiliate-blog-builder

Write SEO-optimized affiliate blog articles, product reviews, comparison posts, listicles, and how-to guides. Triggers on: "write a blog post about", "review of [product]", "best [category] article", "comparison blog", "affiliate blog", "SEO article", "write a review", "product roundup", "blog content for affiliate"…

Affitor/affiliate-skills · 110 tokens

comparison-post-writer

Write "X vs Y" comparison blog posts that help readers choose between two competing products. Triggers on: "write a comparison post", "X vs Y blog post", "compare [product A] and [product B]", "which is better [A] or [B]", "head to head comparison", "[product] vs [product] article", "comparison review", "write a…

Affitor/affiliate-skills · 115 tokens

how-to-tutorial-writer

Write how-to guides and tutorials that naturally integrate affiliate product recommendations. Triggers on: "write a how-to guide", "tutorial for [task]", "step by step guide to [goal]", "how to [verb] with [product]", "write a tutorial blog post", "guide on how to [task]", "beginner guide to [topic]", "walkthrough for…

Affitor/affiliate-skills · 112 tokens

listicle-generator

Write "Top N best..." listicle articles for affiliate marketing with mini-reviews, pricing, pros/cons, and CTAs per entry. Triggers on: "write a best of list", "top 10 [category] tools", "best [product category] article", "roundup post", "listicle about [category]", "write a top tools article", "best [N] alternatives…

Affitor/affiliate-skills · 117 tokens

keyword-cluster-architect

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…

Affitor/affiliate-skills · 101 tokens

content-decay-detector

Monitor existing content for ranking drops and trigger refresh workflows. Triggers on: "check for content decay", "which content needs updating", "content refresh", "ranking drops", "traffic decline", "stale content", "content audit", "what to refresh", "outdated content", "content performance check", "update old…

Affitor/affiliate-skills · 100 tokens