What is seo-keyword-content?

A writing guide for creating search-friendly content for software and tool directory pages, including descriptions, audiences, workflows, features, pros and cons, tips, and FAQs.

Use it to expand or standardize tool-page content and naturally include specific search phrases, such as longer, more focused queries.

It gives thin or repetitive directory entries clearer search intent and more useful detail without simply repeating keywords.

seo-keyword-content — Skill for Claude Code and Codex by sherotree

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 sherotree/seo-agent-skills --skill seo-keyword-content

Clone the repo

git clone --depth 1 https://github.com/sherotree/seo-agent-skills

Made for: Claude Code, Codex.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/sherotree/seo-agent-skills/seo-keyword-content/github.svg)](https://agentmods.dev/skills/sherotree/seo-agent-skills/seo-keyword-content)

Your own site

<a href="https://agentmods.dev/skills/sherotree/seo-agent-skills/seo-keyword-content"><img src="https://agentmods.dev/badge/skills/sherotree/seo-agent-skills/seo-keyword-content/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/sherotree/seo-agent-skills/seo-keyword-content"><img src="https://agentmods.dev/badge/skills/sherotree/seo-agent-skills/seo-keyword-content.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 56 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,540 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.

Model	Per session	Once invoked
Fable 5.1	$0.00056	$0.02540
Opus 5	$0.00028	$0.01270
Sonnet 5	$0.00011	$0.00508
Haiku 4.5	$0.00006	$0.00254

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

Security

Grade A, and why

seo-keyword-content 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 12d 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/seo-keyword-content/SKILL.md · 258 lines

How it starts

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

SEO Keyword Content Skill

Use this skill when a user asks to improve thin content for tool pages, expand programmatic SEO fields, or make data entries "keyword-driven."

When to use: thin or missing longDescription / faqs, generic oneLiner, repetitive bullets, keyword lists that lack intent mix, bulk normalization of tool JSON/TS data, or reviews of SEO field coverage before ship.

This skill is optimized for tool-directory style records. Primary SEO-facing fields:

title
keywords
oneLiner
longDescription
whoItsFor
notFor
workflows
features
advantages
disadvantages
tips
faqs

Goal

Turn short, generic entries into useful, indexable, and differentiated content while avoiding keyword stuffing and repetitive template output.

Core Principle

Keywords are a writing anchor, not a stuffing target.

Use keywords to guide scope and search intent.
Distribute terms naturally across sections.
Prioritize clarity, specificity, and real decision value.

Long-tail keywords (vocabulary and patterns)

Long-tail phrases are specific, multi-word queries (often 3–8 words) with clearer intent than head terms. Use them to anchor keywords, shape FAQ questions, and keep oneLiner / longDescription aligned with how people actually search—without stuffing the same string everywhere.

When to prefer long-tail

The tool serves a narrow audience, regulated workflow, or named integration.
Head terms are generic and would not differentiate the page (AI writer, image generator).
You need commercial or evaluation intent (pricing, migration, compliance, production readiness).

Intent buckets (pick phrases that match real demand)

Intent	Typical long-tail signals	Good for fields
Informational	how to, what is, guide, tutorial, meaning	`longDescription`, `faqs`, `tips`
Commercial	best for, vs, alternative, compare, pricing, ROI	`keywords`, `faqs`, `advantages`
Transactional	free trial, sign up, demo, download, API key	sparingly in copy; often landing CTAs
Navigational	brand + login, brand + docs, official	usually not primary for tool-directory SEO

Read the full file on GitHub · 258 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.

12d ago First seen · 258 lines · 56 tokens per session scan A 8527e13cf402

Subscribe to this mod's changes

seo-keyword-content is a skill published in the GitHub repository sherotree/seo-agent-skills (2 stars, last pushed 25d ago), licensed MIT. It adds 56 tokens to every session and 2,540 once invoked, about $0.0003 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.

Claude Code Marketing and SEO Writing and docs agent-skills ai-agents backlinks cursor dataforseo

gingiris-seo-geo-agent

SEO/GEO Agent Operations SOP v2 — Rebuilt from real-world operations (analook.com 0→launch, GSC incident, DataForSEO monitoring, gingiris.tools post-migration recovery). What's new in v2: • Step-by-step onboarding (Q1→Q6), multiple choice wherever possible — no big forms • Mandatory daily SEO log — first item is…

Gingiris-1031/gingiris-skills · 364 tokens

seo-audit

Use when the user wants to audit, crawl, or diagnose SEO issues on their website. Triggers on: 'audit my site', 'crawl', 'SEO issues', 'broken links', 'missing meta', 'thin content', 'site health', 'technical SEO'.

yagomp/seoagent · 58 tokens

seo-keywords

Use when the user wants keyword research, keyword suggestions, rank tracking, or position monitoring. Triggers on: 'keyword research', 'keyword ideas', 'track rankings', 'rank tracking', 'position tracking', 'SERP', 'search volume', 'keyword difficulty'.