thesmokedev/geo-skills/geo-report

Claude Code and agent skill by thesmokedev/geo-skills

Trust tier 3
  • community
Source check pending

Checking that the SKILL.md file is still in the repository.

Generate a professional, client-facing GEO report combining all audit results into a single deliverable with scores, findings, and prioritized actions

Install

npx vskill@latest install thesmokedev/geo-skills/geo-report

SKILL.md

The same SKILL.md was published earlier as thesmokedev/geo-skills/geo-report.

GEO Client Report Generator

Purpose

This skill aggregates outputs from all GEO audit skills into a single, professional report that can be delivered directly to a client or stakeholder. The report is written for business owners and marketing leaders, not developers — technical findings are translated into business impact and clear action items with priority levels.

How to Use This Skill

  1. Run the following audits first (or use existing report data):
  • geo-platform-optimizer -> GEO-PLATFORM-OPTIMIZATION.md
  • geo-schema -> GEO-SCHEMA-REPORT.md
  • geo-technical -> GEO-TECHNICAL-AUDIT.md
  • geo-content -> GEO-CONTENT-ANALYSIS.md
  • (Optional) geo-llms-txt -> llms.txt assessment
  • (Optional) geo-brand-mentions -> brand authority data
  1. Collect all scores and findings
  2. Calculate the composite GEO Readiness Score
  3. Generate the client report using the template below
  4. Output: GEO-CLIENT-REPORT.md

GEO Readiness Score Calculation

Component Weights
ComponentWeightSource Skill
AI Platform Readiness25%geo-platform-optimizer
Content Quality & E-E-A-T25%geo-content
Technical Foundation20%geo-technical
Schema & Structured Data15%geo-schema
Brand Authority & Entity Presence15%geo-platform-optimizer (entity signals)
Score Formula
GEO Score = (Platform Score * 0.25) + (Content Score * 0.25) + (Technical Score * 0.20) + (Schema Score * 0.15) + (Brand Score * 0.15)

Round to the nearest integer. Cap at 100.

Score Interpretation for Clients
Score RangeLabelClient-Facing Description
85-100ExcellentYour site is well-positioned for AI search. Focus on maintaining and expanding your advantage.
70-84GoodSolid foundation with clear opportunities to improve AI visibility. Targeted optimizations will yield significant results.
55-69ModerateYour site has gaps in AI readiness that competitors may be exploiting. A structured optimization plan will close these gaps.
40-54Below AverageSignificant barriers to AI search visibility exist. Without action, your brand risks being invisible in AI-generated answers.
0-39Needs AttentionCritical AI readiness issues require immediate action. Your competitors are likely capturing the AI search traffic your brand should own.

Report Template

The complete report follows this exact structure. Each section includes instructions on what to write and how.


Section 1: Executive Summary

Write exactly ONE paragraph (4-6 sentences) covering:

  • What was analyzed (domain, number of pages, date of analysis)
  • The overall GEO Readiness Score with context ("XX/100, which places [brand] in the [label] tier")
  • The single most impactful finding (positive or negative)
  • Top 3 priority recommendations in one sentence
  • One sentence on the business impact ("Addressing these recommendations could increase AI-driven traffic by an estimated XX%, representing approximately $X,XXX/month based on current traffic patterns")

Tone: Confident, direct, professional. No jargon. No hedging. Write as a consultant delivering findings, not as a tool generating a report.

Section 2: GEO Readiness Score

Present the overall score prominently:

## GEO Readiness Score: XX/100 — [Label]

Then break down by component in a table:

markdown
| Component | Score | Weight | Weighted Score |
|---|---|---|---|
| AI Platform Readiness | XX/100 | 25% | XX |
| Content Quality & E-E-A-T | XX/100 | 25% | XX |
| Technical Foundation | XX/100 | 20% | XX |
| Schema & Structured Data | XX/100 | 15% | XX |
| Brand Authority | XX/100 | 15% | XX |
| **Overall** | | | **XX/100** |
Section 3: AI Visibility Dashboard

Present per-platform readiness scores:

markdown
## AI Visibility Dashboard
| AI Platform | Readiness Score | Key Gap | Priority Action |
|---|---|---|---|
| Google AI Overviews | XX/100 | [One-line gap] | [One-line action] |
| ChatGPT Web Search | XX/100 | [One-line gap] | [One-line action] |
| Perplexity AI | XX/100 | [One-line gap] | [One-line action] |
| Google Gemini | XX/100 | [One-line gap] | [One-line action] |
| Bing Copilot | XX/100 | [One-line gap] | [One-line action] |

