CtrlK
BlogDocsLog inGet started
Tessl Logo

review-data-pr

Perform an intelligent review of geographic data PRs beyond schema validation. Use this skill whenever reviewing a data PR, performing code review on contributions, checking if data makes geographical sense, or assessing data quality. Trigger on: PR review requests for data changes, "review this PR", "does this look right", "is this data correct", quality assessment requests, geographic plausibility checks, suspicious pattern detection, or any pull request touching files in the contributions/ directory. This goes beyond schema validation to check real-world geographic accuracy.

70

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

75%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 tight, well-structured instruction skill: concrete checklists, specific thresholds, a copy-paste output template, and an escalation feedback loop. It falls just short of maximal scores because checks are judgment-based rather than executable, there is no explicit pre-output verification checkpoint, and the opening line redundantly restates the description.

Suggestions

Add an explicit validation checkpoint before emitting the review (e.g., 'Re-verify each flagged coordinate and source URL before listing findings') to close the workflow feedback loop.

Delete the redundant 'This skill goes beyond schema validation to check data quality and plausibility.' line in the body, which restates the frontmatter description.

Make at least one check executable by naming a concrete tool or command — e.g., how to spot-check a coordinate against a geocoding API or the contributions/ schema path — so guidance is not purely judgment-based.

DimensionReasoningScore

Conciseness

The body is lean and well-organized as bullet checklists that assume Claude's competence, but it restates 'goes beyond schema validation' from the description (line 16) and carries a few illustrative parentheticals (e.g., the Springfield-in-India example) that could be trimmed — efficient with minor over-explanation.

4 / 5

Actionability

Provides concrete, actionable guidance — specific suspicious patterns, source tiers (Tier 1/Tier 2), an escalation threshold (>100 records), a maintainer handle (@dr5hn), and a copy-paste-ready output template — but the plausibility checks remain judgment-based ('Does the city name make sense') rather than executable steps, leaving minor gaps.

4 / 5

Workflow Clarity

A clear six-step sequence (read context → plausibility → suspicious patterns → verify source → completeness → overall quality) with per-step checklists and an escalation path acting as a feedback loop, but there is no explicit verify-before-output checkpoint re-confirming flagged findings before emitting the review.

4 / 5

Progressive Disclosure

Well-organized with clear section headers and no nested references, and all content is appropriately inline for a self-contained review checklist; at ~95 lines it sits just above the simple-skill threshold and lacks the one-level-deep external references the top anchor expects, so it is well-structured but not maximal.

4 / 5

Total

16

/

20

Passed

Description

95%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, well-scoped description that clearly states both what the skill does and when to use it, with abundant natural trigger phrases and a concrete file-path trigger. The only blemish is the slightly abstract lead phrasing ('intelligent review') and review-oriented rather than mechanical action verbs.

DimensionReasoningScore

Specificity

Lists several concrete review actions ('performing code review on contributions', 'checking if data makes geographical sense', 'geographic plausibility checks', 'suspicious pattern detection', 'check real-world geographic accuracy'), but the lead verb 'Perform an intelligent review' is a mild over-claim and the actions are review-oriented rather than mechanical, leaving minor coverage gaps versus the comprehensive anchor.

4 / 5

Completeness

Explicitly answers both 'what' ('Perform an intelligent review of geographic data PRs beyond schema validation ... check real-world geographic accuracy') and 'when' ('Use this skill whenever ... Trigger on: ...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural quoted phrases a user would actually say ('review this PR', 'does this look right', 'is this data correct') plus synonyms (quality assessment, plausibility checks, suspicious pattern detection) and a concrete file-path trigger ('pull request touching files in the contributions/ directory'), giving comprehensive natural-term coverage.

5 / 5

Distinctiveness Conflict Risk

Scoped to a clear niche — geographic data PRs in the contributions/ directory — with distinct triggers (geographic plausibility, suspicious pattern detection) that are unlikely to fire for unrelated skills.

5 / 5

Total

19

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
dr5hn/countries-states-cities-database
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.