How to use the GEO Client Report Generator agent skill (geo-report)

What the geo-report skill makes the agent do

The skill aggregates the outputs of other GEO audit skills into a single deliverable called GEO-CLIENT-REPORT.md. It translates technical findings into business impact and prioritized action items for a business owner rather than a developer.

The agent calculates a composite GEO Readiness Score from five weighted components: AI Platform Readiness (25%), Content Quality and E-E-A-T (25%), Technical Foundation (20%), Schema and Structured Data (15%) and Brand Authority and Entity Presence (15%). The score is rounded to the nearest integer and capped at 100, and it is labelled from Excellent (85-100) down to Needs Attention (0-39).

• Executive summary: one paragraph covering the domain analysed, the overall score and the top priorities.
• Per-platform visibility for Google AI Overviews, ChatGPT Web Search, Perplexity AI, Google Gemini and Bing Copilot.
• AI crawler access status for crawlers such as Googlebot, GPTBot, Bingbot, PerplexityBot, ClaudeBot and Applebot-Extended.
• Brand authority across platforms such as Wikipedia, Wikidata, LinkedIn, YouTube, Reddit and Crunchbase.
• Citability analysis of the most and least citable pages, and a technical health summary.

Install the geo-report skill from the ZIP

Download the ZIP for the skill from this page and unzip it. The skill is a folder that contains SKILL.md. Place that folder in one of two locations, depending on how you want to use it.

For all of your projects, put it in your personal skills folder at ~/.claude/skills/. To use it only inside one project, put it in that project's .claude/skills/ folder. If you use the Claude apps instead of Claude Code, you can upload the skill under Settings → Capabilities → Skills.

• Personal install: ~/.claude/skills/geo-report/ (available across projects).
• Project install: .claude/skills/geo-report/ inside your project folder (available only there).
• Claude apps: Settings → Capabilities → Skills, then upload the skill.

Run the underlying audits before you ask for a report

The report depends on the output files of other skills. Run these first, or supply existing report data. The skill expects each audit to write a specific file.

The four required audits are geo-platform-optimizer (GEO-PLATFORM-OPTIMIZATION.md), geo-schema (GEO-SCHEMA-REPORT.md), geo-technical (GEO-TECHNICAL-AUDIT.md) and geo-content (GEO-CONTENT-ANALYSIS.md). The optional inputs are geo-llmstxt (an llms.txt assessment) and geo-brand-mentions (brand authority data).

If the underlying audits have not been run, do not use this skill. The scores depend on their outputs and can be invented or inaccurate without them.

• Required: geo-platform-optimizer, geo-schema, geo-technical, geo-content.
• Optional: geo-llmstxt, geo-brand-mentions.
• The skill's output file is GEO-CLIENT-REPORT.md.

Trigger the skill with a natural request

You do not need a special command. Describe what you want in plain language and mention the client report or the audit results. Agents load a skill when the request matches its description, which covers generating a professional, client-facing GEO report with scores, findings and prioritized actions.

Make the request specific about the site and the files. This helps the agent find the audit outputs in your project folder.

• "Use the geo-report skill to combine the audit files in this folder into a client report."
• "Create a GEO client report for example.com with scores, findings and priority actions."
• "Write the executive summary and GEO Readiness Score for the client using the existing audit reports."

Read the report and check it before you send it

The report follows a fixed template: executive summary, GEO Readiness Score table, AI Visibility Dashboard, AI Crawler Access, Brand Authority, Citability Analysis, Technical Health and further sections. Each section is written in a client-friendly tone.

Before you deliver it, check the numbers against the underlying audit files. The template asks for estimated traffic and revenue impact figures, which the skill does not ground in real analytics, so remove or label any such estimate that you cannot support.

• Compare each component score with its source audit file.
• Confirm the crawler status rows match your robots.txt and server settings.
• Remove or qualify any estimated percentage or dollar impact figure.

Safety notes: scripts and network access

According to the skill's listing, it does not run scripts. It does use the network: its allowed tools include WebFetch and Bash, so check what the agent does during a run, and review the files it reads and writes.

The skill writes its report to a Markdown file in your working area. Review the output before sharing it with a client, because the agent generates the wording from the audit data it reads.

• Scripts: none, according to the listing.
• Network: yes. The skill's allowed tools include WebFetch.
• Files it writes: GEO-CLIENT-REPORT.md.

Tips for better client reports

Run all four required audits on the same version of the site so the scores describe the same pages. Keep the audit files in one folder so the agent reads a consistent set of inputs.

If a component is missing, say so in the report rather than estimating it. A clear gap is more useful to a client than an invented score.

• Use the same site snapshot for every audit.
• Include the optional geo-llmstxt and geo-brand-mentions audits when you have them.
• Edit the wording into your own voice before sending the report.