Agent skill · Security

blog-geo

AI citation readiness audit as part of SEO, covering classic Google search and AI search surfaces together. Use whenever the user wants their content to rank or be cited in ChatGPT, Perplexity, Claude, Gemini, Copilot, You.com, Google AI Overviews, or Google AI Mode. AI citation optimization audit scoring blog posts for major answer surfaces. Evaluates evidence-backed citability, purpose clarity, entity clarity, structured data, and AI crawler accessibility. Suggests evidence-backed explanations and a 0-100 AI Citation Readiness score. Use when user says "geo", "ai citation", "ai optimization"

AgriciDanielgithub.com/AgriciDanielGitHub ↗
claude-codecopilotMIT
Install
npx skills add AgriciDaniel/claude-blog --skill blog-geo --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 12 KB
Bundled scripts: none
Path: skills/blog-geo/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 1,566
Language: Python

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Blog GEO: AI Citation Optimization Audit Scores blog posts for AI citation readiness across ChatGPT, Perplexity, Claude, Gemini, Copilot, You.com, Google AI Overviews, and Google AI Mode as one SEO workflow, not a separate discipline. Generates a 0-100 internal AI Citation Readiness heuristic with platform-specific recommendations. The score is not a calibrated probability of citation. Google's 2026-05-15 guidance frames generative-AI optimization as SEO: no special markup, llms.txt requirement, or separate GEO/AEO playbook is required for Google visibility. Use GEO/AEO as shorthand labels only. ## Cross-reference This skill covers FLOW surface 3 (AI assistant citations: ChatGPT, Perplexity, Claude, Gemini, Copilot, You.com) and contributes to surface 2 (SERP plus AI Overviews). Surface mapping: `skills/blog/references/flow-alignment.md`. For directly relevant AI-citation prompts (AI-supporting-pages rewrite, evidence-based quality follow-up, ChatGPT discovery, visibility prompts), see `/blog flow optimize`. ## Evidence Discipline Use numeric AI-citation benchmarks only when the report includes a source block with URL, publisher, methodology, sample size, engine or version, query

What's inside
Steps it walks through
  1. Cross-reference
  2. Evidence Discipline
  3. Audit Process
  4. Step 1: Read Content
  5. Step 2: Evidence-Backed Citability (4 pts)
  6. Step 3: Purpose Fit and Reader Utility (3 pts)
  7. Step 4: Entity Clarity (3 pts)
  8. Step 5: Content Structure for Extraction (3 pts)
  9. Step 6: AI Crawler Accessibility (2 pts)
  10. Step 7: Platform-Specific Analysis
  11. Step 8: Strengthen Reusable Evidence
  12. Step 9: Calculate AI Citation Readiness Score (0-100)
  13. Step 10: Generate Report
  14. Optional: Search Performance Context (blog-google)
Commands it runs
python3 scripts/ai_citation_score.py <file> --format markdown
More from claude-blog
All skills →
About this skill
What does the blog-geo skill do?

AI citation readiness audit as part of SEO, covering classic Google search and AI search surfaces together. Use whenever the user wants their content to rank or be cited in ChatGPT, Perplexity, Claude, Gemini, Copilot, You.com, Google AI Overviews, or Google AI Mode. AI citation optimization audit scoring blog posts for major answer surfaces. Evaluates evidence-backed citability, purpose clarity, entity clarity, structured data, and AI crawler accessibility. Suggests evidence-backed explanations and a 0-100 AI Citation Readiness score. Use when user says "geo", "ai citation", "ai optimization"

How do I install it?

Run `npx skills add AgriciDaniel/claude-blog --skill blog-geo --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From AgriciDaniel/claude-blog, a repository with 1,566 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going