AD luzia
Use this skill whenever the user wants to fetch cryptocurrency prices, stream real-time market data, list exchanges or markets, or retrieve historical OHLCV candlestick data using the Luzia API (luzia.dev). Triggers include: any mention of "Luzia", "crypto price", "BTC/USDT", "exchange ticker", "OHLCV", "real-time price stream", or requests to connect to wss://api.luzia.dev. Also use when the user wants to build trading bots, portfolio trackers, or price alert tools on top of the Luzia platform. Do NOT use for non-Luzia crypto APIs (e.g. CoinGecko, Binance direct) unless the user explicitly wants Luzia as the data source.
As a process D 48/100 · Unfinished process — weak spots: result and completion, inputs and preconditions, failures and branches
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 · 0
✓ No critical or high findings
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- note
frontmatter-keyunknown frontmatter key "homepage"
Process rating: all ten parameters 48/100
- 0Result and completion. Does not say what the result is
- 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
- 30Running it twice. 2 mutating operations with no state check
- 40Consistency. Frontmatter name (luzia) differs from the folder (luzia-crypto-api)
- 60Tools and files. Uses tools (web, python) that frontmatter does not declare
- 100Steps. 19 steps
- 100When it triggers. States when to use and when not to
- 100Execution cost. Instruction body is 3491 tokens
- low 12 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
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +5Description quotes 4 example trigger phrases
- +4Description says when NOT to use the skill
- +3Description length 629: enough signal without eating the budget
- +4Structure: 30 headings
- +3Step-by-step instructions: 19 items
- +4Has examples (22 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 92.