Name: geoapify
Rating: 52.8 (1 reviews)
Author: membranedev

geoapify

Geoapify integration. Manage data, records, and automate workflows. Use when the user wants to interact with Geoapify data.

Quality

58%

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/geoapify/SKILL.md

Quality

Content

67%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 a well-structured, actionable CLI integration guide with a clear connection workflow and strong command examples. Its main weaknesses are a padded introductory paragraph and placeholder-only examples rather than complete worked runs.

Suggestions

Trim the marketing-style opening paragraph to a one-line statement of what Geoapify provides.

Add at least one complete end-to-end worked example (connect, search, run an action with real-looking parameters) so the flow is copy-paste runnable.

Move the popular-actions and proxy-flag tables into a reference file and link to it from the body to deepen progressive disclosure.

Dimension	Reasoning	Score
Conciseness	Mostly efficient commands and tables, but the opening marketing paragraph ('Developers and businesses use it to build location-aware applications...') and prose like 'so you can focus on the integration logic rather than auth plumbing' could be trimmed.	3 / 5
Actionability	Provides concrete, copy-paste-ready CLI commands with flag tables and a popular-actions table, but examples lean on placeholders (CONNECTION_ID, actionId) without a full end-to-end worked example.	4 / 5
Workflow Clarity	Clear sequenced flow (install, login, connection ensure, poll state, search, run) with state-based checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a re-poll feedback loop, though action-result error recovery is thin.	4 / 5
Progressive Disclosure	Well-organized into clear sections with no nested references, but all content is inline with no external reference files; at ~150 lines it exceeds the simple-skill threshold that would allow a 5.	4 / 5
	Total	15 / 20 Passed

Description

50%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 correctly identifies the platform and includes a use-when clause, but its action verbs are generic and it lacks the natural trigger terms (geocoding, routing, addresses) users would actually say. It is functional but underspecified for a location-API skill.

Suggestions

Replace generic verbs with concrete Geoapify capabilities, e.g. 'Geocode addresses, calculate routes, and search for places via the Geoapify API.'

Add natural trigger phrases users would say, such as 'Use when the user wants to geocode an address, calculate a route, find nearby places, or reverse-geocode coordinates.'

Drop the boilerplate 'Manage data, records, and automate workflows' which adds overlap risk without communicating real capability.

Dimension	Reasoning	Score
Specificity	Names the domain ('Geoapify integration') but the actions ('Manage data, records, and automate workflows') are generic and not concrete Geoapify operations like geocoding or routing.	2 / 5
Completeness	States both what it does (Geoapify integration, manage data/records/workflows) and when to use it ('Use when the user wants to interact with Geoapify data'), though the trigger is vague rather than concrete.	4 / 5
Trigger Term Quality	Only offers 'Geoapify' and 'data' as keywords and omits the natural phrases a user would actually say (geocode, route, address, coordinates, places).	2 / 5
Distinctiveness Conflict Risk	Naming the specific Geoapify platform makes it clearly distinct, with only minor overlap risk from the generic 'manage data, records, and automate workflows' phrasing.	4 / 5
	Total	12 / 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/geoapify/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.