Add a brief paragraph explaining what these scores mean: "These scores reflect how likely your content is to be cited by each AI search platform. A score below 50 indicates significant barriers to citation on that platform."

Section 4: AI Crawler Access Status

Present as a clear table:

markdown
## AI Crawler Access
| AI Crawler | Platform | Status | Impact | Recommendation |
|---|---|---|---|---|
| Googlebot | Google Search + AIO | Allowed/Blocked | Critical | [Action] |
| GPTBot | ChatGPT / OpenAI | Allowed/Blocked | High | [Action] |
| Bingbot | Bing + Copilot + ChatGPT | Allowed/Blocked | High | [Action] |
| PerplexityBot | Perplexity AI | Allowed/Blocked | Medium | [Action] |
| Google-Extended | Gemini Training | Allowed/Blocked | Medium | [Action] |
| ClaudeBot | Anthropic Claude | Allowed/Blocked | Medium | [Action] |
| Applebot-Extended | Apple Intelligence | Allowed/Blocked | Medium | [Action] |

Translate for the client: "Blocking AI crawlers is like closing your store during business hours. If a crawler cannot access your site, the AI platform it powers cannot cite your content. We recommend allowing all major AI crawlers unless you have a specific data licensing concern."

Section 5: Brand Authority Analysis

Present entity presence across platforms:

markdown
## Brand Authority
| Platform | Presence | Status | Impact on AI Visibility |
|---|---|---|---|
| Wikipedia | Yes/No | [Detail] | Very High — strongest entity-recognition signal for ChatGPT |
| Wikidata | Yes/No | [Detail] | High — machine-readable entity data |
| LinkedIn | Yes/No | [Detail] | High — Bing Copilot and ChatGPT signal |
| YouTube | Yes/No | [Detail] | Very High — YouTube mentions are the strongest single measured AI-visibility signal (r=0.737, Ahrefs 75K brands, Jul 2026) |
| Reddit | Yes/No | [Detail] | Medium — consensus-shaping that influences what models SAY; direct citation share collapsed ~60%→10% in Sept 2025 (5WPR, May 2026) |
| Google Knowledge Panel | Yes/No | [Detail] | High — Gemini entity recognition |
| Crunchbase | Yes/No | [Detail] | Medium — entity validation |
| GitHub | Yes/No | [Detail] | Medium — tech brand signal |

Translate for the client: "AI platforms build trust by cross-referencing your brand across multiple authoritative sources. Each platform where your brand has an accurate, consistent presence increases the likelihood of being cited in AI answers."

Section 6: Citability Analysis
Top 5 Most Citable Pages

For each page:

  • URL
  • Why it is citable (structure, depth, E-E-A-T signals)
  • One specific improvement that would make it even more citable
Top 5 Least Citable Pages

For each page:

  • URL
  • Why it is unlikely to be cited (thin content, poor structure, missing signals)
  • Specific rewrite or restructure recommendation

Business impact framing: "Your most citable pages are your best candidates for appearing in AI-generated answers. Improving the 5 least citable pages represents the highest-ROI content investment you can make for AI visibility."

Section 7: Technical Health Summary

Present the key technical findings in business-friendly language:

