CtrlK
BlogDocsLog inGet started
Tessl Logo

3d-sky-rays

Add sun shafts and crepuscular rays to a Three.js or equivalent 3D scene, using scene occlusion, a projected sun position, controlled foreground spill, and scalable post-processing. Use for rays of light from the sky, sunlight through trees or roofs, and golden-hour architectural scenes.

72

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

81%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 dense, well-structured technical recipe with clear sequencing, a verification checklist, and justified pseudocode. Its main gaps are a non-executable core example and a referenced REFERENCES.md that is missing from the bundle.

Suggestions

Provide a copy-paste-ready shader/code snippet (e.g. a complete GLSL fragment) in addition to the pseudocode, or in a referenced file, to lift actionability to 5.

Add the missing REFERENCES.md file referenced at the end of the body, or remove/repoint the link, so progressive-disclosure navigation is intact.

Tighten the dense prose in 'Tune appearance before cost' and the occlusion-pass notes to trim a few sentences that assume little, improving conciseness.

DimensionReasoningScore

Conciseness

Mostly lean and assumes competence (e.g. 'uv = ndc.xy * 0.5 + 0.5', 'This is an artistic approximation, not a substitute for depth-integrated volumetric scattering'), with a few dense prose passages that could be tightened; not a 5 because some explanatory sentences are slightly more than minimum.

4 / 5

Actionability

Provides concrete formulas, a justified backend-agnostic pseudocode accumulation core, and specific tuning values (24–48 samples, half-res buffer), but the core example is pseudocode rather than copy-paste executable code, so it stops just short of 5.

4 / 5

Workflow Clarity

The ray pass is laid out as a clear 1–6 sequence, followed by an explicit Verify checklist and debugging guidance ('Whiteout usually means excessive intensity or a bad mask'), providing explicit validation steps and an error-recovery signal.

5 / 5

Progressive Disclosure

Well-organized sections with a single clearly-signaled one-level-deep reference ('Read REFERENCES.md for the source and renderer documentation'); not a 5 because the referenced REFERENCES.md file is not present in the bundle, so navigation is partly broken.

4 / 5

Total

17

/

20

Passed

Description

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

The description is exemplary: third-person, concrete, comprehensive in both capability and trigger coverage, with a distinctive niche. It cleanly answers what and when without padding.

DimensionReasoningScore

Specificity

Lists multiple concrete actions and mechanisms — 'Add sun shafts and crepuscular rays', 'scene occlusion', 'projected sun position', 'controlled foreground spill', 'scalable post-processing' — giving comprehensive coverage of what the skill does.

5 / 5

Completeness

Explicitly answers both what ('Add sun shafts and crepuscular rays to a Three.js... scene, using...') and when ('Use for rays of light from the sky, sunlight through trees or roofs, and golden-hour architectural scenes').

5 / 5

Trigger Term Quality

Natural user phrases are well covered with synonyms — 'sun shafts', 'crepuscular rays', 'rays of light from the sky', 'sunlight through trees or roofs', 'golden-hour architectural scenes' — terms a user would actually say.

5 / 5

Distinctiveness Conflict Risk

A clear niche (3D sky-ray volumetric post-processing) with distinct triggers and named renderer context, giving minimal overlap risk with other skills.

5 / 5

Total

20

/

20

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 1 missing

Warning

Total

15

/

16

Passed

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.