CtrlK
BlogDocsLog inGet started
Tessl Logo

fix-contribution

Fix common issues in geographic data contributions to the CSC database. Use this skill whenever you need to fix, correct, repair, patch, or resolve issues in a data contribution or PR. Trigger on: "@copilot fix this", "auto-fix" label on issues, "can you fix", "please correct", "help me fix", "what's wrong with my PR", removing auto-managed fields, correcting country codes, fixing mismatched foreign keys, or formatting JSON. Also use when a PR has validation errors and you need to commit fixes directly. Read common-fixes.md in this directory for fix patterns and examples.

68

Quality

86%

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

65%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 well-structured, actionable instruction-only skill with a clear fix workflow and good safety guardrails. Its main weaknesses are the missing re-validation checkpoint after applying batch fixes, a duplicated patterns section, and a referenced common-fixes.md file that is absent from the bundle.

Suggestions

Add a final validation step after applying fixes (e.g., re-run the PR validation check and only comment/merge when errors are resolved), creating a fix → validate → retry feedback loop.

Resolve the dangling reference: either ship common-fixes.md with the promised before/after examples or remove the two references to it from the body.

De-duplicate the 'Common Fix Patterns' section against 'Step 2: Apply Fixes' — merge the lookup procedures into one place and keep only non-obvious details in the patterns section.

DimensionReasoningScore

Conciseness

The body is lean and list-driven with no padding of concepts Claude already knows, but the 'Common Fix Patterns' section substantially duplicates Step 2 content (code lookups and auto-managed field removal appear twice), which could be trimmed.

4 / 5

Actionability

Guidance is concrete — named lookup files (countries.json, states.json), exact field names, and exact commit message formats ('fix: correct [description] in [filename]') — but the patterns are procedural step lists rather than executable commands, and file locations are not given. Per the instruction-only scoring note this is not heavily penalized, but minor gaps remain.

4 / 5

Workflow Clarity

Steps 1–4 are clearly sequenced and include good safety rules ('ask rather than guess'), but the workflow modifies batch contribution records and commits to PRs with no step to re-run validation after fixes to confirm the errors are resolved — a missing feedback loop that caps this at 3.

3 / 5

Progressive Disclosure

Sections are well organized and the reference to common-fixes.md is clearly signaled, but that file does not exist in the skill directory — a dangling reference promising 'detailed fix patterns with before/after examples' that cannot actually be read, leaving the disclosure structure incomplete.

3 / 5

Total

14

/

20

Passed

Description

100%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.

An exemplary description: concrete capabilities, explicit use-when triggers with natural user phrasings, comprehensive synonym coverage, and a clearly distinct niche. Third-person voice is maintained and there is no fluff.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — 'removing auto-managed fields, correcting country codes, fixing mismatched foreign keys, or formatting JSON' plus 'commit fixes directly' — which comprehensively covers the skill's action space rather than leaving minor gaps.

5 / 5

Completeness

It explicitly answers both what ('Fix common issues in geographic data contributions to the CSC database' plus a concrete action list) and when ('Use this skill whenever you need to...', 'Trigger on:', 'Also use when a PR has validation errors') with concrete trigger phrases.

5 / 5

Trigger Term Quality

It covers natural synonyms ('fix, correct, repair, patch, resolve') and real user phrasings like '@copilot fix this', 'can you fix', 'help me fix', and "what's wrong with my PR", matching the comprehensive-synonyms anchor.

5 / 5

Distinctiveness Conflict Risk

The niche is clearly bounded by 'CSC database', 'geographic data contributions', 'country codes', and 'mismatched foreign keys', with distinct trigger phrases, so conflict with other skills is minimal.

5 / 5

Total

20

/

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.

Validation — 16 / 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.