Teach your AI agentto use BytNode.
Seven open skills. Installed once, your AI agent reads the right units, stays within your plan and recovers from errors.
Open source under MIT, in the Agent Skills format that Claude, Codex, Cursor and 70+ other AI agents read.
Browse the repositorywithout leaving the page.
c01f18cNov 9, 20266 commitsThe real bytnode/bytnode-skills, as GitHub shows it. Open the folders, read a SKILL.md, go back up.
Open a skillRead the README,from top to bottom.
Every install method and how the skills stay in step with the API. Scroll inside it, open the outline, or switch to the license.
Jump toAgent skills that teach an AI agent (Claude, Codex, Cursor, the BytNode-AI app…) to use BytNode, the crypto market-data API — correctly, the first time.
BytNode serves aggregated market data on the largest crypto pairs: candles and trades, order flow, derivatives (funding, open interest, basis, liquidations), options, technical indicators, on-chain, spot ETFs, macro and sentiment — over REST, a real-time WebSocket and a native MCP server. These skills carry what an agent needs to know and would otherwise get wrong: units, bucket timing, pagination, plan limits, error recovery, and how to read the numbers.
| Skill | Use it when the agent… |
|---|---|
bytnode-api | calls the REST API or writes code against it (the foundation: auth, discovery, units, time, pagination, errors) |
bytnode-mcp | answers questions through the BytNode MCP server's tools |
bytnode-market-analysis | interprets funding, open interest, basis, CVD, liquidations, options, sentiment or macro |
bytnode-history-backtest | downloads history for a backtest, a dataset or a chart |
bytnode-realtime-stream | builds on the WebSocket stream (trades, liquidations, order books) |
bytnode-sdk | uses the official Python or TypeScript SDK |
bytnode-market-brief | writes a market report or daily brief from BytNode data |
The seven skills follow the open Agent Skills format (one folder per skill, a SKILL.md inside), so the same files work in every agent below. Install all of them: each skill is only loaded when a task needs it.
Plugin marketplace (recommended — one command to update later):
/plugin marketplace add bytnode/bytnode-skills
/plugin install bytnode@bytnode
Update: /plugin marketplace update bytnode. Or, from a terminal, with the skills CLI (Node.js 18+):
npx skills add bytnode/bytnode-skills -a claude-code -g # -g: every project (~/.claude/skills)
# without -g: this project (.claude/skills)
From a terminal:
npx skills add bytnode/bytnode-skills -a codex -g # -g: ~/.agents/skills, every repo
# without -g: .agents/skills of this repo
Or ask Codex itself, at its prompt, with the built-in installer (it writes to ~/.codex/skills). Give it the path of each skill — a URL to the whole skills/ folder is refused:
$skill-installer install from the repo bytnode/bytnode-skills the paths skills/bytnode-api skills/bytnode-mcp skills/bytnode-market-analysis skills/bytnode-history-backtest skills/bytnode-realtime-stream skills/bytnode-sdk skills/bytnode-market-brief
One skill: $skill-installer install https://github.com/bytnode/bytnode-skills/tree/main/skills/bytnode-api.
Codex picks up new skills automatically; type /skills to check, restart Codex if one is missing.
Cursor, Gemini CLI, GitHub Copilot, OpenCode, Windsurf, Cline, Goose, Kiro, Roo Code and 70+ others:
npx skills add bytnode/bytnode-skills # detects your agents and asks where
npx skills add bytnode/bytnode-skills -a cursor -a gemini-cli -g # or name them
npx skills add bytnode/bytnode-skills --list # see the skills without installing
npx skills add bytnode/bytnode-skills --skill bytnode-api # only one skill
npx skills update -g # update later
Without Node.js, copy the folders yourself into the skills folder your agent reads (.agents/skills/ in a project is read by Codex, Cursor, Gemini CLI, Copilot, OpenCode and most others; Claude Code reads .claude/skills/):
git clone --depth 1 https://github.com/bytnode/bytnode-skills
mkdir -p ~/.agents/skills && cp -r bytnode-skills/skills/* ~/.agents/skills/
git clone --depth 1 https://github.com/bytnode/bytnode-skills
New-Item -ItemType Directory -Force "$HOME\.agents\skills" | Out-Null
Copy-Item -Recurse -Force bytnode-skills\skills\* "$HOME\.agents\skills\"
BytNode-AI app: copy the folders into ~/.bytnode-ai/skills/ (same commands, other folder).
Claude (claude.ai, desktop app): zip one skill folder per upload, then Settings → Capabilities → Skills → Upload skill (code execution must be on; the menu can sit under Customize depending on your plan). Start with bytnode-mcp and bytnode-market-analysis.
cd bytnode-skills/skills && zip -r bytnode-mcp.zip bytnode-mcp # macOS, Linux
cd bytnode-skills\skills; Compress-Archive bytnode-mcp bytnode-mcp.zip # Windows
Any other chatbot (no skill upload): paste the content of the SKILL.md you need into the custom instructions of a project or custom assistant, and attach its references/ files as knowledge files. For live data, also add the BytNode MCP server as a connector: https://api.bytnode.com/mcp (sign-in with OAuth on bytnode.com, no key to paste).
- REST, SDK, WebSocket: a key in the environment,
export BYTNODE_API_KEY=cb_live_…(PowerShell:$env:BYTNODE_API_KEY="cb_live_…"), free at bytnode.com/sign-up. - MCP connectors (claude.ai, ChatGPT, Claude Code): add
https://api.bytnode.com/mcp; they sign in with OAuth, no key. See thebytnode-mcpskill.
Everything that can drift — routes, parameters, units, error codes, snapshot fields, indicators, MCP tools — lives in references/*.generated.md, generated from the public contract (https://api.bytnode.com/openapi.json) and the MCP server card. CONTRACT.json records the contract version they were generated from. The skills never hard-code a pair count or a price: they tell the agent to ask the API (/v1/symbols, /v1/limits).
python tools/generate_references.py # regenerate from the live contract
python tools/generate_references.py --check # CI: fail if a generated file is stale
evals/ holds the test tasks used to check each skill (run with and without the skill) and real captured responses in evals/fixtures/.
MIT for the skills. The data you fetch with them is governed by your BytNode subscription.
Seven skills, one for each job.
Install them all: an AI agent only opens a skill when the task needs it.
REST APIFoundation
Calling the API or writing code against it: discovery, units, bucket timing, pagination, plan limits and error recovery.
The six other skills build on it.MCP server
Answering market questions through the eleven MCP tools: which tool for which question, plan limits, summaries and cut responses.
Market analysis
Reading funding, open interest, basis, CVD, liquidations, options, sentiment and macro without misreading a unit or a window.
History and backtests
Downloading history for a backtest or a dataset: sized to the plan, every page, final rows only, no lookahead.
Real-time stream
Building on the WebSocket: browser tokens, live candles from trades, lost messages and reconnection.
Python and TypeScript SDKs
Writing code with the official SDKs: install, history to pandas, errors and built-in retries, streaming.
Market brief
Writing a daily or morning market report: what to fetch, what to check, and a fixed, dated format.
- bytnode/bytnode-skillsAll seven skills, the README with every install method, and the generator that keeps them in step with the API.View on GitHub
Install in one line,wherever your AI agent runs.
The same files work in every AI agent. Pick yours.
In Claude Code, add the marketplace and install the plugin (recommended):
Update later:
Or from a terminal, for every project (Node.js 18+):
Then give your AI agent the data.
For the REST API, the SDKs and the WebSocket, put a key in BYTNODE_API_KEY: the free plan needs no card. Chat assistants connect the MCP server instead and sign in with OAuth.
Routes, units, error codes and MCP tools are generated from the public API contract, never copied by hand, and every skill was tested against an AI agent working without it.