# Explore Crypto Market Data with BlackForge

Crypto market questions require precise metric definitions, exchange identifiers, and reliable time windows. BlackForge connects those questions to its MCP tools or CLI and explains returned measurements with units and quality context.

## Install

```bash
npx skillstore add blackforge-so/blackforge
```

## Metadata

- Status: approved
- Slug: blackforge-so-blackforge
- Skillstore revision: r1
- Version status: missing
- Tree hash: 27ca902c2a9126c524cb0fb89026d31a5dc01dad81e91bbe07ec8e9852bbd952
- Author: blackforge-so
- GitHub username: blackforge-so
- License: MIT
- Repository: https://github.com/blackforge-so/skill/tree/b87e294feb12e6582cf98eb9782ff297f38fb028/
- Ref: ebcb2eb7ad397e055696549961e5b4f8cfeb7ea5
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: network, filesystem, env\_access, external\_commands
- Quality score: 74
- Public page: https://skillstore.pages.dev/skills/blackforge-so-blackforge
- Manifest: https://skillstore.pages.dev/api/skills/blackforge-so-blackforge/manifest

## Capabilities

- Discover exchange identifiers, metric definitions, units, and plan requirements through the public BlackForge catalog.
- List available trading pairs using each exchange's native symbol format.
- Retrieve the latest completed market snapshot with selected columns and quality flags.
- Retrieve metric time series and derive bid-ask spreads from matching best bid and best ask timestamps.
- Explain liquidity, trade flow, trade timing, and enrichment measurements using documented units and quality context.
- Report account usage, remaining monthly rows, omitted columns, and plan restrictions.

## Use Cases

- Review Spot Market Liquidity: Inspect resting liquidity and taker volume for a specified pair, with clear units, snapshot timing, and data quality caveats.
- Compare Historical Measurements: Retrieve aligned time series and compare measured spreads or trade flow across periods without treating observations as forecasts.
- Check Data Access and Consumption: Confirm available pairs, account usage, and plan restrictions before integrating BlackForge measurements into a reporting workflow.

## Prompt Templates

### Find Available Pairs

```
Use BlackForge to list Kraken pairs quoted in USDT. Confirm exchange and symbol identifiers before presenting the results.
```

### Read a Latest Snapshot

```
Show the latest ETHUSDT bid depth within 5% on Binance. Include units, quality flags, and the actual completed bucket length.
```

### Compare Taker Trade Flow

```
Compare SOLUSDT taker buy and sell volume on Binance over the last 24 hours. State the UTC range, supported interval, and quality caveats.
```

### Derive a Historical Spread

```
Derive BTC-USDT bid-ask spreads on OKX for the last seven days from best bid and ask series. Align timestamps and report plan restrictions.
```

## Limitations

- Requires a configured BlackForge MCP server or CLI and an API key for authenticated queries.
- Available venues, columns, history, and intervals depend on the API key's plan and remaining quota.
- Reads completed windows only; it does not operate live formulas, notifications, or order execution.
- Provides measurements rather than trading recommendations; external client implementations and service coverage are not bundled.

## Best Practices

- Confirm metric keys and native exchange symbols through the catalog and pair list before querying.
- Include quality flags, units, UTC timestamps, and the actual plan-supported interval when reporting measurements.
- Use reviewed, version-pinned clients and keep API credentials outside command arguments, shared configuration, and version control.

## Anti Patterns

- Treating resting liquidity, trade flow, or historical spreads as buy or sell recommendations.
- Guessing metric keys, confusing percent depth bands with basis points, or requesting non-queryable identity fields.
- Interpreting omitted columns or silently shortened history as proof that the underlying data does not exist.

## Security Audit

- Audited at: 2026-10-12T17:15:26.244\+00:00
- Summary: The static alerts reflect documentation syntax, market vocabulary, public catalog access, and intended authentication rather than demonstrated malicious behavior. Two semantic risks remain: automatic execution of unpinned npm clients and credential exposure through documented command arguments. No evidence found of prompt injection, deliberate credential theft, or unrelated sensitive-file access in the reviewed sources.

## Stats

- Views: 0
- Downloads: 0
- Favorites: 0
- Popularity score: 0