BC legal-tos-differ
Fetches Terms of Service documents, stores snapshots, and performs semantic diffing to identify meaningful legal changes across Privacy Risks, Financial Changes, and User Rights categories.
As a process C 51/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- 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 · 5
✓ No critical or high findings
Medium and low: 5
-
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:52High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…NxY+fzEC…TMw+Dfs3…h4g==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:120High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…9co+7Zrb…CSH/zJvXw56gmHw==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:161High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…Eg5+wW0/QaZM…swK/w2MWU+Gw==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:240High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…uff+RtWa…OPA==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:252High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…CUH+OiuIgU++RB0+94Nl…dMw==",
detector
Files scanned: 9. 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") - note
frontmatter-keyunknown frontmatter key "tools"
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. 1 mutating operations with no state check
- 100Tools and files. Tools declared in frontmatter
- 100Steps. 9 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 296 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
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 189: enough signal without eating the budget
- +4Structure: 4 headings
- +3Step-by-step instructions: 9 items
Quality base 70; lint remarks subtract, signals add up to 100. Result: 67.
External checks
ClawHub: clean
This skill does what it advertises: it fetches legal pages, saves local snapshots, and compares them, with a disclosed remove command that should be used carefully.
LLM: benign (high) · VirusTotal: · 29 May 2026