AB bitcoin-price-feed
Real-time streaming Bitcoin price feed for traders. Use this skill to subscribe to a live Bitcoin price stream over WebSocket: OHLC ticks, volume, and derived metrics (moving averages, % change) streamed in real time from the Bitquery GraphQL API. ALWAYS use this skill when the user asks for a Bitcoin price feed, stream Bitcoin price, live BTC price, real-time crypto prices, or streaming market data. Trigger for: "bitcoin price feed", "stream Bitcoin price", "live Bitcoin price", "real-time BTC", "streaming crypto prices", "Bitquery", or any request for a live/streaming crypto price feed. Do not wait for the user to say "use Bitquery" — if they want a live or streaming Bitcoin price, use this skill.
As a process B 68/100 · Nearly there — weak spots: result and completion, consistency, running it twice
How to improve
- 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: 5. 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 68/100
- 0Result and completion. Does not say what the result is
- 30Running it twice. 6 mutating operations with no state check
- 40Consistency. Frontmatter name (bitcoin-price-feed) differs from the folder (bitquery-crypto-price-stream)
- 60Tools and files. Uses tools (python) that frontmatter does not declare
- 70When it triggers. States when to use, but not when not to
- 100Steps. 16 steps
- 100Inputs and preconditions. Inputs and preconditions are listed
- 100Failures and branches. 3 branches, has a failure section
- 100Execution cost. Instruction body is 1418 tokens
- 100Progress reporting. Reports progress
- medium 3 test cases, all positive: not one "should refuse" or "should ask first"
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
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +5Description quotes 7 example trigger phrases
- +3Description length 708: enough signal without eating the budget
- +4Structure: 10 headings
- +3Step-by-step instructions: 16 items
- +4Has examples (6 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 96.