Three.js post-processing - EffectComposer, bloom, DOF, screen effects. Use when adding visual effects, color grading, blur, glow, or creating custom screen-space shaders.
Install with Tessl CLI
npx tessl i github:cloudai-x/threejs-skills --skill threejs-postprocessing98
Does it follow best practices?
Validation for skill structure
Discovery
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.
This is an excellent skill description that follows best practices. It uses third person voice, provides specific technical capabilities, includes a clear 'Use when...' clause with natural trigger terms, and carves out a distinct niche within the Three.js ecosystem that won't conflict with other 3D graphics skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and techniques: 'EffectComposer, bloom, DOF, screen effects' along with 'visual effects, color grading, blur, glow, custom screen-space shaders' - these are concrete, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what ('Three.js post-processing - EffectComposer, bloom, DOF, screen effects') and when ('Use when adding visual effects, color grading, blur, glow, or creating custom screen-space shaders') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'bloom', 'DOF', 'visual effects', 'color grading', 'blur', 'glow', 'screen-space shaders' - these are terms developers naturally use when seeking post-processing help. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with clear niche: specifically targets Three.js post-processing with unique triggers like 'EffectComposer', 'bloom', 'DOF', 'screen-space shaders' that wouldn't conflict with general 3D or graphics skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an excellent skill file that serves as a comprehensive reference for Three.js post-processing. It provides extensive, executable code examples covering common effects, custom shaders, and performance optimization without unnecessary verbosity. The structure progresses logically from quick start to advanced topics with clear cross-references.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, providing executable code examples without unnecessary explanations. It assumes Claude knows Three.js basics and doesn't waste tokens explaining what post-processing or bloom effects are conceptually. | 3 / 3 |
Actionability | Every section provides complete, copy-paste ready code examples with proper imports. The code is executable, includes parameter comments where helpful, and covers both basic usage and runtime adjustments. | 3 / 3 |
Workflow Clarity | The skill clearly sequences operations (setup composer → add render pass → add effects → use composer.render()). The 'Combining Multiple Effects' section shows explicit ordering with numbered steps, and resize handling is consistently addressed. | 3 / 3 |
Progressive Disclosure | Content is well-organized with a Quick Start followed by detailed sections for each effect type. References to related skills (threejs-shaders, threejs-textures, threejs-fundamentals) are clearly signaled at the end without deep nesting. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 13 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (603 lines); consider splitting into references/ and linking | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
Total | 13 / 16 Passed | |
Table of Contents
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.