CtrlK
BlogDocsLog inGet started
Tessl Logo

globe-particles

Create a globe-like 3D particle visualization with a dense luminous spherical core and thinner orbital ring or flattened disc. Use when a design needs a premium planetary, orbital, synthesized data-globe effect rendered with real WebGL/Three.js particles, not generic starfields or full page layout changes.

70

Quality

85%

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

82%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 highly actionable, executable recipe skill with clean structure and a useful closing verification checklist. Its main weaknesses are mild redundancy across the Taste Rules/Avoid/Quick Checks sections and inlining the entire code recipe rather than splitting it into reference files.

Suggestions

Consolidate the overlapping guidance in 'Taste Rules', 'Avoid', and 'Quick Checks' — e.g., the globe-silhouette and restrained-glow points each appear in multiple sections; stating each once and letting the checklist verify them would trim tokens without losing coverage.

Move the full Three.js recipe (init/geometry/shader code) into a scripts or reference file and keep a short integration snippet plus the tuning knobs in SKILL.md to improve progressive disclosure.

Add a brief failure-mode note to the workflow (WebGL context unavailable, --brand-accent not resolving at runtime) so the integration has an explicit feedback checkpoint.

DimensionReasoningScore

Conciseness

Prose sections ("Scope", "Visual Target", "Tuning Knobs") are lean bullets with no explanations of concepts Claude already knows, but "Taste Rules", "Avoid", and "Quick Checks" restate overlapping ideas (e.g., the globe-vs-starfield silhouette and restrained-glow points each appear twice or more), which keeps it at anchor 4 rather than fully lean anchor 5.

4 / 5

Actionability

Quotes: complete executable HTML ("<canvas class=\"globe-particles-canvas\" data-globe-particles>"), CSS, GLSL vertex/fragment shaders, and a full "initGlobeParticles" function with defaults, reduced-motion handling, resize, and a cleanup return disposing geometry/material/renderer. This is copy-paste ready code covering the common case, matching anchor 5.

5 / 5

Workflow Clarity

The single integration task is clearly sequenced (markup -> CSS -> shader -> Three.js recipe -> tuning knobs -> "Quick Checks" verification checklist), and the closing checklist provides checkpoints. It is not anchor 5 because there are no feedback loops for likely failure modes (e.g., WebGL unavailable, --brand-accent resolving empty), though the skill is non-destructive so no workflow cap applies.

4 / 5

Progressive Disclosure

The body is well-organized into clear sections with no nested or dead references, and no bundle directories exist to verify against. However, roughly 170 lines of the Three.js recipe are inlined in SKILL.md where a scripts/references split would keep the overview lean, placing it at anchor 4 (good structure, minor organization gaps) rather than anchor 5's ideal split.

4 / 5

Total

17

/

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 clearly states what the skill builds and when to use it, with explicit negative triggers that sharply reduce misfire risk. Trigger-term coverage is good but could add a few more natural synonyms (sphere, planet).

DimensionReasoningScore

Specificity

Quotes: "Create a globe-like 3D particle visualization with a dense luminous spherical core and thinner orbital ring or flattened disc", "rendered with real WebGL/Three.js particles". The deliverable and rendering tech are concrete with explicit exclusions, but it centers on a single action (create) rather than the several distinct actions of anchor 5, sitting above anchor 3's minimal 1-2 actions.

4 / 5

Completeness

Quotes: "Create a globe-like 3D particle visualization with a dense luminous spherical core and thinner orbital ring" (what) and "Use when a design needs a premium planetary, orbital, synthesized data-globe effect... not generic starfields or full page layout changes" (when). Both what and when are explicit with concrete trigger phrases, matching the anchor-5 exemplar; third-person voice is used throughout.

5 / 5

Trigger Term Quality

Natural trigger phrases present: "globe", "particle", "planetary", "orbital", "data-globe", "WebGL/Three.js", plus the contrast term "starfields". Coverage is good but misses common synonyms like "sphere", "planet", or "3D background", so it falls between anchors 4 and 5.

4 / 5

Distinctiveness Conflict Risk

Quotes: "not generic starfields or full page layout changes" — the description carves out a clear niche and actively differentiates from the nearest competing skills, so conflict risk is minimal per anchor 5.

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.