BC ta-radar
Multi-Dimensional Technical Analysis Radar for cryptocurrencies. Supports spot trading pairs (Binance/Gate.io) and on-chain contract addresses (via DexScreener proxy). Generates objective TA reports including EMA, RSI, MACD, Bollinger Bands, support/resistance levels and trend analysis.
As a process C 62/100 · Has gaps — weak spots: result and completion, when it triggers, progress reporting
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- 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 · 2
✓ No critical or high findings
Medium and low: 2
-
low Secrets in code
secret-high-entropy-tokenREADME.md:45High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)TA_SYMBOL="0x90…6be" python3 ta_radar_run.py
quoted -
low Secrets in code
secret-high-entropy-tokenREADME.md:129High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)TA_SYMBOL="0x90…6be" python3 ta_radar_run.py
quoted
Files scanned: 4. 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") - warning
body-longSKILL.md body ≈ 6453 tokens (recommended < 5000); move details to references/ - note
frontmatter-keyunknown frontmatter key "requires"
Process rating: all ten parameters 62/100
- 0Result and completion. Does not say what the result is
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 60Tools and files. Uses tools (bash, web, python) that frontmatter does not declare
- 70Inputs and preconditions. Inputs and preconditions are listed
- 70Execution cost. Instruction body is 6453 tokens
- 100Steps. 6 steps
- 100Failures and branches. 4 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Running it twice. Mutating operations check current state
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)
- -41 reference files, but SKILL.md never points to them: the model will not open them
- +1No license
- +2Single-language instructions
- +3Description length 287: enough signal without eating the budget
- +4Structure: 34 headings
- +3Step-by-step instructions: 6 items
- +3Output format is stated explicitly
- +4Has examples (4 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 60.