AC methodalgo-market-intel-explorer
Fetch MethodAlgo crypto market intelligence with methodalgo-cli. Use when: checking crypto news, trading signals, token unlocks, ETF flows, chart snapshots, economic calendar events, macro data, BTC/ETH dominance, total crypto market cap, Fear & Greed, Altseason Index, or Binance public spot/futures prices, ticker, movers, order books, trades, klines, funding, OI, long/short sentiment, basis, exchange-info, and allowlisted raw endpoints.
As a process C 62/100 · Has gaps — weak spots: inputs and preconditions, running it twice, progress reporting
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: 7. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- note
frontmatter-keyunknown frontmatter key "credentials" - note
frontmatter-keyunknown frontmatter key "provenance"
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
- 30Running it twice. 1 mutating operations with no state check
- 50When it triggers. No condition that starts the skill
- 60Tools and files. Uses tools (bash, web, node) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 70Failures and branches. 4 branches
- 100Steps. 40 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2458 tokens
- low The response is described with custom markup (5 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 441: enough signal without eating the budget
- +4Structure: 9 headings
- +3Step-by-step instructions: 40 items
- +3Output format is stated explicitly
- +4Has examples (4 code blocks)
- +4Reference files are cited in the instructions (5 of 5)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 89.