markdown
## Technical Health
| Area | Status | Business Impact |
|---|---|---|
| Core Web Vitals | Good/Needs Work/Poor | [Impact on user experience and rankings] |
| Server-Side Rendering | Yes/Partial/No | [Impact on AI crawler visibility] |
| Mobile Optimization | Good/Needs Work/Poor | [Impact on Google's mobile-first indexing] |
| Security (HTTPS + Headers) | Good/Needs Work/Poor | [Impact on trust signals] |
| Page Speed | Fast/Average/Slow | [Impact on user experience and crawl budget] |
| IndexNow Protocol | Implemented/Not | [Impact on Bing/ChatGPT indexing speed] |

Critical finding callout: If SSR is missing or partial, highlight this prominently: "Your site uses client-side rendering, which means AI crawlers see an empty page when they visit. This is the single most impactful technical issue for AI search visibility. Until this is resolved, most AI platforms cannot cite your content."

Section 8: Schema & Structured Data
markdown
## Schema & Structured Data
### Current Implementation
| Schema Type | Present | Status | Value |
|---|---|---|---|
| Organization | Yes/No | [Valid/Issues] | Critical — unambiguous entity data |
| Article + Author | Yes/No | [Valid/Issues] | High — E-E-A-T presentation + rich results |
| sameAs (entity links) | Yes/No | [Count] links | Critical — cross-platform entity consistency |
| [Business-specific] | Yes/No | [Valid/Issues] | [Rich-result eligibility] |
| WebSite + SearchAction | Yes/No | [Valid/Issues] | Medium — sitelinks |
| BreadcrumbList | Yes/No | [Valid/Issues] | Low-Medium — navigation context |
Note for framing: schema earns rich results and entity clarity. It does NOT lift AI citations on its own — the Ahrefs controlled study (1,885 pages, May 2026) measured ChatGPT +2.2%, AI Mode +2.4%, AIO -4.6%, all within noise.

If schemas are missing, note: "Ready-to-use structured data code has been prepared and is included in the technical appendix. Your development team can add this to your site with minimal effort."

Section 9: llms.txt Status
markdown
## llms.txt — AI Facts Hedge (Hygiene, Not Visibility)
| File | Status | Recommendation |
|---|---|---|
| /llms.txt | Present/Missing | [Action] |
| /llms-full.txt | Present/Missing | [Action] |

Translate for the client: "llms.txt is a small file (similar in spirit to robots.txt) that states your canonical business facts and key pages in one place. It is a 30-minute hedge against AI systems hallucinating your pricing, locations, or founding date — it is NOT a visibility play. Google stated officially in 2026 that 'you don't need to create new machine readable files... to appear in generative AI search,' and independent studies (Zyppy, Jun 2026; SE Ranking, Nov 2025) found no citation benefit. We include it as cheap hygiene, nothing more."

Section 10: Prioritized Action Plan

This is the most important section of the report. Organize actions by timeline and impact.

Falsifiability fields — required for EVERY action in all three tables below. A recommendation without a falsifiability block is an opinion, not a finding. Directly beneath each action's table entry, include:

  • Observation: the specific audit finding the action rests on (score, URL, or measurement — e.g. "ChatGPT readiness scored 22/100; only 3 of 40 key pages in the Bing index")
  • Failure check: how we would know this fix FAILED — a measurable post-change test with a timeframe (e.g. "30 days after IndexNow setup, Bing still indexes < 50% of key pages")
  • Leading indicator: the earliest watchable signal that the fix is working, before citation metrics move (e.g. "Bing WMT index coverage rising week-over-week in the first 2 weeks")

Worked example (Quick Win):

#ActionImpactEffortPlatforms Affected
1Register Bing Webmaster Tools, submit sitemap, enable IndexNowHigh2-3 hoursChatGPT, Copilot
  • Observation: ChatGPT readiness scored 22/100; site:example.com on Bing returned 3 of 40 key pages — 87% of ChatGPT citations match Bing results, so Bing indexation is the hard gate.
  • Failure check: 30 days after setup, Bing index coverage is still under 50% of key pages, or citation tests across 10 target queries show zero brand URLs in ChatGPT. If so, the problem is crawlability/rendering, not indexation — escalate to the technical audit.
  • Leading indicator: Bing WMT index-coverage count trending up week-over-week within the first 2 weeks, before any citation movement.

This is the start of the file. Read the full SKILL.md on GitHub.

Security

  • Security scanPassed, 95 of 100Pattern checks on the skill's files.
  • Model reviewPassed

Quality evaluation

  • Task evaluationNot runNo evaluation yet. Run one in Skill Studio.

Source

Popularity

Repository stars
25
Repository forks
6
7-day trend score
16

Stars and forks are for the whole GitHub repository, not this skill alone. Not refreshed yet.

Works with

Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.

  • Claude Code
  • Cursor
  • GitHub Copilot
  • Windsurf
  • Codex
  • Gemini CLI
  • Cline
  • Amp
  • Roo Code
  • Goose
  • Continue
  • Kilo Code
  • Junie
  • Trae
  • OpenHands
  • Qwen Code
  • AI Agent
  • Tabnine Chat
  • Sourcegraph Cody
  • Amazon Q
  • Firebase Genkit
  • Sweep
  • Devin
  • Phind
  • Mentat
  • Claude Desktop
  • Aider
  • GPT Pilot
  • Plandex
  • bolt.new
  • v0
  • Replit Agent
  • Anse
  • TypingMind
  • BetterChatGPT
  • LibreChat
  • Warp AI
  • Pieces
  • Fig AI
Embed badge
vskill VERIFIED badge
[![vskill VERIFIED](https://verified-skill.com/api/v1/skills/thesmokedev/geo-skills/geo-report/badge)](https://verified-skill.com/skills/thesmokedev/geo-skills/geo-report)

Something wrong with this skill or its page? Tell us.