SKILLEMALL.ai

BD threejs-interaction

Picking with raycasting, camera controls, transform gizmos, drag, hover and box selection for three.js, identical under WebGL and WebGPU. Use when handling mouse, touch or keyboard input, detecting clicks on 3D objects, adding camera controls, or making scene objects interactive.

CloudAI-X/threejs-skills Agent Skills author: CloudAI-X MIT 1 file body ≈ 5 487 tokens Open the sourcegithub.com↗ analyzed 4 h ago

Picking with raycasting, camera controls, transform gizmos, drag, hover and box selection for three.js, identical under WebGL and WebGPU. Use when handling…

As a process D 49/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions

GeneratorSoftware developmentWriting and documentstype and topics are labelled automatically from the skill text
JSON
Technical rating
B
90/100
safety, quality, tests
Safety 60%
100
Quality 40%
74
Run on models
none yet
Process rating
D
49/100
Unfinished process
Result and completion w 14
0
Inputs and preconditions w 11
0
Failures and branches w 10
0
the three weakest of ten parameters · all ten

How to improve

  1. The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
For the model run — optional
  • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
  • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

Guard findings · 0

✓ No critical or high findings

Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning body-long SKILL.md body ≈ 5487 tokens (recommended < 5000); move details to references/
  • note edit-residue the text marks something as outdated (lines 477): check that old rules are not kept next to new ones — the full check reads the text for contradictions

Process rating: all ten parameters 49/100

  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Failures and branches. Linear process with no failure handling
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 4 mutating operations with no state check
  • 70Execution cost. Instruction body is 5487 tokens
  • 100Tools and files. No external tools needed
  • 100Steps. 19 steps
  • 100Consistency. Name and required fields are in place
  • low 10 top-level sections: this looks like several domains in one skill

Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

Quality signals

  • +5Description has no quoted example phrases that should trigger the skill
  • +4Description does not say when NOT to use the skill (false activations)
  • +3Output format is not stated: the model decides each time
  • +1No license
  • +2Single-language instructions
  • +3Description length 280: enough signal without eating the budget
  • +4Structure: 20 headings
  • +3Step-by-step instructions: 19 items
  • +4Has examples (17 code blocks)

Quality base 70; lint remarks subtract, signals add up to 100. Result: 74.