CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

r3f-physics

React Three Fiber physics with Rapier - RigidBody, colliders, forces, joints, sensors. Use when adding physics simulation, collision detection, character controllers, or creating interactive physics-based experiences.

64

Quality

80%

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-physics/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

Highly actionable reference content with clean, executable examples across the API surface, held back by its monolithic single-file structure. The full joint catalog and property listings should be split into reference files, and the character controller case promised by the description is missing.

Suggestions

Split the joint catalog, collider API reference, and world-access sections into bundle files (e.g., references/joints.md, references/api.md), keeping only Quick Start, Installation, and the most common patterns (colliders, forces, collision events) in SKILL.md.

Add a character controller example (e.g., KinematicCharacterController or a kinematic capsule controller) to match the description's explicit trigger, and move Installation ahead of Quick Start.

Trim prop enumerations to the non-obvious properties (ccd, enabledTranslations, lockRotations) and cut boilerplate mesh JSX from examples to reduce token load.

DimensionReasoningScore

Conciseness

The ~820-line body inlines the library's full API surface (every joint type, full prop enumerations, arg tables), much of which Claude already knows or belongs in separate reference files, though prose padding is minimal. Mostly efficient but should be significantly tightened.

3 / 5

Actionability

Code examples are copy-paste ready and cover common cases (quick start, forces, joints, sensors, instancing, collision events), but the description advertises "character controllers" and the body contains no character controller example.

4 / 5

Workflow Clarity

Reference-style skill with a logical progression from basics to advanced topics and no destructive operations requiring validation; minor sequencing gap since Quick Start appears before Installation.

4 / 5

Progressive Disclosure

Good section headers aid navigation, but there are no bundle files at all and roughly 800 lines of API reference are inlined in SKILL.md that clearly belong in separate reference files (joints, collider API, world access).

3 / 5

Total

14

/

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 description that clearly states both capabilities and explicit trigger conditions in third person with concrete API-level specifics. The only weakness is a few missing natural synonyms and slight overlap risk with closely related R3F skills.

DimensionReasoningScore

Specificity

Names the domain plus five concrete capability areas ("RigidBody, colliders, forces, joints, sensors") and concrete actions in the trigger clause ("adding physics simulation, collision detection, character controllers"), giving comprehensive coverage with no notable gaps.

5 / 5

Completeness

Explicitly answers what ("React Three Fiber physics with Rapier - RigidBody, colliders, forces, joints, sensors") and when ("Use when adding physics simulation, collision detection, character controllers, or creating interactive physics-based experiences") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Good natural phrases like "physics simulation", "collision detection", and "character controllers", but misses common variations users would say such as "gravity", "ragdoll", or "game physics".

4 / 5

Distinctiveness Conflict Risk

Clearly niche (Rapier physics within React Three Fiber), but the broad phrase "interactive physics-based experiences" and overlap with sibling skills like r3f-animation create minor conflict risk with closely related skills.

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

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

Warning

Total

15

/

16

Passed

Repository

AzizBelhassan/timeverse

Path

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

Revision

9dc2cb4

Reviewed

Table of Contents

DiscoveryImplementationValidation

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.

Claim skill