DC tyt
(no description)
Not recommendedlow grade D
As a process C 53/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-tokenSKILL.md:56High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)paymentAsset: "0x83…913", // Base USDC
quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:81High-entropy token-like string (may be an id, hash or a credential) (documentation table row)| Base | `eip155:8453` | 8453 | `0x83…913` |
table -
low Secrets in code
secret-high-entropy-tokenSKILL.md:82High-entropy token-like string (may be an id, hash or a credential) (documentation table row)| Peaq | `eip155:3338` | 3338 | `0xbb…d10` |
table -
low Secrets in code
secret-high-entropy-tokenSKILL.md:83High-entropy token-like string (may be an id, hash or a credential) (documentation table row)| Avalanche | `eip1…114` | 43114 | `0xB9…a6E` |
table -
low Secrets in code
secret-high-entropy-tokenSKILL.md:321High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)const BASE_USDC = "0x83…913";
quoted
Files scanned: 3. 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 53/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
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 2 mutating operations with no state check
- 50Failures and branches. 0 branches, has a failure section
- 100Tools and files. No external tools needed
- 100Steps. 21 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3828 tokens
- 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
- +1No license
- +2Single-language instructions
- +4Structure: 33 headings
- +3Step-by-step instructions: 21 items
- +4Has examples (20 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 0.
External checks
ClawHub: suspicious
This is coherent Teneo SDK documentation, but it teaches wallet-private-key authentication and paid USDC agent calls without strong safeguards against exposing keys or unintended spending.
LLM: suspicious (medium) · VirusTotal: benign · 28 May 2026