CD nansen-holder-analysis
Is this token held by quality wallets or retail noise? SM holder ratio, flow breakdown by label, and recent buyer quality.
Is this token held by quality wallets or retail noise?
As a process D 43/100 · Unfinished process — weak spots: steps, result and completion, when it triggers
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
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 · 0
✓ No critical or high findings
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 43/100
- 0Steps. Prose only: no discrete steps
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 50Failures and branches. 0 branches, has a failure section
- 100Tools and files. Tools declared in frontmatter
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 767 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)
- +4Structure: 2 headings, hard to scan
- +3No numbered steps or checklist
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 122: enough signal without eating the budget
- +4Has examples (1 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 65.
External checks
ClawHub: clean
This skill is a Nansen CLI workflow for token holder-quality analysis, with its authentication and possible paid API behavior disclosed.
LLM: benign (high) · VirusTotal: · 29 Sept 2026