---
name: Intelligence
slug: intelligence
category: AI Engineering
description: Intelligence uses Superior Trade Unified API market data to rank current setups and inspect a single canonical symbol. Use it for “what’s hot” scans or symbol drilldowns, and read the returned evidence instead of treating scores as advice.
github: "https://github.com/Superior-Trade/superior-skills/tree/main/skills/intelligence"
language: JavaScript
stars: 207
forks: 9
install: "npx degit https://github.com/Superior-Trade/superior-skills/tree/main/skills/intelligence ~/.claude/skills/intelligence"
installs_to: ~/.claude/skills/intelligence
source_path: skills/intelligence/SKILL.md
collection_size: 25
category_size: 3101
collection_url: "https://dirskills.com/collections/Superior-Trade/superior-skills"
added: 2026-09-05T05:28:44.236Z
last_synced: 2026-09-05T05:28:44.236Z
canonical_url: "https://dirskills.com/skills/intelligence"
---

# Intelligence

Intelligence uses Superior Trade Unified API market data to rank current setups and inspect a single canonical symbol. Use it for “what’s hot” scans or symbol drilldowns, and read the returned evidence instead of treating scores as advice.

**Install:**

```bash
npx degit https://github.com/Superior-Trade/superior-skills/tree/main/skills/intelligence ~/.claude/skills/intelligence
```

## README

# Intelligence

Use Unified API market intelligence to rank current setups and inspect one
canonical symbol. Read the returned evidence; never treat a score as advice.

## Files in this skill

| File | What it covers |
|---|---|
| [`references/api.md`](references/api.md) | Unified scan/setup parameters and contract-shaped examples. |
| [`references/workflow.md`](references/workflow.md) | Scan → setup → backtest → deploy workflows. |
| [`references/buckets.md`](references/buckets.md) | Optional strategy lenses for interpreting evidence; these are not Unified response categories. |
| [`references/glossary.md`](references/glossary.md) | How to explain common evidence fields without assuming they are always present. |

## Route selection

- List/ranking question → `GET /context/scan`. Use `bucket=all` for an
  open-ended scan, or `alts`/`hip3` when the user narrows the universe. Use
  `category=all` unless they explicitly request `momentum`, `mean_reversion`,
  `breakout`, or `volume`. `top_n` defaults to 10 and must not exceed 50.
- Single-symbol question → first resolve a canonical symbol with
  `GET /context/markets`, then call `GET /context/setup/{symbol}` with the
  URL-encoded canonical value.

## Presenting results

1. State `computed_at` when the response includes it.
2. Present the returned `symbol`, `category`, and `score` without renaming them
   to an older bucket taxonomy.
3. Cite the exact `evidence` values returned for each conclusion.
4. Treat setup fields such as regime, levels, volatility, and funding as
   optional unless they appear in the response.
5. Before recommending capital, apply an appropriate strategy lens, run a
   backtest, and explain the principal risk.

Never manufacture an empty or unavailable scan from training data. Scores are
deterministic market computations, not guarantees or a signal service.