CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

geo-report-pdf

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.

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./skills/geo-report-pdf/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

82%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A highly actionable, well-structured skill body: exact commands, concrete extraction patterns, and a useful troubleshooting table. Remaining improvements are minor — a duplicated overview section, no output-verification step, and non-portable hardcoded template paths.

DimensionReasoningScore

Conciseness

Largely lean — terse prerequisites ('No Python dependencies. No ReportLab. No JSON data wrangling.'), a compact field-extraction table, and a troubleshooting table — but 'How It Works' overlaps somewhat with 'Workflow' and could be trimmed.

4 / 5

Actionability

Fully executable, copy-paste-ready pandoc and Chrome headless commands with exact field-extraction patterns (e.g. '## Overall GEO Score: XX / 100', '**Domain:**') and an explicit fallback rule ('If a field is not found... omit that --metadata flag') covering the common cases.

5 / 5

Workflow Clarity

Five clearly sequenced steps with a prerequisite check (Step 1) and a troubleshooting table for error recovery; the minor gap is no explicit verification that GEO-REPORT.pdf was created and is non-empty before reporting completion in Step 5.

4 / 5

Progressive Disclosure

Well-organized sections with styling and JavaScript logic appropriately externalized to the template and CSS files, clearly signaled with full paths and a 'Customizing the Report' section. Minor gaps: references use hardcoded absolute paths (~/.claude/skills/geo/templates/) rather than skill-relative paths, and no bundle files ship alongside SKILL.md.

4 / 5

Total

17

/

20

Passed

Description

71%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A specific, concrete, third-person description that clearly names its input, pipeline, and outputs. Its main weakness is the missing 'Use when...' trigger clause, which leaves the 'when' only implied and caps completeness.

Suggestions

Append an explicit trigger clause, e.g. 'Use when the user wants to convert a GEO audit report into a PDF, export a client-ready deliverable, or asks for a formatted/styled report from GEO-AUDIT-REPORT.md.'

Add natural synonyms and file variations to the trigger terms — 'PDF', '.pdf', 'export', 'client deliverable', 'styled report' — so the description matches how users would phrase the request.

Clarify the dependency on the upstream skill (e.g. 'Use after /geo audit has produced GEO-AUDIT-REPORT.md') to sharpen the 'when' and reduce overlap with generic PDF-generation skills.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions — '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' — with comprehensive coverage and correct third-person voice.

5 / 5

Completeness

The 'what' is clearly and concretely stated, but there is no 'Use when...' clause or equivalent explicit trigger guidance; the 'when' is only weakly implied by 'from a GEO audit', which caps completeness at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

Good natural keywords ('PDF report', 'GEO audit', 'client-ready') but missing common variations users would say, such as 'export the audit', 'turn the audit into a PDF', or '.pdf'.

4 / 5

Distinctiveness Conflict Risk

A clear niche (GEO audit → client-ready PDF) anchored by the specific input file GEO-AUDIT-REPORT.md, but the absent trigger guidance leaves minor overlap risk with generic PDF-generation requests.

4 / 5

Total

16

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository

zubair-trabzada/geo-seo-claude

Path

skills/geo-report-pdf/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.