CC wristclaw
Bridges the WristClaw watch ↔ OpenClaw agent. Recognizes pairing payloads sent via any inbound channel, registers the native WristClaw OpenClaw channel after explicit user confirmation, and keeps replies concise for the watch.
Bridges the WristClaw watch ↔ OpenClaw agent.
As a process C 58/100 · Has gaps — References files that are not bundled: url, ...
ProcedureTelegramWhatsAppData and analyticsAI and agentstype and topics are labelled automatically from the skill text
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- The text references files that are not there: add them or drop the references.
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: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - warning
body-longSKILL.md body ≈ 6839 tokens (recommended < 5000); move details to references/ - warning
missing-refreference to a missing file: url - warning
missing-refreference to a missing file: ... - note
frontmatter-keyunknown frontmatter key "homepage" - note
frontmatter-keyunknown frontmatter key "repository"
Process rating: all ten parameters 58/100
Will not run. References files that are not bundled: url, ...
- 0Tools and files. 2 referenced file(s) missing: url, ...
- 0Inputs and preconditions. Does not say what the process needs to start
- 60Steps. 61 steps, 4 vague phrases
- 60Result and completion. Output format stated, no completion criterion
- 70Execution cost. Instruction body is 6839 tokens
- 100When it triggers. States when to use and when not to
- 100Failures and branches. 3 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Running it twice. Mutating operations check current state
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 11 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)
- +2Single-language instructions
- +3Description length 226: enough signal without eating the budget
- +4Structure: 45 headings
- +3Step-by-step instructions: 61 items
- +3Output format is stated explicitly
- +4Has examples (12 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 55.
External checks
ClawHub: suspicious
The skill is a coherent watch-to-agent channel, but it installs a high-impact external plugin through mutable, unpinned paths that users should review carefully.
LLM: suspicious (medium) · VirusTotal: · 16 Sept 2026