CtrlK
BlogDocsLog inGet started
Tessl Logo

geomaster

Comprehensive geospatial science skill covering remote sensing, GIS, spatial analysis, machine learning for earth observation, and 30+ scientific domains. Supports satellite imagery processing (Sentinel, Landsat, MODIS, SAR, hyperspectral), vector and raster data operations, spatial statistics, point cloud processing, network analysis, cloud-native workflows (STAC, COG, Planetary Computer), and 8 programming languages (Python, R, Julia, JavaScript, C++, Java, Go, Rust) with 500+ code examples. Use for remote sensing workflows, GIS analysis, spatial ML, Earth observation data processing, terrain analysis, hydrological modeling, marine spatial analysis, atmospheric science, and any geospatial computation task.

65

Quality

78%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/geomaster/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

Highly actionable content with strong copy-paste-ready examples and a reasonable reference structure, but it is verbose for an overview (citation boilerplate, known-concept explainers, repeated opener), lacks an end-to-end validated workflow, and leaves one bundle file (specialized-topics.md) orphaned from navigation.

Suggestions

Link specialized-topics.md from the 'Detailed Documentation' list (or remove the file) so every bundle file is reachable from the overview.

Move the inline 'Image Classification' and 'Modern Cloud-Native Workflows' sections into machine-learning.md and big-data.md respectively, keeping only a brief pointer in the body to improve progressive disclosure and conciseness.

Add an explicit validate-then-retry feedback loop to the batch classification example (e.g., sanity-check predicted class distribution / output raster before writing) so workflow_clarity can exceed the batch-operation cap of 3.

Trim the OGC-standards/CRS basics explainers and the citation-boilerplate section, and drop the repeated opening summary line, to tighten token efficiency.

DimensionReasoningScore

Conciseness

Mostly tight, actionable code, but it includes unnecessary material Claude already knows (the OGC-standards and basic-CRS explainers), a ~15-line citation-boilerplate section unrelated to the task, and an opening line that repeats the frontmatter description; the ~375-line body could also be tightened by pushing more inline examples into the existing reference files.

3 / 5

Actionability

Packed with copy-paste-ready, executable Python for the common cases (NDVI from Sentinel-2, GeoPandas spatial join, GEE time series, RF classification, STAC+Planetary Computer load, COG read/write/validate) with real library calls and parameters, matching the fully-executable/common-cases 5 anchor.

5 / 5

Workflow Clarity

The body is a topic catalog rather than a coherent sequenced workflow; scattered checkpoints exist (CRS assert, cog_validate, geometry is_valid) but the batch classification example predicts and writes output with no validation feedback loop, triggering the cap-at-3 rule for batch operations without validation.

3 / 5

Progressive Disclosure

Good one-level-deep structure with a clearly labeled 'Detailed Documentation' section pointing to 13 reference files, but specialized-topics.md exists in references/ yet is never linked from the body (orphaned, unnavigable), and some heavy inline sections (Image Classification, Cloud-Native Workflows) overlap content that has dedicated reference files — minor organization gaps that keep it below 5.

4 / 5

Total

15

/

20

Passed

Description

87%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 description that explicitly covers what the skill does and when to use it with concrete, domain-specific triggers and low conflict risk. It loses a little on specificity and trigger quality due to marketing padding ('30+ domains', '500+ examples') and missing common file-extension synonyms.

DimensionReasoningScore

Specificity

Lists several concrete capability areas ('satellite imagery processing', 'vector and raster data operations', 'point cloud processing', 'network analysis', 'cloud-native workflows'), but the action list is diluted by marketing-style over-claims ('30+ scientific domains', '500+ code examples', '8 programming languages') that the rubric penalizes as fluff, keeping it just below the comprehensive-and-clean 5 anchor.

4 / 5

Completeness

Explicitly answers both 'what' (the enumerated processing/analysis capabilities) and 'when' via a concrete 'Use for ...' trigger clause listing specific task types, matching the 5 anchor that requires clear what-and-when with concrete trigger phrases.

5 / 5

Trigger Term Quality

Good natural-term coverage in the 'Use for' clause ('remote sensing workflows', 'GIS analysis', 'spatial ML', 'terrain analysis', 'hydrological modeling') plus mission names (Sentinel, Landsat, MODIS), but common file extensions and synonyms users say (.tif/.shp/.geojson, 'raster', 'shapefile') are absent from the trigger phrases, so it stops short of the 5 anchor.

4 / 5

Distinctiveness Conflict Risk

Occupies a clearly distinct geospatial niche with domain-specific triggers (Sentinel/Landsat, SAR, hyperspectral, STAC, COG) unlikely to fire for a non-geospatial skill, matching the clear-niche/minimal-conflict 5 anchor; the catch-all 'any geospatial computation task' is still geospatial-scoped.

5 / 5

Total

18

/

20

Passed

Validation

100%

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
K-Dense-AI/scientific-agent-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.