Agent skill · Audited from source
geo-report-pdf
skill · zubair-trabzada/geo-seo-claudeMIT licenceAudited 30 Oct 2026 · source a1519a410207
Is it safe? Yes — SAFE, grade B (89/100). We read this skill's source at commit a1519a410207 and found no filesystem, network or shell access and no hard-coded secrets. What it does: Generate a professional PDF report from a GEO audit using pandoc + Chrome headless. Converts GEO-AUDIT-REPORT.md into a styled, client-ready PDF with a cover page, color-coded score tables, severity-tagged findings, and…
Cite
Cite this page
ModelsAtlas. “geo-report-pdf (zubair-trabzada/geo-seo-claude)”. Retrieved 30 Oct 2026. https://modelsatlas.com/skills/zubair-trabzada/geo-report-pdf
Trust audit
Audit 0.4.1 · source read 30 Oct 2026
SAFE means nothing in the source contradicts what the skill says it does. Grade B is shared by 16,667 of 17,602 audited skills.
What the source does
- FilesystemNone observedNo reads or writes in the source
- NetworkNone observedNo outbound calls in the source
- ShellNone observedNo commands run in the source
- DependenciesPinnedNothing floats
- SecretsNone foundNo keys in source
Five audit layers
| Layer | What we check | Result | Findings |
|---|---|---|---|
L0 Provenance | Repo owner, licence, archive status, activity | PASS | 0 |
L1 Static source | Secrets, path traversal, supply chain, hidden code | NA | 0 |
L2 Instructions | Prompt injection, authority framing, hidden directives | PASS | 0 |
L3 Inventory | The files and declarations match the source | PASS | 0 |
L4 Sandbox | Run in isolation and watch behaviour | SKIPPED why | 0 |
Gates applied: no behavioural pass.
Findings (0)
No findings at any severity. We re-audit when the source changes.
Audit 0.4.1 · source sha a1519a410207 · 30 Oct 2026Report an issue or request a re-scan
Provenance
Who published it, and what the verdict is pinned to
- Publisherzubair-trabzada GitHub userOwner of the repository this skill is read from
- Source folderzubair-trabzada/geo-seo-claude/skills/geo-report-pdfThe exact folder we audited
- LicenceMITAs the repository states it
- Commit pinned for this verdicta1519a410207A new audit runs when the source changes
- Repository statusNot archivedPushed today
- Sandboxed runNot runSkills are read, not executed; layer L4 is skipped
What it tells the agent
Full source on GitHub ↗Its description: Generate a professional PDF report from a GEO audit using pandoc + Chrome headless. Converts GEO-AUDIT-REPORT.md into a styled, client-ready PDF with a cover page, color-coded score tables, severity-tagged findings, and…
--- name: geo-report-pdf description: Generate a professional PDF report from a GEO audit using pandoc + Chrome headless. Converts GEO-AUDIT-REPORT.md into a styled, client-ready PDF with a cover page, color-coded score tables, severity-tagged findings, and a 90-day roadmap. version: 2.0.0 author: geo-seo-claude tags: [geo, pdf, report, client-deliverable, professional] allowed-tools: Read, Grep, Glob, Bash, Write --- # GEO PDF Report Generator (pandoc pipeline) ## Prerequisites - **pandoc** — `brew install pandoc` - **Google Chrome** — must be installed at `/Applications/Google Chrome.app/` No Python dependencies. No ReportLab. No JSON data wrangling. ## How It Works 1. Read `GEO-AUDIT-REPORT.md` in the current directory (created by `/geo audit`) 2. Extract cover metadata from the report (brand name, domain, GEO score, date, locations) 3. Run `pandoc` with the bundled CSS + HTML template to produce a self-contained `GEO-REPORT.html` 4. Run Chrome headless to print the HTML to `GEO-REPORT.pdf` The pandoc template (`~/.claude/skills/geo/templates/geo-report-template.html`) injects: - A full-bleed dark navy cover section with the GEO score badge - Per-section cover metadata (date, business type, locations, platform) - JavaScript that runs inside Chrome before printing to color-code score cells and severity-tag finding sections ## Workflow ### Step 1: Check for audit report Look for `GEO-AUDIT-REPORT.md` in the current directory. If absent, tell the user to run `/geo audit <url>` first. ### Step 2: Extract cover metadata from the report Read the top of `GEO-AUDIT-REPORT.md` and extract: | Field | Where to find it | |---|---| | `brand_name` | First H1 title (after "GEO Audit Report:") | | `domain` | Second bold line (e.g. `**Domain:** alexamediasolutions.com`) | | `geo_score` | Line matching `## Overall GEO Score: XX / 100` | | `score_label` | Word after the score on that same line (e.g. "Poor", "Fair", "Good") | | `date` | `**Audit Date:**` line | | `business_type` | `**Business Type:**` line | | `locations` | `**Locations:**` line | | `platform` | `**CMS:**` line | ### Step 3: Run pandoc ```bash pandoc GEO-AUDIT-REPORT.md \ --to html5 \ --standalone \ --embed-resources \ --template ~/.claude/skills/geo/templates/geo-report-template.html \ --css ~/.claude/skills/geo/templates/geo-report-style.css \ --metadata title="GEO Audit Report — <brand_name>" \ --metadata brand_name="<brand_name>" \ --metadata domain="<domain>" \ --metadata geo_score="<geo_score>" \ --metadata score_label="<score_label>" \ --metadata date="<date>" \ --metadata business_type="<business_type>" \ --metadata locations="<locations>" \ --metadata platform="<platform>" \ -o GEO-REPORT.html ``` Replace `<field>` placeholders with values extracted in Step 2. If a field is not found in the report, omit that `--metadata` flag — the template has sensible defaults. ### Step 4: Run Chrome headless ```bash "/Applications/Google Chrome.app/Contents/MacOS/Google Chrome" \ --headless=new \ --disable-gpu \ --no-sandbox \ --print-to-pdf="$(pwd)/GEO-REPORT.pdf" \ --print-to-pdf-no-header \ --no-pdf-header-footer \ --virtual-time-budget=5000 \ "file://$(pwd)/GEO-REPORT.html" ``` ### Step 5: Report completion Tell the user: - `GEO-REPORT.pdf` was generated in the current directory - File size - Optionally: `open GEO-REPORT.pdf` to preview it ## What the PDF Contains - **Cover page** — Dark navy gradient, brand name, domain, GEO score badge (colored by score), audit date, business type, locations, CMS platform - **Score tables** — Cells containing `XX/100` are color-coded: ≥80 green, ≥65 blue, ≥50 amber, ≥35 orange, <35 red - **Finding sections** — `h3` headings containing "Critical / High / Medium / Low" get severity-colored left-border callout blocks (red / orange / yellow / green) - **Section page breaks** — Major sections (High Priority, 90-Day Roadmap, Component Score Summary, Generated Schema) break to new pages automatically - **Code blocks** — JSON schema templates render with dark theme monospace styling - **Page footer** — Brand name · GEO Audit · date + page numbers (via CSS `@page`) ## Customizing the Report - **Colors / typography** — Edit `~/.claude/skills/geo/templates/geo-report-style.css` - **Cover layout** — Edit `~/.claude/skills/geo/templates/geo-report-template.html` - **Score thresholds for color-coding** — Edit the `scoreColor()` function in the template's `<script>` block - **Which sections get page breaks** — Edit the `breakBefore` array in the template's `<script>` block ## Troubleshooting | Problem | Fix | |---|---| | `pandoc: command not found` | `brew install pandoc` | | Chrome not found | Check path: `/Applications/Google Chrome.app/Contents/MacOS/Google Chrome` | | PDF is blank / empty | Increase `--virtual-time-budget` to 8000 | | Cover metadata missing | Check GEO-AUDIT-REPORT.md has the standard header format | | Fonts not loading | PDF is rendered offline; system fonts are used as fallback — this is expected |
Excerpt, first 5,055 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.
Install
Pinned to the audited commit a1519a4
git clone https://github.com/zubair-trabzada/geo-seo-claude git -C geo-seo-claude checkout a1519a410207
The author documents no install command, so this uses the repository directly. Our verdict covers commit a1519a410207 only.
Works in
The author has not said which agents this skill supports, and we have not tested it in any.
Audit history
Every audit, every source change
- ✓SAFE B 89 / 100
first audit · source
a1519a410207
README badge
For maintainers · shows the latest audit
[](https://modelsatlas.com/skills/zubair-trabzada/geo-report-pdf/)
The badge shows our verdict and grade for this skill, and links back to this page. It changes when the audit does.
Similar skills
obra/superpowers
Use when creating new skills, editing existing skills, or verifying skills work before deployment
mattpocock/skills
A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.
mattpocock/skills
Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.
Add this badge to your README
[](https://modelsatlas.com/skills/zubair-trabzada/geo-report-pdf/)
<a href="https://modelsatlas.com/skills/zubair-trabzada/geo-report-pdf/"><img src="https://modelsatlas.com/skills/zubair-trabzada/geo-report-pdf/badge.svg" alt="ModelsAtlas: SAFE B"></a>
Questions about geo-report-pdf
What does the geo-report-pdf skill do?
Is geo-report-pdf safe to install?
What can geo-report-pdf access on my machine?
How current is this page?
Sources
- github.com/zubair-trabzada/geo-seo-claude/tree/main/skills/geo-r — the audited source at commit a1519a410207 and every finding aboveObserved · 30 Oct 2026
Spotted something wrong? Report a correction · Methodology
Keep going in your AI
Opens with this page as the source. We add nothing else to the prompt.
- What does the geo-report-pdf skill do?
- Is geo-report-pdf safe to install?
- What can geo-report-pdf access on my machine?