Name: mapbox
Rating: 55.2 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

mapbox

Mapbox integration. Manage Maps. Use when the user wants to interact with Mapbox 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/mapbox/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, largely executable guide to driving Mapbox through the Membrane CLI, with a clear connection workflow and useful state-check feedback loops. Its main weakness is conciseness — the introductory Mapbox background is padding — plus minor workflow numbering gaps and an undefined Step 2 reference.

Suggestions

Cut the opening background paragraph ("Mapbox is a mapping and location platform…") and the "Developers across various industries…" sentence; Claude already knows what Mapbox is.

Fix the step numbering: label the connection steps consistently and define or remove the dangling "Step 2" reference so the flow is unambiguous.

Consider moving the proxy flags option table into a short reference section or file so the main flow stays lean.

Dimension	Reasoning	Score
Conciseness	The opening paragraph ("Mapbox is a mapping and location platform for developers… Developers across various industries use Mapbox to enhance their applications with location intelligence") explains what Mapbox is — context Claude already knows — so it is mostly efficient but includes unnecessary explanation that could be trimmed.	3 / 5
Actionability	It provides concrete, executable membrane commands with flags (--json, --wait, --input) throughout install, auth, connection, search, run, and proxy sections; minor gaps like CONNECTION_ID placeholders keep it just below fully copy-paste-ready.	4 / 5
Workflow Clarity	The install→login→connect→poll→search→run sequence is clear with explicit state checkpoints (READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a polling feedback loop, but it references an undefined "Step 2" and uses odd "1b" numbering, leaving minor sequencing gaps.	4 / 5
Progressive Disclosure	Sections are well-organized (Overview, Working with Mapbox, Authentication, Connecting, Searching, Popular actions, Best practices) with no nested or buried references in this single-file CLI skill; it is not a 5 because some inline material like the proxy flags table could be separated and there are no signaled deeper references.	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 pairs a what with an explicit Use-when trigger and targets a distinct platform, but its capability statement is thin ("Manage Maps") and lacks concrete actions and natural trigger synonyms. Tightening the action list and adding user-facing terms would lift specificity and trigger quality.

Suggestions

Replace the generic "Manage Maps" with 2-3 concrete actions (e.g., "Manage map styles, tokens, and tilesets; query Mapbox APIs").

Add natural trigger synonyms and file/term variations users actually say (e.g., "map styles", "access tokens", "Mapbox APIs", "tilesets").

Make the when-clause more concrete by listing triggering phrases (e.g., "Use when the user wants to manage Mapbox maps, styles, tokens, or query Mapbox location APIs").

Dimension	Reasoning	Score
Specificity	"Manage Maps" names the Mapbox domain but the only action is the generic verb "Manage", matching the anchor that names the domain with minimal/generic actions rather than the 3-anchor which requires 1-2 concrete actions.	2 / 5
Completeness	It states a what ("Mapbox integration. Manage Maps.") and an explicit when ("Use when the user wants to interact with Mapbox data"), so it clears the 3-cap that applies when trigger guidance is missing; it is not a 5 because the what is vague and the when is not tied to concrete trigger phrases.	4 / 5
Trigger Term Quality	It includes relevant keywords ("Mapbox", "Maps", "interact with Mapbox data") but misses common variations, synonyms, or concrete artifacts users would say, fitting the anchor for some relevant keywords with missing synonyms.	3 / 5
Distinctiveness Conflict Risk	Mapbox is a distinct platform niche with a fairly specific trigger, but the generic term "Maps" carries minor overlap risk with other map-related skills, placing it at mostly-distinct rather than minimal-conflict.	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/mapbox/SKILL.md
Commit: f484c82

Reviewed: 6 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.