Name: geokeo
Rating: 56.8 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

geokeo

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

Quality

65%

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/geokeo/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 content is a well-structured, actionable integration guide anchored in copy-paste CLI commands and a clear connection-state feedback loop. Its main weaknesses are unnecessary marketing prose at the top, inconsistent step numbering, and the absence of validation guidance for running actions.

Suggestions

Trim the introductory marketing paragraph about what Geokeo is and who uses it; Claude does not need that context to run the integration.

Add explicit validation/error-recovery guidance for `membrane action run` (e.g. inspecting the response, retrying on failure) and fix the inconsistent step numbering so "Step 1/Step 2" and "1b" line up.

Either expand the bare "Geokeo Overview" list into useful entries or remove it, since a nested list of unexplained terms adds tokens without guidance.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean executable commands, but the opening marketing prose ("Geokeo is a location intelligence platform... used by analysts and decision-makers in industries like retail, real estate, and logistics") and phrases like "so you can focus on the integration logic rather than auth plumbing" explain context Claude does not need. This fits the anchor for mostly efficient with some unnecessary explanation, not 4 which requires only minor trimmable instances.	3 / 5
Actionability	It provides concrete, copy-paste-ready CLI commands for install, login, connection ensure, action list/run, and request, plus a flag options table, fitting the anchor for mostly executable guidance with minor gaps. It is not 5 because parameters like CONNECTION_ID, actionId, and the QUERY intent are left as placeholders without a complete end-to-end worked example.	4 / 5
Workflow Clarity	The install→authenticate→connect→search→run flow is clearly sequenced, and the connection polling includes an explicit feedback loop over states (READY, BUILDING, CLIENT_ACTION_REQUIRED, CONFIGURATION_ERROR). This matches the anchor for a clear sequence with most checkpoints present; it is not 5 because action-running lacks validation/error-recovery guidance and step numbering is inconsistent ("Step 2" and "1b" referenced without clearly labeled steps).	4 / 5
Progressive Disclosure	Content is organized into clear, navigable sections (Overview, Working with Geokeo, Install, Authentication, Connecting, Searching, Popular actions, Proxy, Best practices) with no nested references. This fits the anchor for good structure with most content appropriately placed and minor organization gaps; it is not 5 because the file exceeds 50 lines with a bare, under-explained Overview list that is a minor organization gap and no progressive split of the larger reference material.	4 / 5
	Total	15 / 20 Passed

Description

62%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 functional and correctly pairs a "what" with an explicit "Use when" trigger, and the Geokeo brand name keeps it distinct. It is held back by generic action verbs and a thin set of natural trigger terms that omit common synonyms like geospatial, maps, and location.

Suggestions

Replace generic verbs with concrete geospatial actions, e.g. "Search geospatial records, manage datasets and maps, and automate Geokeo workflows."

Expand the trigger clause with natural terms users actually say: "Use when the user wants to work with Geokeo, geospatial data, location intelligence, or Geokeo maps and datasets."

Add file-format or endpoint cues (e.g. Geokeo API) to strengthen distinctiveness and trigger-term coverage.

Dimension	Reasoning	Score
Specificity	The description names the domain ("Geokeo integration") and a few actions ("Manage data, records, and automate workflows"), but those actions are generic rather than concrete, matching the anchor for naming a domain with 1-2 non-comprehensive actions. It does not reach 4 because the actions lack specificity (no concrete geospatial operations).	3 / 5
Completeness	It explicitly answers both "what" (Geokeo integration; manage data, records, automate workflows) and "when" ("Use when the user wants to interact with Geokeo data"), matching the anchor for both present with the "when" being somewhat generic. It is not 5 because the trigger phrase is not concrete and specific enough.	4 / 5
Trigger Term Quality	It includes the brand keyword and phrase "interact with Geokeo data" plus "Use when", but misses common natural variations and synonyms a user would say (geospatial data, maps, location intelligence, Geokeo API). This fits the anchor for some relevant keywords missing common variations, not 4 which requires broader coverage.	3 / 5
Distinctiveness Conflict Risk	Tying the skill to the specific brand "Geokeo" gives it a clear niche with low conflict risk, fitting the "mostly distinct; minor overlap risk" anchor. It is not 5 because the action wording ("manage data, records") is generic and could overlap conceptually with other data-management skills.	4 / 5
	Total	14 / 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/geokeo/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.