Name: google-maps
Rating: 55.2 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

google-maps

Google Maps integration. Manage Maps. Use when the user wants to interact with Google Maps data.

Quality

62%

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/google-maps/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 highly actionable with concrete Membrane CLI commands and a well-sequenced connection state machine, but it spends tokens explaining Google Maps itself and could push some reference material into bundle files.

Suggestions

Remove the opening paragraph describing what Google Maps is; Claude already knows this and it adds no integration value.

Move the Popular actions table into a references/ file (e.g. ACTIONS.md) and link to it from a short overview, keeping only the most common actions inline.

Clarify the step numbering (define an explicit Step 1 / Step 2) so the "skip to Step 2" and "1b" cross-references resolve unambiguously.

Dimension	Reasoning	Score
Conciseness	Most sections are efficient with copy-ready commands and tables, but the opening paragraph explaining what Google Maps is (satellite imagery, street maps, 360° views, etc.) and phrases like "so you can focus on the integration logic rather than auth plumbing" explain concepts Claude already knows, fitting the mostly-efficient-but-could-be-tightened anchor.	3 / 5
Actionability	It provides concrete, executable commands for install, login, connection ensure, action list/run, and proxy requests plus a Popular actions table, with only minor gaps such as placeholder CONNECTION_ID values and flag-only proxy examples, matching the mostly-executable anchor.	4 / 5
Workflow Clarity	The connect-to-run flow is clearly sequenced with explicit polling and a state machine (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) that includes feedback loops, but cross-references like "skip to Step 2" and a "1b" sub-step reveal minor sequencing gaps, fitting the clear-sequence-with-minor-gaps anchor.	4 / 5
Progressive Disclosure	Content is organized into well-labeled sections (Overview, Working with Google Maps, Install, Authentication, Connecting, Searching, Popular actions, Proxy, Best practices) with no nested references, though the inline Popular actions table and feature inventory could live in a separate reference file, matching the good-structure-with-minor-gaps anchor.	4 / 5
	Total	15 / 20 Passed

Description

57%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 signals a Google Maps niche and includes an explicit Use-when trigger, but its capability statement is generic ("Manage Maps") and lacks the concrete actions and natural synonyms that would make it specific and richly triggered.

Suggestions

Replace the generic "Manage Maps" with concrete capabilities, e.g. "Get directions, search and geocode places, retrieve static maps and place details."

Expand trigger terms with natural synonyms users say, such as directions, navigation, geocoding, nearby places, or distance matrix.

Tighten the Use-when clause to concrete triggers like "Use when the user wants directions, place search, geocoding, or static map images."

Dimension	Reasoning	Score
Specificity	The description names the domain ("Google Maps") but the only action stated is the generic "Manage Maps", with no concrete capabilities such as directions, geocoding, or place search, matching the anchor where the domain is named but actions are minimal.	2 / 5
Completeness	It provides a "what" ("Google Maps integration. Manage Maps.") and an explicit "when" clause ("Use when the user wants to interact with Google Maps data"), but the "when" is generic rather than tied to concrete triggers, fitting the anchor where both are present but the when could be more specific.	4 / 5
Trigger Term Quality	"Google Maps" and "Maps" are natural terms a user would say, but common variations and synonyms (directions, navigation, places, geocoding) are missing, fitting the anchor of some relevant keywords without common variations.	3 / 5
Distinctiveness Conflict Risk	"Google Maps integration" carves a clear niche with minimal conflict risk against unrelated skills, but the broad trigger phrasing leaves minor overlap risk with general mapping or location skills, matching the mostly-distinct anchor.	4 / 5
	Total	13 / 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/google-maps/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.