test-physics
Test Havok physics system (gravity, rigid bodies, static vs dynamic) against the physics example using the iwsdk CLI.
61
72%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.claude/skills/test-physics/SKILL.mdQuality
Discovery
67%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 is technically specific and clearly identifies a narrow domain (Havok physics testing via iwsdk CLI), making it highly distinctive. However, it lacks an explicit 'Use when...' clause which limits its completeness score, and the trigger terms, while accurate, are somewhat narrow and technical without covering common user phrasings.
Suggestions
Add a 'Use when...' clause such as 'Use when the user wants to test or validate Havok physics behavior, run physics simulations, or debug gravity/rigid body issues using the iwsdk CLI.'
Include additional natural trigger terms like 'physics simulation', 'physics engine', 'collision testing', or 'physics validation' to broaden keyword coverage.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: testing Havok physics system with specific aspects (gravity, rigid bodies, static vs dynamic) against a physics example using a named CLI tool (iwsdk CLI). | 3 / 3 |
Completeness | Clearly answers 'what' (test Havok physics system aspects against the physics example using iwsdk CLI) but lacks an explicit 'Use when...' clause or equivalent trigger guidance, which caps this at 2 per the rubric. | 2 / 3 |
Trigger Term Quality | Includes domain-specific terms like 'Havok', 'physics', 'rigid bodies', 'gravity', 'iwsdk CLI' which are relevant but fairly technical. Missing common variations a user might say like 'physics simulation', 'collision', 'physics engine testing'. The terms are natural for the domain but narrow. | 2 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche: Havok physics system testing via iwsdk CLI is very specific and unlikely to conflict with other skills. The combination of 'Havok', 'physics', and 'iwsdk CLI' creates a unique fingerprint. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured, highly actionable test procedure with excellent workflow clarity including validation checkpoints, error recovery, and retry logic. The main weakness is its length — the inline MCPCALL helper and known issues section inflate the document, and the content could benefit from progressive disclosure via supporting files. Overall it serves its purpose effectively as a comprehensive physics system test guide.
Suggestions
Extract the MCPCALL shell function into a separate helper script file (e.g., mcpcall.sh) and reference it from SKILL.md to reduce inline verbosity.
Move the 'Known Issues & Workarounds' section to a separate KNOWN_ISSUES.md file and link to it, keeping SKILL.md focused on the test procedure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly long but most content is necessary for the multi-step test workflow. However, the MCPCALL shell function definition is verbose and could be provided as a referenced script file. Some explanatory notes (e.g., 'This must return JSON with a list of systems') are slightly redundant for Claude. | 2 / 3 |
Actionability | Every step provides exact bash commands with concrete arguments, specific assertion criteria with field names and expected values, and clear pass/fail conditions. The commands are copy-paste ready with only entity index placeholders that are explicitly explained. | 3 / 3 |
Workflow Clarity | The workflow is clearly sequenced (install → start server → verify connectivity → run suites → cleanup) with explicit validation checkpoints at each stage, feedback loops for server failures, a recovery section for transient errors, and retry logic with clear escalation (fail after one retry). | 3 / 3 |
Progressive Disclosure | The content is a monolithic document at ~250 lines. The MCPCALL shell function (~30 lines) and Known Issues section could be split into separate referenced files. However, for a test procedure that needs to be followed sequentially, inline content is somewhat justified. No bundle files are provided to offload content to. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- facebook/immersive-web-sdk
- Commit
b3d1162
- 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.