CtrlK
BlogDocsLog inGet started
Tessl Logo

r3f-postprocessing

React Three Fiber post-processing - @react-three/postprocessing, bloom, DOF, screen effects. Use when adding visual effects, color grading, blur, glow, or creating custom screen-space shaders.

68

Quality

82%

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

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

Excellent actionability and conciseness with runnable examples throughout, but the skill is a monolithic wall of inlined reference material that should be split into separate files for progressive disclosure.

Suggestions

Move the full Blend Functions enumeration and the per-effect complete API reference into a separate references file (e.g., EFFECTS_REFERENCE.md), keeping only the most common effects inline in SKILL.md with one-level-deep links.

Add a brief "Common workflow" section that sequences effect selection → tuning → mobile/performance fallback so the recipe has an explicit ordered path rather than only isolated examples.

Trim a few obvious inline prop comments (e.g., on lines where the prop name already self-documents) to further tighten the already-lean body.

DimensionReasoningScore

Conciseness

No preamble explaining R3F or post-processing basics; every section is a tight, runnable example with inline prop comments that each earn their place, matching the "lean and efficient" anchor.

5 / 5

Actionability

Copy-paste-ready TSX for ~20 effects plus a full custom Effect class, wrapEffect pattern, conditional/animated effects, and a mobile-adaptive performance example — fully executable across common cases.

5 / 5

Workflow Clarity

This is a reference/recipe skill with no multi-step process or destructive/batch operation needing validation checkpoints; only implicit ordering hints ("Anti-aliasing should be last") exist, so it sits at the sequence-present-but-checkpoints-absent anchor.

3 / 5

Progressive Disclosure

A ~760-line monolithic SKILL.md with no bundle files; the full blend-function enumeration and every effect's complete API are inlined at one level rather than split into one-level-deep reference files, though section headers provide some structure.

2 / 5

Total

15

/

20

Passed

Description

88%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, concrete description with an explicit "Use when" trigger clause and good natural keyword coverage. It is distinct and actionable, with only minor gaps in trigger-term synonyms and a slight overlap risk with adjacent r3f skills.

DimensionReasoningScore

Specificity

Names the library and multiple concrete capabilities — "bloom, DOF, screen effects", "color grading, blur, glow", "creating custom screen-space shaders" — with broad coverage rather than just 1-2 actions.

5 / 5

Completeness

Explicitly states both what the skill does (library + capabilities) and when to use it via a concrete "Use when adding visual effects, color grading, blur, glow, or creating custom screen-space shaders" clause.

5 / 5

Trigger Term Quality

Includes natural user-facing terms ("visual effects", "color grading", "blur", "glow") but misses a few synonyms or the package name users might actually say, so it falls just short of comprehensive.

4 / 5

Distinctiveness Conflict Risk

Anchored to a specific package and a clear R3F post-processing niche with distinct triggers; minor overlap risk with sibling shader/material skills keeps it just below a 5.

4 / 5

Total

18

/

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (760 lines); consider splitting into references/ and linking

Warning

Total

15

/

16

Passed

Repository
AzizBelhassan/timeverse
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.