DC china-localization
(no description)
Not recommendedlow grade D
As a process C 51/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- Add a description to the frontmatter: without it the skill never triggers.
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:63High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"integrity": "sha5…xCA+ORZv…wO5/ywWF…Tag==",
quoted -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:81High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"integrity": "sha512-+qIYR…PQd+PJGi…oLv+RhT3…mNQ==",
quoted -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:90High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"integrity": "sha5…GD3+82K6JgJlm/Y+KI92…no5+4jh9sw==",
quoted -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:114High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…MfZ+71RA…HvA==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:120High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"integrity": "sha5…Kxf+MSr9…jrj/FHl8…mYA+ftRkP/3oKQ==",
quoted
Files scanned: 10. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- error
frontmatterSKILL.md: no YAML frontmatter block found - error
name-missingSKILL.md: frontmatter has no `name` - error
description-missingSKILL.md: no `description` — the skill can never trigger
Process rating: all ten parameters 51/100
- 0Result and completion. Does not say what the result is
- 0When it triggers. No condition that starts the skill
- 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
- 100Tools and files. No external tools needed
- 100Steps. 24 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 885 tokens
- 100Running it twice. No mutating operations
- low 14 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)
- +3Description length 0: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- -4Absolute local paths (C:\Users, /home/…): not portable
- -226 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +4Structure: 27 headings
- +3Step-by-step instructions: 24 items
- +4Has examples (9 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 0.
External checks
ClawHub: suspicious
The skill is not clearly malicious, but it asks users to configure broad workspace, messaging, maps, and payment credentials without enough scoping or data-flow explanation.
LLM: suspicious (high) · VirusTotal: · 29 May 2026