geospatial-and-cartographic-visualization

Design geospatial and cartographic visualizations. Use when the user needs help deciding whether to use a map, choosing projections or basemaps, building choropleths or symbol maps, or implementing thematic maps, slippy maps, or geospatial interactions with D3 geo, Leaflet, MapLibre, Mapbox GL JS, Google Maps, OpenLayers, deck.gl, ArcGIS Maps SDK, Azure Maps, HERE Maps, CesiumJS, or related tools.

Quality

86%

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

Quality

Content

72%Weight 40%Scale 1-3

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 thorough, actionable decision-tree for geospatial visualization design with clean progressive disclosure into real reference files. Its main weakness is redundancy between the Working Pattern and Output Expectations sections and implicit rather than explicit validation checkpoints.

Suggestions

Collapse the overlap between 'Working Pattern' and 'Output Expectations' so each deliverable is stated once, or explicitly cross-reference rather than restate.

Add explicit validation checkpoints (e.g., a 'Verify before coding' step for coordinate alignment, projection spot checks, and the source-method ledger) instead of embedding them as advisory clauses.

Consider trimming the 18-step working pattern by merging related decisions (e.g., overlap strategy and multiscale zoom behavior) to reduce token load.

Dimension	Reasoning	Score
Conciseness	The body is dense and directive without explaining concepts Claude already knows, but the 'Output Expectations' section substantially restates the 'Working Pattern' steps (e.g., source-method ledger, mobile layout, globe alignment), and the 18-step pattern could be tightened.	2 / 3
Actionability	Concrete, executable decision rules map situations to specific choices — e.g., 'D3 geo for custom projections, thematic cartography', 'clustered summary symbols when dense points need a count', 'screen-stable symbols ... when they act as locators'. No code is needed for this instruction-only skill.	3 / 3
Workflow Clarity	A clearly numbered 1–18 sequence exists, but validation checkpoints are mostly implicit ('audit coordinate alignment ... before coding', 'spot checks') with no explicit validate→fix→retry feedback loop.	2 / 3
Progressive Disclosure	SKILL.md is a well-signaled overview with a References section pointing one level deep to verified real files under ./references/ and ../../references/foundations/, with content appropriately split.	3 / 3
	Total	10 / 12 Passed

Description

100%Weight 40%Scale 1-3

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 third-person, concise, and clearly answers both what the skill does and when to use it, with strong coverage of natural trigger terms and named tooling. No vague fluff or over-claims.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'deciding whether to use a map, choosing projections or basemaps, building choropleths or symbol maps, ... implementing thematic maps, slippy maps, or geospatial interactions' — rather than vague language.	3 / 3
Completeness	Explicitly states what ('Design geospatial and cartographic visualizations') and when ('Use when the user needs help deciding whether to use a map, choosing projections or basemaps, ...').	3 / 3
Trigger Term Quality	Covers natural terms users would say ('map', 'projections', 'basemaps', 'choropleths', 'slippy maps') plus the named tools a user would actually request (Leaflet, MapLibre, Mapbox GL JS, Google Maps, deck.gl, CesiumJS).	3 / 3
Distinctiveness Conflict Risk	Occupies a clear niche (geospatial/cartographic visualization) with distinct, tool-specific triggers unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 12 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: openai/plugins
Path: plugins/build-web-data-visualization/skills/geospatial-and-cartographic-visualization/SKILL.md
Commit: 11c74d6

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