portaljs-add-map

Render a GeoJSON dataset on an interactive Leaflet map in the Views section of a dataset's showcase. Installs react-leaflet and a Map component, then renders the map for the chosen dataset. Use when a dataset's data is geographic and a map view is needed alongside the showcase's default metadata and download.

Quality

88%

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

92%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.

A well-structured, concise skill body with concrete commands, an explicitly validated multi-step workflow, and clean progressive disclosure to a real reference file. The only gap is the absence of inline copy-paste component code, which is reasonably deferred to the canonical workflow.

Dimension	Reasoning	Score
Conciseness	Lean and efficient with no padding of concepts Claude already knows; asides like 'since Leaflet touches window at module load' and 'added directly — never @portaljs/components' are justified, non-obvious whys rather than over-explanation.	5 / 5
Actionability	Concrete commands and paths throughout ('npm install react-leaflet@^5 leaflet@^1.9', 'npx tsc --noEmit', 'pages/[owner]/[slug].tsx') with full slash-command examples, but the actual copy-paste-ready MapView/Map component code and import snippet are deferred to the external workflow rather than inlined.	4 / 5
Workflow Clarity	An 8-step sequence with explicit validation checkpoints (portal dir validation in step 2, 'npx tsc --noEmit' verify in step 7) plus an error-handling table providing feedback loops, satisfying the validation requirement even for mutating route/dataset operations.	5 / 5
Progressive Disclosure	A clear overview that defers full detail to the canonical linked workflow and the verified references/reference.md, with one-level-deep, clearly signaled references and well-organized sections for easy navigation.	5 / 5
	Total	19 / 20 Passed

Description

83%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.

A strong, third-person description that concretely names the domain and key actions and includes an explicit 'Use when' trigger. It is held back only by slightly limited action breadth and a few missing trigger synonyms/extensions.

Suggestions

Add the '.geojson' file extension and a synonym like 'plot a map' to the trigger clause to lift trigger_term_quality toward 5.

Mention dataset registration as a supported action (covered in the body) to broaden specificity coverage.

Dimension	Reasoning	Score
Specificity	Names the domain and several concrete actions — 'Render a GeoJSON dataset on an interactive Leaflet map', 'Installs react-leaflet and a Map component', 'renders the map for the chosen dataset' — but the action set is somewhat narrow for a single-purpose skill, leaving minor gaps versus the comprehensive anchor 5.	4 / 5
Completeness	Clearly states what it does (renders a GeoJSON dataset on a Leaflet map in the Views section, installs deps) and explicitly answers when with a concrete 'Use when a dataset's data is geographic and a map view is needed' trigger clause.	5 / 5
Trigger Term Quality	Good natural keyword coverage — 'GeoJSON dataset', 'interactive Leaflet map', 'map view', 'geographic' — but misses some synonyms and the explicit '.geojson' file extension that anchor 5 expects.	4 / 5
Distinctiveness Conflict Risk	Carves a clear PortalJS-specific niche (Leaflet + GeoJSON + showcase Views) that is mostly distinct, with only minor overlap risk against closely related sibling skills like portaljs-add-chart.	4 / 5
	Total	17 / 20 Passed

Validation

87%

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

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: datopian/portaljs
Path: skills/portaljs-add-map/SKILL.md
Commit: ebfd391

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