CtrlK
BlogDocsLog inGet started
Tessl Logo

globe-gl

Use when implementing globe.gl (Globe.GL) for 3D globe data visualization with WebGL/ThreeJS, including setup, data layers (points, arcs, polygons, labels), and integration patterns in plain HTML or React.

73

Quality

90%

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

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 tight, well-structured body: executable quick-start code in both module and script-tag flavors, a clear sequenced workflow, and a clarifying-questions section, all within ~50 lines. The main gap is that 'Common layers to mention' lists layer names without the layer-specific API fields the workflow promises.

DimensionReasoningScore

Conciseness

Roughly 50 lean lines with no padded explanations or concepts Claude already knows; even tips are one-liners ('Size the container with CSS; the globe fills its parent element.'). Every token earns its place, matching the level 5 anchor rather than level 4's minor over-explanation.

5 / 5

Actionability

Two executable quick-start snippets (ESM and CDN script tag) with real API calls ('.globeImageUrl(myImageUrl)', '.pointsData(myData)'). However, 'Common layers to mention' is a bare name list with no layer-specific fields (e.g. arcsData, pointRadius, polygonsData) despite the workflow promising 'layer-specific fields'. Not level 3 (code is executable, not pseudocode) and not level 5 (common cases beyond points are uncovered).

4 / 5

Workflow Clarity

Four clearly sequenced steps (confirm environment, minimal snippet plus layer fields, extras only if requested, sizing/performance callouts) plus a 'Questions to ask when specs are missing' clarification checkpoint. This is a non-destructive guidance task so no validation loop is needed, and the simple-skill exception applies.

5 / 5

Progressive Disclosure

Single-file skill with no references/scripts/assets bundle to verify, well-organized sections, and no buried or nested references. Per the guideline that skills under 50 lines with no need for external references can score 5 on well-organized sections alone.

5 / 5

Total

19

/

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: it names the specific library, enumerates concrete capabilities, and opens with an explicit 'Use when...' clause containing natural trigger terms. Keyword coverage could add common synonyms such as 'earth' or 'react-globe.gl' to reach the top anchor on trigger quality.

DimensionReasoningScore

Specificity

Names the domain and several concrete actions ('setup, data layers (points, arcs, polygons, labels), and integration patterns in plain HTML or React'), with minor gaps such as no method-level API terms. It is not level 3 (more than 1-2 actions) nor level 5 (coverage is not comprehensive).

4 / 5

Completeness

Explicitly answers both what ('implementing globe.gl... including setup, data layers..., and integration patterns in plain HTML or React') and when ('Use when implementing globe.gl (Globe.GL) for 3D globe data visualization...') with concrete trigger phrases. Not level 4 because the when-clause is fully explicit rather than merely present.

5 / 5

Trigger Term Quality

Good natural keyword coverage: 'globe.gl', 'Globe.GL', '3D globe data visualization', 'WebGL/ThreeJS', 'points, arcs, polygons, labels', 'React'. A few natural variations are missing (e.g. 'earth', 'world map', 'react-globe.gl'), so it falls just below the comprehensive-synonym level 5.

4 / 5

Distinctiveness Conflict Risk

Clear niche naming a specific library (globe.gl) with distinct triggers; minimal conflict risk with other visualization skills. Matches the level 5 anchor rather than level 4, which implies overlap with closely related skills.

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
MengTo/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.