BC dexscreener
Query DexScreener API for token prices, market data, trending pools, and memecoin categories. Automatically installs @kilincarslan/dexscreener-cli if not present. Use for trading research, token discovery, liquidity analysis, and market trend monitoring via 13 CLI commands that return structured JSON data.
Query DexScreener API for token prices, market data, trending pools, and memecoin categories.
As a process C 62/100 · Has gaps — weak spots: when it triggers, inputs and preconditions, consistency
How to improve
- 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 · 1
✓ No critical or high findings
Medium and low: 1
-
low Secrets in code
secret-high-entropy-tokenSKILL.md:52High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)- `base…f82`
quoted
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 62/100
- 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
- 40Consistency. Frontmatter name (dexscreener) differs from the folder (dexscreener-cli)
- 50Failures and branches. 0 branches, has a failure section
- 60Result and completion. Output format stated, no completion criterion
- 100Tools and files. No external tools needed
- 100Steps. 13 steps
- 100Execution cost. Instruction body is 712 tokens
- 100Running it twice. No mutating operations
- low 11 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (7 tags): a typed call is more reliable
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)
- +1No license
- +2Single-language instructions
- +3Description length 307: enough signal without eating the budget
- +4Structure: 16 headings
- +3Step-by-step instructions: 13 items
- +3Output format is stated explicitly
- +4Has examples (5 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 87.