← ClaudeAtlas

reportlisted

Render a recorded audit as a client-ready HTML or PDF report, with optional agency branding and a separate operator copy. Use when asked for a report, a deliverable, a PDF, something to send a client, or a white-labelled audit.
seo-skills/geo-audit-skill · ★ 3 · Data & Documents · score 79
Install: claude install-skill seo-skills/geo-audit-skill
# Reports Turn a recorded audit into a document someone can send. The CLI renders it; you decide which mode, and you check it before it goes out. ## Preflight Run this first, once per session: ```bash geo --version ``` Expected: `seomator-geo-audit 1.2.x` or newer. - **Command not found** -> stop and say: "The geo CLI is not installed. Install it with `uv tool install seomator-geo-audit` (or `pipx install seomator-geo-audit`), then run this again." - **Older than 1.2.0** -> stop and say: "This skill needs seomator-geo-audit 1.2.0 or newer. Upgrade with `uv tool upgrade seomator-geo-audit`." - **Anything else odd** -> run `geo doctor` and relay what it reports. ## Run ```bash geo report <url> --json geo report <url> --site-kind docs --json geo report <url> --mode operator --json geo report <url> --brand-config brand.json --pdf --json geo report <url> --out ./audit.html --json ``` It reads from disk and never crawls, so it always describes a run that happened. Run `geo audit <url>` first. ## The two modes **Client** is the default because it is the one that gets sent. It carries the score, what is already working, the categories, the findings with their pages and remediation, the advisory section, and the methodology appendix. **Operator** is the same document plus a provenance section: run id, evidence hash, crawl settings, the failed-page table, the robots-disallowed list, every signal with its class and value, and the brand contrast measurements. The separation