Crypto charting with USD pricing (1s)

ReviewAudited by ClawScan on May 1, 2026.

Overview

This skill appears to do what it claims—stream public crypto chart data from Bitquery—but it needs careful handling of a Bitquery API key and an unpinned Python dependency.

Install only if you are comfortable providing a Bitquery API key that must be embedded in the WebSocket URL. Use an isolated virtualenv or container, avoid logging full URLs, consider running with `--timeout`, monitor quota usage, and rotate the key if you suspect it was captured.

Findings (4)

Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.

What this means

If the full WebSocket URL is captured, someone could use your Bitquery token and consume your account quota.

Why it was flagged

The skill requires a provider API token and passes it in the URL. This is disclosed and purpose-aligned, but URL-based tokens can leak through logs, proxies, shell history, debuggers, or monitoring tools.

Skill content
Bitquery's streaming endpoint accepts the token **only in the WebSocket URL** as a query parameter (`?token=...`).
Recommendation

Use a dedicated, rotatable Bitquery key; set it only via environment variable; avoid logging full URLs; run in an isolated environment; rotate the key if exposure is suspected.

What this means

Users may need to set the API key manually and may not get normal credential-handling prompts from the installer.

Why it was flagged

The registry metadata does not cleanly declare the required `BITQUERY_API_KEY`, even though the skill instructions require it. This may prevent installers from clearly prompting for the credential.

Skill content
Required env vars: [object Object] ... Env var declarations: none ... Primary credential: none
Recommendation

The publisher should fix the registry metadata to explicitly declare `BITQUERY_API_KEY` as a required environment variable or credential.

What this means

Running it without a timeout may consume Bitquery quota, generate large logs, or keep an agent session busy.

Why it was flagged

The default runtime is a continuous, all-token live stream. This matches the stated purpose, but it can run indefinitely and produce a large amount of output or provider usage.

Skill content
Streams 1-second ticks for all tokens until interrupted (Ctrl+C) or optional --timeout seconds.
Recommendation

Use `--timeout` for tests, monitor provider quota, and avoid enabling verbose logging around the WebSocket connection.

What this means

A future dependency version could introduce breaking changes or unexpected behavior.

Why it was flagged

The required Python dependency is not version-pinned. The dependency is central to the WebSocket purpose, but unpinned packages can change behavior across installs.

Skill content
gql[websockets]
Recommendation

Install in a virtualenv or container and consider pinning a reviewed version of `gql[websockets]` before production use.