DC trip-protocol
(no description)
Not recommendedlow grade D
As a process C 54/100 · Has gaps — weak spots: result and completion, when it triggers, running it twice
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:53High-entropy token-like string (may be an id, hash or a credential)cast send 0x45…EAf "claim()" \
-
low Secrets in code
secret-high-entropy-tokenSKILL.md:133High-entropy token-like string (may be an id, hash or a credential)cast call 0xd0…f6F \
-
low Secrets in code
secret-high-entropy-tokenSKILL.md:169High-entropy token-like string (may be an id, hash or a credential) (documentation table row)| TripExperience (NFT) | `0xd0…f6F` |
table -
low Secrets in code
secret-high-entropy-tokenSKILL.md:170High-entropy token-like string (may be an id, hash or a credential) (documentation table row)| TripToken ($TRIP) | `0x11…934` |
table -
low Secrets in code
secret-high-entropy-tokenSKILL.md:172High-entropy token-like string (may be an id, hash or a credential) (documentation table row)| TripClaimer (free) | `0x45…EAf` |
table
Files scanned: 14. 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 54/100
- 0Result and completion. Does not say what the result is
- 0When it triggers. No condition that starts the skill
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 2 mutating operations with no state check
- 55Failures and branches. 1 branches
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 29 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1421 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)
- +3Description length 0: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +4Structure: 22 headings
- +3Step-by-step instructions: 29 items
- +4Has examples (10 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 0.
External checks
ClawHub: suspicious
The skill largely does what it claims (temporarily rewrite SOUL.md), but its runtime scripts expect access to private wallet material and call third‑party endpoints that are not declared in the registry metadata, and there are several inconsistencies in scheduling/markers — proceed only after manual review and sandboxing.
LLM: suspicious (medium) · 15 Feb 2026