CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

geo-compare

Monthly delta tracking and progress reporting for GEO clients. Compares two GEO audits (baseline vs. current), calculates score improvements across all categories, tracks action item completion, and generates a "here's your progress" client report. Use when user says "compare", "delta", "monthly report", "progress", "confronta", "progressi", "report mensile", or when running a monthly client check-in.

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

78%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-sequenced skill with concrete commands, parsing rules, edge-case handling, and a worked example. Its main weaknesses are the monolithic inline report template that bloats SKILL.md for every invocation, and the absence of an explicit validation checkpoint on extracted scores before report generation.

Suggestions

Move the ~170-line report template to references/report-template.md and reference it from the Workflow step ('Generate the report using [report-template.md](references/report-template.md)'), keeping only the section outline in SKILL.md so the template loads only when generating.

Add a validation checkpoint between Step 2 and Step 3: confirm every extracted baseline/current score is present and numeric before computing deltas, and re-parse or fall back to contextual estimation per-category if any value is missing (currently the fallback is stated only loosely at the end).

Trim the agency-flavored padding in the Purpose section ('The single most powerful retention tool', 'proof of value') and the 'celebrate' note to one directive sentence each.

DimensionReasoningScore

Conciseness

The body is mostly lean: concrete commands, exact file paths, delta formulas, and trend thresholds with almost no explanation of concepts Claude already knows. Minor over-explanation could be trimmed — the sales pitch ('The single most powerful retention tool for a GEO agency... Every point gained on the GEO score is proof of value') and the 'Use this section to celebrate — clients need to see the value clearly' note add agency framing Claude doesn't need. It does not reach anchor 5 because a few of these tokens don't earn their place.

4 / 5

Actionability

Guidance is fully executable: exact commands ('/geo compare electron-srl.com --month march-2026'), specific lookup paths ('~/.geo-prospects/audits/'), explicit score markers to extract ('GEO Score: XX/100', 'GPTBot: Allowed/Blocked'), a delta formula with trend thresholds (+5 → ▲▲), a defined output path, and a worked example (electron-srl.com 32 → 44) woven through the template. This matches anchor 5 — specific examples cover the common cases; anchor 4 would imply missing key details.

5 / 5

Workflow Clarity

The 4-step workflow is clearly sequenced with edge-case handling (one file → run fresh audit; no files → suggest /geo prospect audit) and an error-recovery fallback ('If exact scores are not found in audit files, use contextual analysis...'). It sits at anchor 4 rather than 5 because there is no explicit validation checkpoint that extracted baseline/current scores are correct before generating the report, and no post-generation verification; it is above anchor 3 because fallback and edge-case checkpoints are present.

4 / 5

Progressive Disclosure

The body has good section structure (Commands, Workflow, Report Template, Delta Calculation Logic, Trend Interpretation, Output), but the ~170-line report template is inlined wholesale in SKILL.md when it is exactly the kind of stable artifact that belongs in a separate references/ file loaded only at generation time. This matches anchor 3 ('content that should be separate is inline'); it is above anchor 2 because sections are clearly headed and navigable, and below anchor 4 because no bundle split exists at all for a skill this size.

3 / 5

Total

16

/

20

Passed

Description

88%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 strong description: comprehensive third-person capability statement, explicit 'Use when' triggers with bilingual synonyms, and a contextual monthly-check-in trigger. The main weakness is that several trigger words are generic, giving it modest conflict risk with non-GEO 'compare'/'progress' requests.

DimensionReasoningScore

Specificity

The description lists four concrete actions — 'Compares two GEO audits (baseline vs. current), calculates score improvements across all categories, tracks action item completion, and generates a "here's your progress" client report' — which comprehensively covers the skill's capabilities in third-person voice. It matches the anchor for multiple specific concrete actions with comprehensive coverage, not the anchor below (minor gaps in coverage).

5 / 5

Completeness

It explicitly answers both what (the four concrete actions) and when ('Use when user says "compare", "delta", "monthly report", "progress", "confronta", "progressi", "report mensile", or when running a monthly client check-in') with concrete trigger phrases. This matches anchor 5 exactly; anchor 4 would require the 'when' to be less explicit or specific.

5 / 5

Trigger Term Quality

Triggers include natural terms ('compare', 'delta', 'monthly report', 'progress') plus Italian synonyms ('confronta', 'progressi', 'report mensile') and a contextual phrase ('monthly client check-in') — good coverage with synonym awareness. It falls short of anchor 5 because the terms are generic words rather than domain-distinct phrases, and one or two natural phrasings a client-facing user might say (e.g., 'show progress', 'how are we doing') are absent; it is clearly above anchor 3 since synonyms and a context trigger are present.

4 / 5

Distinctiveness Conflict Risk

The GEO-audit domain framing makes the skill mostly distinct, but bare trigger words 'compare' and 'progress' are common in many non-GEO requests, creating minor overlap risk with other comparison/reporting skills. It is above anchor 3 (would still overlap with many similar skills) because the GEO/agency framing narrows it, but below anchor 5 (minimal conflict risk) due to those generic single-word triggers.

4 / 5

Total

18

/

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-compare/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.