CtrlK
BlogDocsLog inGet started
Tessl Logo

test-physics

Test Havok physics system (gravity, rigid bodies, static vs dynamic) against the physics example using the iwsdk CLI.

62

Quality

73%

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

Quality

Content

88%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 content is highly actionable and exceptionally well-sequenced, with executable commands, explicit assertions, validation checkpoints, and recovery loops throughout. It is token-efficient and well-structured for a self-contained test-runner skill with no external bundle files.

DimensionReasoningScore

Conciseness

The body is mostly lean, leading with executable commands and assertions rather than explaining concepts Claude already knows; only minor instances (repeated IMPORTANT callouts and a few parenthetical notes) could be trimmed, sitting just above the efficient midpoint.

4 / 5

Actionability

Commands like 'npx iwsdk ecs query --input-json ...' and 'npx iwsdk ecs diff --input-json {"from":"before-fall","to":"after-fall"}' are fully executable and copy-paste ready, with specific assertions covering the common cases comprehensively.

5 / 5

Workflow Clarity

A clear 5-step sequence with explicit validation checkpoints ('Assert: ...' after each command), a Recovery feedback loop with retry logic, and a Known Issues section match the explicit-validation-with-feedback-loops anchor.

5 / 5

Progressive Disclosure

No bundle files exist, so scoring is against the single-file structure; sections (Steps 1-5, suites, Recovery, Known Issues) are well organized and self-contained for a test-runner skill, with only minor organization gaps versus the clear-overview anchor.

4 / 5

Total

18

/

20

Passed

Description

58%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 clearly names a specific domain and tool but omits any explicit 'when to use' trigger guidance, capping completeness. It is specific and distinct but slightly heavy on technical jargon over natural user phrasing.

Suggestions

Append a 'Use when...' clause naming natural triggers, e.g. 'Use when the user asks to verify or debug the Havok physics example, gravity behavior, or rigid-body dynamics.'

Soften jargon with natural synonyms users would say, such as 'physics', 'gravity test', and 'test the physics demo'.

Keep the concrete aspect list (gravity, rigid bodies, static vs dynamic) which is the description's strongest asset.

DimensionReasoningScore

Specificity

Quotes 'Test Havok physics system (gravity, rigid bodies, static vs dynamic) against the physics example using the iwsdk CLI' name the domain and several concrete aspects plus the tool, listing several specific actions with only minor gaps in coverage versus the comprehensive anchor.

4 / 5

Completeness

The 'what' is clear (test the Havok physics system), but there is no 'Use when...' clause or equivalent explicit trigger guidance, which per the rubric caps completeness at 3.

3 / 5

Trigger Term Quality

Terms like 'Havok', 'rigid bodies', 'static vs dynamic', and 'iwsdk CLI' are relevant but lean technical; common natural phrasings such as 'physics', 'gravity', or 'test physics' are present only implicitly, so coverage misses common variations and synonyms.

3 / 5

Distinctiveness Conflict Risk

The narrow niche of Havok physics testing via the iwsdk CLI is mostly distinct from other skills, with only minor overlap risk against closely related test-runner skills.

4 / 5

Total

14

/

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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
facebook/immersive-web-sdk
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.