Geo report pdf
Generate a professional PDF report from GEO audit data using ReportLab. Creates a polished, client-ready PDF with score gauges, bar charts, platform readiness visualizations, color-coded tables, and prioritized action plans.From its SKILL.md
npx -y skills add techhorizonlabs/thl-open --skill geo-report-pdfAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 14 stars14 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
- runs commandsInstructs the agent to run 5 commands, including `pip install reportlab` and 4 more.
SKILL.md
6.6 KB, ~1.6k tokens by cl100k_base, as published. Nobody here has run it
GEO PDF Report Generator
Purpose
This skill generates a professional, visually polished PDF report from GEO audit data. The PDF includes score gauges, bar charts, platform readiness visualizations, color-coded tables, and a prioritized action plan — ready to deliver directly to clients.
Two PDF paths — pick one. For a branded, client-ready deliverable, prefer the TypeScript
tools/audit-report-kit(react-pdf, THL brand tokens, provenance tags,—for null scores, compile-checked JSON-LD alongside). The ReportLab script below is the lightweight Python path when you don't want a Node toolchain. They render the same audit JSON; don't run both.
Prerequisites
- ReportLab must be installed:
pip install reportlab - The Python PDF generation script lives at
../geo/scripts/generate_pdf_report.py(shared with thegeoumbrella skill). Run it from the repo root:python3 skills/geo/scripts/generate_pdf_report.py <data.json> <out.pdf>. - Run a full GEO audit first (using
geo-audit) to have data to include in the report
How to Generate a PDF Report
Step 1: Collect Audit Data
After running a full /geo-audit, collect all scores, findings, and recommendations into a JSON structure. The JSON data must follow this schema:
{
"url": "https://example.com",
"brand_name": "Example Company",
"date": "2026-02-18",
"geo_score": 65,
"scores": {
"ai_citability": 62,
"brand_authority": 78,
"content_eeat": 74,
"technical": 72,
"schema": 45,
"platform_optimization": 59
},
"platforms": {
"Google AI Overviews": 68,
"ChatGPT": 62,
"Perplexity": 55,
"Gemini": 60,
"Bing Copilot": 50
},
"executive_summary": "A 4-6 sentence summary of the audit findings...",
"findings": [
{
"severity": "critical",
"title": "Finding Title",
"description": "Description of the finding and its impact."
}
],
"quick_wins": [
"Action item 1",
"Action item 2"
],
"medium_term": [
"Action item 1",
"Action item 2"
],
"strategic": [
"Action item 1",
"Action item 2"
],
"crawler_access": {
"GPTBot": {"platform": "ChatGPT", "status": "Allowed", "recommendation": "Keep allowed"},
"ClaudeBot": {"platform": "Claude", "status": "Blocked", "recommendation": "Unblock for visibility"}
}
}
Step 2: Write JSON Data to a Temp File
Write the collected audit data to a temporary JSON file:
# Write audit data to temp file
cat > /tmp/geo-audit-data.json << 'EOF'
{ ... audit JSON data ... }
EOF
Step 3: Generate the PDF
Run the PDF generation script:
python3 skills/geo/scripts/generate_pdf_report.py /tmp/geo-audit-data.json GEO-REPORT-[brand].pdf
The script will produce a professional PDF report with:
- Cover Page — Brand name, URL, date, overall GEO score with visual gauge
- Executive Summary — Key findings and top recommendations
- Score Breakdown — Table and bar chart of all 6 scoring categories
- AI Platform Readiness — Visual horizontal bar chart per platform with scores
- AI Crawler Access — Color-coded table (green=allowed, red=blocked)
- Key Findings — Severity-coded findings list (critical/high/medium/low)
- Prioritized Action Plan — Quick wins, medium-term, and strategic initiatives
- Appendix — Methodology, data sources, and glossary
Step 4: Return the PDF Path
After generation, tell the user where the PDF was saved and its file size.
Complete Workflow Example
When the user runs this skill, follow this exact sequence:
-
Check for existing audit data — Look for recent GEO audit reports in the current directory:
GEO-CLIENT-REPORT.mdGEO-AUDIT-REPORT.md- Or any
GEO-*.mdfiles from a recent audit
-
If no audit data exists — Tell the user to run
/geo-audit <url>first, then come back for the PDF. -
If audit data exists — Parse the markdown report to extract:
- Overall GEO score
- Category scores (citability, brand authority, content/E-E-A-T, technical, schema, platform)
- Platform readiness scores (Google AIO, ChatGPT, Perplexity, Gemini, Bing Copilot)
- AI crawler access status
- Key findings with severity levels
- Quick wins, medium-term, and strategic action items
- Executive summary
-
Build the JSON — Structure all data into the JSON schema shown above.
-
Write JSON to temp file — Save to
/tmp/geo-audit-data.json -
Run the PDF generator:
python3 skills/geo/scripts/generate_pdf_report.py /tmp/geo-audit-data.json "GEO-REPORT-[brand_name].pdf" -
Report success — Tell the user the PDF was generated, its location, and file size.
If the User Provides a URL
If the user runs /geo-report-pdf https://example.com with a URL:
- First run a full audit: invoke the
geo-auditskill for that URL - Then collect all the audit data from the generated report files
- Generate the PDF as described above
Parsing Markdown Audit Data
When extracting data from existing GEO markdown reports, look for these patterns:
- GEO Score: Look for "GEO Score: XX/100" or "Overall: XX/100" or "GEO Readiness Score: XX"
- Category Scores: Look for score tables with columns like "Component | Score | Weight"
- Platform Scores: Look for tables with "Google AI Overviews", "ChatGPT", "Perplexity", etc.
- Crawler Status: Look for tables with "Allowed" or "Blocked" status for crawlers like GPTBot, ClaudeBot
- Findings: Look for sections titled "Key Findings", "Critical Issues", "Recommendations"
- Action Items: Look for sections titled "Quick Wins", "Action Plan", "Recommendations"
Notes
- If ReportLab is not installed, run:
pip install reportlab - The PDF is designed for US Letter size (8.5" x 11")
- Color palette: Navy primary (#1a1a2e), Blue accent (#0f3460), Coral highlight (#e94560), Green success (#00b894)
- Each page has a header line, page numbers, "Confidential" watermark, and generation date
- Score gauges use traffic-light colors: green (80+), blue (60-79), yellow (40-59), red (below 40)
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.
Gives 0 of the 12 instructions most docs writing skills give in ~1.6k tokens
Counted across 1,951 of the 3,904 authors here whose files we hold, read 2026-09-06
- Use third-person for skill descriptionsin 54 of 1951, across 35 files
- Start descriptions with Use whenin 43 of 1951, across 29 files
- Run baseline scenarios before writing any skillin 40 of 1951, across 26 files
- Use active voicein 40 of 1951, across 36 files
- Map file responsibilities before defining tasksin 36 of 1951, across 29 files
- Use checkbox syntax for tracking stepsin 35 of 1951, across 27 files
- Ask one question at a timein 35 of 1951
- Offer execution options after saving the planin 33 of 1951, across 24 files
- Include complete code in every stepin 33 of 1951, across 27 files
- Design units with clear boundaries and interfacesin 31 of 1951, across 23 files
- Announce the skill usage at the startin 30 of 1951
- Verify agent compliance after adding the skillin 29 of 1951, across 17 files
Said here and by no other author read
- Run geo-audit before generating the PDF
- Collect audit data into the required JSON schema
- Report the saved PDF location and file size
- Parse existing markdown audit reports for data extraction
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.