CtrlK
BlogDocsLog inGet started
Tessl Logo

geopandas

Python library for working with geospatial vector data including shapefiles, GeoJSON, and GeoPackage files. Use when working with geographic data for spatial analysis, geometric operations, coordinate transformations, spatial joins, overlay operations, choropleth mapping, or any task involving reading/writing/analyzing vector geographic data. Supports PostGIS databases, interactive maps, and integration with matplotlib/folium/cartopy. Use for tasks like buffer analysis, spatial joins between datasets, dissolving boundaries, clipping data, calculating areas/distances, reprojecting coordinate systems, creating maps, or converting between spatial file formats.

70

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

72%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, actionable skill body with genuine progressive-disclosure references and strong code examples. The main gaps are repeated content across sections and missing validation checkpoints in the workflows.

Suggestions

Consolidate CRS and geometric-operations content into single sections and remove the 'Detailed Documentation' recap, since each reference is already linked inline where it is introduced.

Add explicit validation checkpoints to workflows (e.g., assert gdf.is_valid.all() and verify matching CRS before spatial joins, then re-check before to_file) so the Load→Transform→Export flow has a feedback loop.

Trim the one-line 'GeoPandas extends pandas to enable spatial operations...' intro, which restates a concept Claude already knows.

DimensionReasoningScore

Conciseness

Mostly code-first and efficient, but CRS and geometric-operation content repeats across Quick Start, Core Concepts, and Common Workflows, and the 'Detailed Documentation' section re-lists references already linked inline.

2 / 3

Actionability

Numerous executable, copy-paste-ready examples with specific APIs (read_file, sjoin, overlay, to_crs, explore) and concrete parameters like bbox, predicate, and use_arrow.

3 / 3

Workflow Clarity

Common Workflows are numbered and sequenced, but lack explicit validation checkpoints or feedback loops despite file writes and batch spatial operations.

2 / 3

Progressive Disclosure

Clear overview with inline, one-level-deep references to real files in references/ (all six referenced paths exist), plus a recap section for easy navigation.

3 / 3

Total

10

/

12

Passed

Description

100%

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 with concrete capabilities and explicit use-when triggers covering both what and when. Slightly verbose due to two near-duplicate trigger clauses, but each clause contributes specific keywords rather than filler.

DimensionReasoningScore

Specificity

Enumerates many concrete actions — buffer analysis, spatial joins, overlay operations, dissolve, clipping, area/distance calculation, reprojection, choropleth mapping, format conversion — rather than vague language.

3 / 3

Completeness

Explicitly states what the library does and includes 'Use when...' and 'Use for tasks like...' clauses that clearly answer when Claude should invoke it.

3 / 3

Trigger Term Quality

Covers natural terms users would say (shapefiles, GeoJSON, GeoPackage, spatial joins, choropleth mapping, geographic data) with good variation across both trigger clauses.

3 / 3

Distinctiveness Conflict Risk

Scoped to geospatial vector data with distinctive, domain-specific triggers unlikely to overlap with unrelated skills.

3 / 3

Total

12

/

12

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
foryourhealth111-pixel/Vibe-Skills
Reviewed

Table of Contents

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.