Geo Fundamentals
wasp-lang/wasp
Generative Engine Optimization for AI search engines (ChatGPT, Claude, Perplexity).
AI citation readiness audit as part of SEO, covering classic Google search and AI search surfaces together.
Install Blog Geo
$ npx skills add AgriciDaniel/claude-blog --skill blog-geo -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install AgriciDaniel/claude-blog blog-geo --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/AgriciDaniel/claude-blog.git skills-src && mkdir -p .claude/skills && cp -r skills-src/brain/.raw/sources/claude-blog-skill/skills/blog-geo .claude/skills/blog-geo && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "blog-geo" agent skill from https://github.com/AgriciDaniel/claude-blog/tree/main/brain/.raw/sources/claude-blog-skill/skills/blog-geo into .claude/skills/blog-geo/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "blog-geo", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/AgriciDaniel/claude-blog/tree/main/brain/.raw/sources/claude-blog-skill/skills/blog-geoType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add AgriciDaniel/claude-blog --skill blog-geo -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install AgriciDaniel/claude-blog blog-geo --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/AgriciDaniel/claude-blog.git skills-src && mkdir -p .agents/skills && cp -r skills-src/brain/.raw/sources/claude-blog-skill/skills/blog-geo .agents/skills/blog-geo && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "blog-geo" agent skill from https://github.com/AgriciDaniel/claude-blog/tree/main/brain/.raw/sources/claude-blog-skill/skills/blog-geo into .agents/skills/blog-geo/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "blog-geo", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add AgriciDaniel/claude-blog --skill blog-geo -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install AgriciDaniel/claude-blog blog-geo --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/AgriciDaniel/claude-blog.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/brain/.raw/sources/claude-blog-skill/skills/blog-geo .cursor/skills/blog-geo && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "blog-geo" agent skill from https://github.com/AgriciDaniel/claude-blog/tree/main/brain/.raw/sources/claude-blog-skill/skills/blog-geo into .cursor/skills/blog-geo/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "blog-geo", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/AgriciDaniel/claude-blog.git --path brain/.raw/sources/claude-blog-skill/skills/blog-geo--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add AgriciDaniel/claude-blog --skill blog-geo -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install AgriciDaniel/claude-blog blog-geo --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/AgriciDaniel/claude-blog.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/brain/.raw/sources/claude-blog-skill/skills/blog-geo .gemini/skills/blog-geo && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "blog-geo" agent skill from https://github.com/AgriciDaniel/claude-blog/tree/main/brain/.raw/sources/claude-blog-skill/skills/blog-geo into .gemini/skills/blog-geo/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "blog-geo", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install AgriciDaniel/claude-blog blog-geoInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add AgriciDaniel/claude-blog --skill blog-geo -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/AgriciDaniel/claude-blog.git skills-src && mkdir -p .github/skills && cp -r skills-src/brain/.raw/sources/claude-blog-skill/skills/blog-geo .github/skills/blog-geo && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "blog-geo" agent skill from https://github.com/AgriciDaniel/claude-blog/tree/main/brain/.raw/sources/claude-blog-skill/skills/blog-geo into .github/skills/blog-geo/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "blog-geo", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add AgriciDaniel/claude-blog --skill blog-geo -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install AgriciDaniel/claude-blog blog-geo --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/AgriciDaniel/claude-blog.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/brain/.raw/sources/claude-blog-skill/skills/blog-geo .opencode/skills/blog-geo && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "blog-geo" agent skill from https://github.com/AgriciDaniel/claude-blog/tree/main/brain/.raw/sources/claude-blog-skill/skills/blog-geo into .opencode/skills/blog-geo/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "blog-geo", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
blog-geo- GitHub stars
- 2.3k
- Token cost
- ~2.9k tokens
- SKILL.md length
- 1,180 words
- Files
- 1
- Skills in repo
- 39
- Repo updated
- First seen
- Licence
- MIT
At a glance
AI citation readiness audit as part of SEO, covering classic Google search and AI search surfaces together.
- Works in 10 steps: Read Content → Passage-Level Citability (4 pts) → Q&A Formatting (3 pts) → …
- The user wants their content to rank
- SKILL.md covers Cross-reference, Evidence Discipline and Audit Process
- Calls python3
What it does
Blog Geo is an agent skill from AgriciDaniel/claude-blog. 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 passage-level citability, Q&A formatting, entity clarity, structured data, and AI crawler accessibility. Generates citation capsules and a 0-100 AI Citation…
Its SKILL.md is about 2.9k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Marketing & SEO, covering AI search optimization and Web search. It works with OpenAI and Perplexity. The repository describes itself as: Claude Code blog skill suite: 30 sub-skills, 5 agents, 5-gate v1.9.0 Blog Delivery Contract, dual-optimized for Google rankings and AI citations. Active development at… The licence is MIT.
When your agent uses it
- The user wants their content to rank
- Be cited in ChatGPT
- Google AI Overviews
- Ai optimization
Example prompts
- “ai citation”
- “ai optimization”
- “citation audit”
- “/blog-geo”
Requirements
- Python 3
Workflow steps
10 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 2500d4c. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
python3
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Blog Geo loads about 2.9k tokens when it runs. Until then it costs about 167 tokens; SKILL.md has 1,180 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from AgriciDaniel/claude-blog at commit 2500d4c, republished under its MIT licence (© AgriciDaniel). 1,180 words, ~2,885 tokens.
Download SKILL.mdSave it as
.claude/skills/blog-geo/SKILL.md (or your agent's skills folder).- name
- blog-geo
- description
- 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 passage-level citability, Q&A formatting, entity clarity, structured data, and AI crawler accessibility. Generates citation capsules and a 0-100 AI Citation Readiness score. Use when user says "geo", "ai citation", "ai optimization", "citation audit", "aeo", "perplexity optimization", "chatgpt citation".
- user-invokable
- true
- argument-hint
- <file-path>
- license
- MIT
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 citation capsules and a 0-100 AI Citation Readiness score with platform-specific recommendations.
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-prompt, ai-detector-test, 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 class, retrieval date, and expiry date. If any field is missing, label the benchmark as directional or remove the number. Default heuristics:
- Self-contained 120-180 word answer passages are a practitioner heuristic.
- Comparison tables with semantic headers may improve extractability, but do not cite an uplift without a dated source block.
- AI Overviews coverage is methodology-dependent: cite a dated range, not a fixed point.
Audit Process
Step 1: Read Content
Extract from the blog post:
- Full content text and word count
- Heading structure (H1, H2, H3 hierarchy)
- Individual paragraphs and their word counts
- FAQ sections (if present)
- Schema markup (JSON-LD, microdata, RDFa)
- robots.txt mentions or meta robots directives
- Any TL;DR or summary boxes
- Comparison tables and their HTML structure
- Numbered/ordered lists
- Definition-style formatting
Step 2: Passage-Level Citability (4 pts)
Check each section between headings for AI-extractable passages:
| Check | Criteria |
|---|---|
| Word count | Each section contains 120-180 word self-contained passages |
| Context independence | Each passage makes sense extracted from surrounding context |
| Claim structure | Passages contain: specific claim + supporting evidence + source attribution |
| Completeness | Passage answers a question without requiring reader to read adjacent sections |
Scoring: Count passages meeting all criteria vs total sections.
- 4 pts: 80%+ sections have citable passages
- 3 pts: 60-79%
- 2 pts: 40-59%
- 1 pt: 20-39%
- 0 pts: <20%
Step 3: Q&A Formatting (3 pts)
Check heading format and answer structure:
| Check | Criteria |
|---|---|
| Question headings | 60-70% of H2s are phrased as questions |
| Answer-first format | Opening paragraph under each H2 provides a direct answer |
| FAQ section | Dedicated FAQ section with structured question-answer pairs |
Scoring:
- 3 pts: All three criteria met
- 2 pts: Two criteria met
- 1 pt: One criterion met
- 0 pts: None met
Step 4: Entity Clarity (3 pts)
Check topic consistency and disambiguation:
| Check | Criteria |
|---|---|
| Canonical topic | One unambiguous primary topic per page |
| Consistent naming | Same entity name used throughout (no confusing synonyms) |
| Intro statement | Clear topic statement in the introduction paragraph |
| Title-content match | Title accurately reflects the content focus |
Scoring:
- 3 pts: All four criteria met
- 2 pts: Three criteria met
- 1 pt: One or two criteria met
- 0 pts: None met
Step 5: Content Structure for Extraction (3 pts)
Check for AI-extractable content patterns:
| Check | Criteria |
|---|---|
| TL;DR box | 40-60 word standalone summary present at top |
| Comparison tables | Tables with semantic headers such as <thead> or clear column labels |
| Ordered lists | Numbered lists for processes and step-by-step instructions |
| Definition formatting | Key terms formatted with clear definition patterns |
| Citation capsules | 40-60 word definitive statements in each major section |
Scoring:
- 3 pts: 4-5 elements present
- 2 pts: 3 elements present
- 1 pt: 1-2 elements present
- 0 pts: None present
Step 6: AI Crawler Accessibility (2 pts)
Check technical requirements for AI crawler indexing:
| Check | Criteria |
|---|---|
| Static HTML | Content rendered in static HTML, not behind JavaScript |
| Google visibility | Normal crawlability and indexability for Googlebot. No special GEO/AEO file or markup is required for Google AI features |
| Non-Google AI crawlers | If the site wants visibility in non-Google answer engines, check robots.txt treatment for GPTBot, ChatGPT-User, ClaudeBot, PerplexityBot, and related documented crawlers |
| Schema in HTML | Schema markup in static HTML, not JS-injected |
| Page size | Reasonable page size within AI crawler limits |
Scoring:
- 2 pts: Google crawlability/indexability is clean, and selected non-Google crawler policies match the site's stated goals
- 1 pt: Google is indexable but one selected non-Google crawler or rendering check needs review
- 0 pts: Google crawling/indexing is blocked or multiple selected crawlers are unintentionally blocked
Show full SKILL.md (476 more words)Show less
Step 7: Platform-Specific Analysis
Evaluate the post for each AI platform's citation preferences:
ChatGPT
- Favors "Best X" listicles (43.8% of citations)
- Prefers well-cited, authoritative content
- Recency matters: recent updates get priority
- Domain authority influences citation likelihood
Perplexity
- Often favors fresh, source-dense, community-validated content. Verify with current logs or tooling before claiming a citation window.
Google AI Overviews
- Follow Google's normal SEO guidance: make content helpful, crawlable, indexable, and eligible for snippets. No special GEO/AEO markup or llms.txt is required for Google visibility.
- Prefers content that already ranks well organically, but verify any numeric claims with dated source blocks.
Google AI Mode
- Treat separately from AI Overviews in reports. Emphasize normal Search eligibility, clear page purpose, accessible text, and consistency between visible content and structured data.
Claude, Gemini, Copilot, and You.com
- Evaluate content clarity, source accessibility, freshness, and whether robots policy intentionally allows or blocks each crawler where documented.
- Use engine-specific recommendations only when current docs, logs, or test results are available.
For each platform, provide:
- Current citability rating (High / Medium / Low)
- Specific improvements to increase citation likelihood
- Content format recommendations
Step 8: Generate Citation Capsules
For each H2 section in the post, write a citation capsule:
- Length: 40-60 words, self-contained
- Structure: Specific claim + data point + source attribution
- Purpose: A passage AI could directly quote as a citation
- Format: Present as a suggested addition the author can embed
Example:
According to [Source], [specific claim with number]. This represents
[context/comparison], making it [significance]. [Supporting detail
that reinforces the claim].Generate one capsule per H2 section. Label each with the section heading it belongs under.
Step 9: Calculate AI Citation Readiness Score (0-100)
Map the 15-point subcategory scores to a 0-100 display score:
| Category | Raw Points | Display Weight | Max Display Score |
|---|---|---|---|
| Passage-Level Citability | /4 | x6.75 | 27 |
| Q&A Formatting | /3 | x6.67 | 20 |
| Entity Clarity | /3 | x6.67 | 20 |
| Content Structure | /3 | x6.67 | 20 |
| AI Crawler Accessibility | /2 | x6.5 | 13 |
| Total | /15 | 100 |
Rating thresholds:
- 90-100: Excellent: highly citable by AI systems
- 70-89: Good: citable with minor improvements
- 50-69: Needs Work: significant gaps in citability
- Below 50: Poor: major restructuring needed
Step 10: Generate Report
Output the following report:
## AI Citation Readiness Report: [Title]
**AI Citation Readiness Score: [X]/100**: [Rating]
### Score Breakdown
| Category | Raw | Display | Max |
|----------|-----|---------|-----|
| Passage-Level Citability | X/4 | X | 27 |
| Q&A Formatting | X/3 | X | 20 |
| Entity Clarity | X/3 | X | 20 |
| Content Structure | X/3 | X | 20 |
| AI Crawler Accessibility | X/2 | X | 13 |
| **Total** | **X/15** | **X** | **100** |
### Per-Section Citability Analysis
| Section (H2) | Word Count | Self-Contained | Claim+Evidence | Citable |
|---------------|-----------|----------------|----------------|---------|
| [heading] | [N] | Yes/No | Yes/No | Yes/No |
### Platform-Specific Optimization
#### ChatGPT
- [specific recommendations]
#### Perplexity
- [specific recommendations]
#### Google AI Overviews
- [specific recommendations]
#### Google AI Mode
- [specific recommendations]
#### Claude / Gemini / Copilot / You.com
- [specific recommendations]
### Generated Citation Capsules
#### [H2 Section 1]
> [40-60 word citation capsule]
#### [H2 Section 2]
> [40-60 word citation capsule]
### Technical Recommendations
- [ ] [Technical fix with specifics]
### Priority Action Items
1. [Most impactful improvement]
2. [Second most impactful]
3. [Third most impactful]
Run `/blog analyze <file>` for full content quality scoring.Optional: Search Performance Context (blog-google)
If blog-google credentials include Tier 1 (GSC) and the post has a published URL:
- Query GSC by page and query dimensions, then filter rows to the URL:
python3 skills/blog-google/scripts/run.py gsc_query --property <property> --dimensions query,page --json - Add to platform-specific analysis:
- Current impressions, clicks, CTR, average position
- Search queries driving traffic to this URL
- Check indexation:
python3 skills/blog-google/scripts/run.py gsc_inspect <url> --json - Report indexation status, canonical selection, mobile usability.
- If skipped, report
SKIPPED: credentials unavailableorSKIPPED: unpublished URL.
Optional: AI Citation Probability Score
For a per-engine likelihood that the post gets cited by AI answer engines (distinct
from the 15-point AI Citation Readiness category scored by /blog analyze), run:
python3 scripts/ai_citation_score.py <file> --format markdownIt returns a 0-100 overall score plus per-engine subscores for Google AI Overview, Perplexity, and ChatGPT, a factor breakdown, and up to three highest-impact fixes.
© AgriciDaniel, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in brain/.raw/sources/claude-blog-skill/skills/blog-geo of AgriciDaniel/claude-blog.
Open the folder on GitHubat commit 2500d4c
Compare with similar skills
Blog Geo next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Blog Geo this skillAgriciDaniel/claude-blog | 2.3k | — | ~2.9k | Automated safety check: Pass | MIT | |
| Geo Fundamentalswasp-lang/wasp | 19k | 9 repos | ~861 | Automated safety check: Pass | MIT | |
| Marketing OsYuzzyuk/marketing-os | 540 | — | ~2.5k | Automated safety check: Pass | MIT | |
| Geoliangdabiao/GEO-Content-Optimizer-Skill | 205 | 1 repos | ~2.3k | Automated safety check: Notes | MIT | |
| Geo Optimizerliangdabiao/GEO-Content-Optimizer-Skill | 205 | — | ~1.1k | Automated safety check: Pass | None | |
| SEO Auditshadcn-labs/agentcn | 490 | — | ~598 | Automated safety check: Pass | MIT |
Similar skills
Marketing Os
Yuzzyuk/marketing-os
A complete marketing department in one skill. An agent skill from Yuzzyuk/marketing-os.
Geo
liangdabiao/GEO-Content-Optimizer-Skill
完整的 GEO（生成式引擎优化）服务流水线：给一个产品官网 URL 和介绍材料， 做站点诊断与 AI 答案采样、生成带验收标准的执行工单、产出可直接部署的资产 （llms.txt / JSON-LD / 定义块 / FAQ / 内容大纲与初稿）、自动验收工单是否闭环、 并打包成可直接发给客户的交付物。可按周期复跑，做长期 GEO 运营与月报。
Geo Optimizer
liangdabiao/GEO-Content-Optimizer-Skill
GEO (Generative Engine Optimization) 全流程优化工具。帮助品牌内容被 ChatGPT、Perplexity、Gemini 等 AI 搜索引擎引用。
SEO Audit
shadcn-labs/agentcn
How to present the deterministic AI-SEO audit returned by auditpage.
AI Traffic Tracking
kostja94/marketing-skills
When the user wants to track AI search traffic in GA4 or GSC.
More from AgriciDaniel/claude-blog
All 39 skills in this repoBlog Google
AgriciDaniel/claude-blog
Google API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity…
Blog Audio
AgriciDaniel/claude-blog
Generate audio narration of blog posts using Google Gemini TTS.
Blog Flow
AgriciDaniel/claude-blog
FLOW framework integration for bloggers. An agent skill from AgriciDaniel/claude-blog.
Blog Notebooklm
AgriciDaniel/claude-blog
Query Google NotebookLM notebooks for source-grounded, citation-backed answers from user-uploaded documents.
Blog Image
AgriciDaniel/claude-blog
AI image generation and editing for blog content powered by Gemini via MCP.
Blog Cluster
AgriciDaniel/claude-blog
Semantic topic cluster planning and automated execution engine for claude-blog.
Related
Works with
Categories
Questions about Blog Geo
What does Blog Geo do?
AI citation readiness audit as part of SEO, covering classic Google search and AI search surfaces together. Blog Geo is an agent skill from AgriciDaniel/claude-blog. AI citation readiness audit as part of SEO, covering classic Google search and AI search surfaces together.
When should I use Blog Geo?
Blog Geo fits situations like: the user wants their content to rank; be cited in ChatGPT; google AI Overviews; ai optimization.
How do I install Blog Geo in Claude Code?
Run `npx skills add AgriciDaniel/claude-blog --skill blog-geo -a claude-code`. Or copy the skill folder (brain/.raw/sources/claude-blog-skill/skills/blog-geo in AgriciDaniel/claude-blog) into .claude/skills/blog-geo in your project. Claude Code loads it when a task matches its description.
How do I install Blog Geo in Codex?
Run `npx skills add AgriciDaniel/claude-blog --skill blog-geo -a codex`. Or copy the skill folder (brain/.raw/sources/claude-blog-skill/skills/blog-geo in AgriciDaniel/claude-blog) into .agents/skills/blog-geo in your project. Codex loads it when a task matches its description.
Can I use Blog Geo in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add AgriciDaniel/claude-blog --skill blog-geo -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/blog-geo, .gemini/skills/blog-geo, .github/skills/blog-geo and .opencode/skills/blog-geo in your project.
What does Blog Geo need to run?
Going by SKILL.md and its folder, Blog Geo needs the command-line tools its instructions call (python3). Our summary lists: Python 3.
Does Blog Geo access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Blog Geo safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Blog Geo use?
Blog Geo is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Blog Geo use?
About 2.9k tokens (SKILL.md is roughly 12k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Blog Geo?
Skills that share tags, products or a category with Blog Geo: Geo Fundamentals (wasp-lang/wasp, 19k stars), Marketing Os (Yuzzyuk/marketing-os, 540 stars), Geo (liangdabiao/GEO-Content-Optimizer-Skill, 205 stars) and Geo Optimizer (liangdabiao/GEO-Content-Optimizer-Skill, 205 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Blog Geo?
AgriciDaniel (a GitHub user) maintains it in AgriciDaniel/claude-blog, which has 2,348 GitHub stars. The repository holds 39 skills in this directory. The repository was last updated on October 9, 2026.
Source: AgriciDaniel/claude-blog on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.