SKILLEMALL.ai

BC s2-light-perception

S2-SP-OS Light Radar. Real LAN UDP discovery and local API calls (Hue/Wiz) to create a 4sqm voxel light memzero. / S2-SP-OS 光之雷达。真实的局域网UDP发现与本地API调用,逆向推算4平米光线记忆体。

ClawHub Agent Skills author: MilesXiang v1.0.2 MIT-0 3 files body ≈ 434 tokens Open the sourceclawhub.ai analyzed 2 d ago

As a process C 51/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions

IntegrationInfrastructuretype and topics are labelled automatically from the skill text
JSON
Technical rating
B
87/100
safety, quality, tests
Safety 60%
100
Quality 40%
67
Run on models
none yet
Process rating
C
51/100
Has gaps
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. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
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: 3. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")
  • note frontmatter-key unknown frontmatter key "homepage"

Process rating: all ten parameters 51/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. 2 mutating operations with no state check
  • 100Tools and files. Tools declared in frontmatter
  • 100Steps. 4 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 434 tokens

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
  • +4No input/output examples
  • +1No license
  • +2Single-language instructions
  • +3Description length 162: enough signal without eating the budget
  • +4Structure: 3 headings
  • +3Step-by-step instructions: 4 items

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

External checks

ClawHub: clean
The skill openly describes and implements local smart-light discovery and read-only light-state checks, with no evidence of hidden exfiltration, persistence, or destructive behavior.
LLM: benign (high) · VirusTotal: · 29 May 2026