DD zap1-zcash-attestation
(no description)
Not recommendedlow grade D
As a process D 44/100 · Unfinished process — 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 · 6
✓ No critical or high findings
Medium and low: 6
-
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:54High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…3wH+jfWB…yfN+lFri…oov+PzfnxxD5g==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:152High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…wIN//F77/IADDSs58i+MDaO…jeo+YFg==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:779High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…8tJ++Ku97…8Zu+xfBP…2pf+8SGN5/NoytfKgYPIw==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:864High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…x9D+4jKA…w7A==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:879High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…rQc+GZ14…I4P/jsSo…7rC/hms+WclQQ==",
detector -
low Secrets in code
secret-high-entropy-tokenREADME.md:120High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)Proofs are also verifiable on Ethereum via the Solidity verifier at `0x3f…87F` (Sepolia).
quoted
Files scanned: 22. 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 44/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
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 100Steps. 12 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 323 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: 6 headings
- +3Step-by-step instructions: 12 items
- +4Has examples (2 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 0.
External checks
ClawHub: suspicious
This attestation plugin appears purpose-built rather than clearly malicious, but it needs review because it can continuously send agent activity hashes to a remote service and exposes admin API-key creation as an agent tool.
LLM: suspicious (high) · VirusTotal: · 29 May 2026