DC contract-reviewer-dongjie
(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) (detector / deny-list definition)"integrity": "sha5…lh5/QnVs…M7y/WU9j+236K…xwI+0sEO…EXw==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:72High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…vqj+UbDfWig+DHr5…CZQ==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:244High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…oyg+GOH3rYX++Kpzr…3Nk+U8XO…syg==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:299High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…vAm+c/Slfz…0Nt+v8wr…WwQ==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:367High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…8CM+MzKM…4lA==",
detector
Files scanned: 6. 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. 8 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 177 tokens
- 100Running it twice. No mutating operations
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
- +1No license
- +2Single-language instructions
- +4Structure: 5 headings
- +3Step-by-step instructions: 8 items
- +4Has examples (0 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 0.
External checks
ClawHub: suspicious
The skill’s code is a simple local contract-text checker, but its marketplace metadata advertises unrelated crypto and purchase capabilities.
LLM: suspicious (medium) · VirusTotal: · 29 May 2026