CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

r3f-fundamentals

React Three Fiber fundamentals - Canvas, hooks (useFrame, useThree), JSX elements, events, refs. Use when setting up R3F scenes, creating components, handling the render loop, or working with Three.js objects in React.

56

Quality

71%

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

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/r3f-fundamentals/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

The body delivers abundant concrete, executable R3F code, but as a monolithic 780-line inline reference it heavily duplicates knowledge Claude already has and ignores progressive disclosure entirely — no reference files split out the JSX catalog, event properties, or Leva debugging guide. Restructuring into a lean overview plus one-level-deep reference files would fix both the conciseness and structure problems at once.

Suggestions

Split the body into one-level-deep reference files (e.g., references/jsx-elements.md, references/events.md, references/leva-debugging.md) and reduce SKILL.md to a concise overview with clearly signaled links, keeping only the Quick Start inline.

Trim sections that restate what Claude already knows (Canvas Defaults, basic JSX camelCase usage, event bubbling) and move the 130-line Leva guide out of the fundamentals skill or into its own reference, since it documents a third-party tool beyond R3F core.

Fix non-executable example fragments — the Canvas props showcase has a duplicate `camera` prop alongside `orthographic`, and `ConditionalAnimation`/`TriggerRender` use an undeclared `meshRef` — or explicitly label them as prop documentation rather than runnable code.

DimensionReasoningScore

Conciseness

The ~780-line body extensively restates well-known R3F knowledge Claude already has ("All Three.js objects are available as JSX elements (camelCase)", "Events bubble up through the scene graph", Canvas defaults), and the ~130-line Leva debugging guide covers a third-party tool beyond R3F fundamentals. This is noticeably verbose at the section level, matching anchor 2 rather than 3, where padding is only a stray sentence or two.

2 / 5

Actionability

Mostly executable, copy-paste-ready TSX covering Quick Start, hooks, events, refs, and performance patterns. Minor gaps keep it below anchor 5: the Canvas props block is a non-executable showcase (duplicate `camera` prop with `orthographic`), and fragments like ConditionalAnimation and TriggerRender reference a `meshRef` that is never declared.

4 / 5

Workflow Clarity

Organized as a topical API reference rather than a sequenced workflow; the Quick Start gives an entry sequence but there is no guidance for navigating scenarios (e.g., choosing frameloop modes vs. invalidate) or checkpoints. Anchor 3 — structure present but no explicit workflow path; no validation cap applies since nothing destructive or batch-oriented is involved.

3 / 5

Progressive Disclosure

No bundle files exist (no references/, scripts/, or assets/), and roughly 780 lines of API reference — event property tables, JSX element catalog, and the entire Leva guide — are inlined in SKILL.md where a reference file clearly belongs. Internal section headers are good, but per anchor 2 ("content that clearly belongs in separate files is inlined"), file-level structure is effectively monolithic; the See Also list points to sibling skills, not navigable bundle files.

2 / 5

Total

11

/

20

Passed

Description

83%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 explicitly states both what the skill covers and when to use it, with good natural trigger terms including the R3F synonym. The only weaknesses are noun-based rather than action-based capability listing and slight trigger overlap with sibling R3F skills.

DimensionReasoningScore

Specificity

"Canvas, hooks (useFrame, useThree), JSX elements, events, refs" names several concrete capabilities, though as topic nouns rather than action verbs, with minor gaps (extend, primitive, performance patterns are unmentioned). Matches anchor 4 — several specific items with minor coverage gaps — rather than 5, which requires comprehensive action-oriented coverage.

4 / 5

Completeness

Explicitly answers both: what — "React Three Fiber fundamentals - Canvas, hooks (useFrame, useThree), JSX elements, events, refs" — and when — "Use when setting up R3F scenes, creating components, handling the render loop, or working with Three.js objects in React". This mirrors the anchor 5 example structure with concrete multi-trigger phrasing.

5 / 5

Trigger Term Quality

Includes natural terms users would say — "React Three Fiber", "R3F", "Three.js", "render loop", "useFrame" — with the R3F abbreviation synonym covered. Falls short of anchor 5 only because common variations like "3D" or "3D scene in React" are missing.

4 / 5

Distinctiveness Conflict Risk

Clear niche (React Three Fiber in React) with distinct triggers like useFrame and R3F, but "working with Three.js objects in React" is broad enough to also fire for closely related sibling skills (r3f-geometry, r3f-materials, r3f-lighting). Anchor 4 — mostly distinct with minor overlap risk.

4 / 5

Total

17

/

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

skill_md_line_count

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

Warning

Total

15

/

16

Passed

Repository

AzizBelhassan/timeverse

Path

.agents/skills/r3f-fundamentals/SKILL.md

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.