agentleFS
Ormus-SolutionsOrmus-Solutions/LibreGEO-Claude-Code/skills/geo-report/SKILL.md

geo-report

Skill1 starsChanged 43 days agoMITView on GitHub

Client-facing GEO report generator that combines audit results into one Markdown deliverable with a GEO readiness score, findings, and an action plan in quick wins, medium-term, and strategic buckets. Use after an audit when the user wants a report to hand to a client or stakeholder.

6 other projects use a version of this, 4 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

4 rules. 2 are common, 2 are distinctive, and 0 are very specific to this project.

  • 2

    Common

    Most of the 5 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run (or collect existing output of) these audits:

    line 15
  2. Distinctive:

    Every finding connects to a specific action

    line 86
  3. Common:

    Avoid: jargon without explanation, hedging, passive voice, excessive caveats

    line 88
  4. Common:

    Use: "Your site [does/does not]...", "We recommend...", "This impacts..."

    line 89

“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

GEO client report generator

Aggregates outputs from the geo-* audit family into one report for business owners and marketing leaders (not developers). Technical findings translate into business impact and prioritized actions.

How to use

  1. Run (or collect existing output of) these audits:
    • 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
  2. Collect all scores and findings
  3. Calculate the composite GEO Readiness Score (formula below)
  4. Generate the report using the 12-section template in template.md
  5. Output: GEO-CLIENT-REPORT.md

GEO readiness score

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)

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

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 structure

The 12-section template lives in template.md. Fill each section with actual audit data.

  1. Executive summary (one paragraph)
  2. GEO readiness score (overall + component table)
  3. AI visibility dashboard (per-platform readiness)
  4. AI crawler access status (robots.txt by bot)
  5. Brand authority analysis (entity presence across platforms)
  6. Citability analysis (top 5 most + least citable pages)
  7. Technical health summary
  8. Schema and structured data
  9. llms.txt status
  10. Prioritized action plan (Quick Wins / Medium-Term / Strategic) — bucket criteria + examples in examples.md
  11. Competitor comparison (if URLs provided)
  12. Appendix (methodology, data sources, glossary)

Tone and formatting

  • Markdown throughout: tables for data, bullets for recommendations, bold sparingly for key terms
  • One blank line between sections; --- separators between major sections
  • All URLs absolute
  • Written for business owners — confident, direct, action-oriented
  • Every finding connects to a specific action
  • Translate technical issues into business outcomes
  • Avoid: jargon without explanation, hedging, passive voice, excessive caveats
  • Use: "Your site [does/does not]...", "We recommend...", "This impacts..."
  • Dollar-value framing: conservative estimates, state assumptions, never guarantee results (examples in examples.md)

Output

GEO-CLIENT-REPORT.md — filled template, 3,000-6,000 words, ready to send to a client without editing, self-contained (no references to other report files).

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.