Name: geodb-cities
Rating: 62.4 (1 reviews)
Author: membranedev

geodb-cities

GeoDB Cities integration. Manage Cities, Countries, Continents. Use when the user wants to interact with GeoDB Cities data.

Quality

74%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/geodb-cities/SKILL.md

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.

The body is highly actionable with concrete, executable commands and a clear connection-readiness feedback loop. Its weaknesses are moderate verbosity in explanatory prose and an opportunity to move the long actions table into a reference file.

Suggestions

Trim explanatory prose (e.g., the "focus on the integration logic rather than auth plumbing" aside and the opening GeoDB Cities description) to assume Claude's existing knowledge.

Label the workflow steps explicitly (Step 1 install/login, Step 2 search/run actions) so the referenced "Step 2" is unambiguous and the "1b" subsection integrates cleanly.

Consider moving the 15-row actions table and the proxy flag reference into a separate reference file (e.g., ACTIONS.md) referenced from the body, keeping SKILL.md as a concise overview.

Dimension	Reasoning	Score
Conciseness	Mostly command-driven and efficient, but padded with prose explaining what GeoDB Cities is, the Membrane philosophy ("so you can focus on the integration logic rather than auth plumbing"), and verbose best-practice rationales; not a 4 because several sections could be tightened, not a 2 because commands dominate over exposition.	3 / 5
Actionability	Provides fully executable, copy-paste-ready commands covering the common cases (install, login, connection ensure, action list/run, request proxy) with flags and JSON examples; placeholders like CONNECTION_ID and <actionId> are expected and do not reduce executability.	5 / 5
Workflow Clarity	Clear sequence (install → login → connect → search → run → proxy) with a state-checking feedback loop (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR polling) for connection readiness; not a 5 because step numbering is loose (a referenced "Step 2" is not clearly labeled, and the "1b" subsection breaks the flow).	4 / 5
Progressive Disclosure	Well-organized into clear sections with a useful inline actions table and no nested references; not a 5 because the 15-row actions table and proxy-flag reference arguably belong in a separate file, and not a 3 because structure is clean and navigable as written.	4 / 5
	Total	16 / 20 Passed

Description

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

The description is clear and distinct, answering both what and when with a specific product name and natural entity keywords. Its main weakness is the generic "Manage" action verb, which limits action specificity.

Suggestions

Replace the generic verb "Manage" with concrete actions the skill performs (e.g., "Find cities near a location, get city time and distance, list countries and regions").

Expand the trigger phrase beyond the tautological "interact with GeoDB Cities data" to concrete user intents like "Use when the user asks for city populations, nearby cities, or distances between cities."

Add common synonyms or phrasings users might say (e.g., "city lookup", "geography data", "find cities by coordinates") to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	Names the domain and three concrete entities ("Cities, Countries, Continents") but only one generic action verb ("Manage"), which is minimal rather than comprehensive; not a 2 because the three named entity types add concreteness beyond a single bare action.	3 / 5
Completeness	Has both a "what" ("Manage Cities, Countries, Continents") and an explicit "when" ("Use when the user wants to interact with GeoDB Cities data"); not a 5 because the trigger is somewhat tautological and lacks multiple concrete trigger phrases.	4 / 5
Trigger Term Quality	Good natural keyword coverage ("cities", "countries", "continents", "GeoDB Cities data") that a user would plausibly say; not a 5 because synonyms and variants are absent, but better than the 3-anchor's thin single-keyword coverage.	4 / 5
Distinctiveness Conflict Risk	Names a specific product ("GeoDB Cities") with a clear niche and product-specific triggers, giving minimal conflict risk with other skills.	5 / 5
	Total	16 / 20 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/geodb-cities/SKILL.md
Commit: f484c82

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.