Mission Control Agent API
builderz-labs/mission-control
Teaches an agent to use the Mission Control dashboard API: register, send heartbeats, fetch assigned tasks, report progress and disconnect, with API key auth.
Talks to a running DeerFlow agent platform over its HTTP API to send research questions, stream replies, check health and manage models, skills, memory and uploads.
$ npx skills add bytedance/deer-flow --skill claude-to-deerflow -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install bytedance/deer-flow claude-to-deerflow --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/bytedance/deer-flow.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/public/claude-to-deerflow .claude/skills/claude-to-deerflow && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "claude-to-deerflow" agent skill from https://github.com/bytedance/deer-flow/tree/main/skills/public/claude-to-deerflow into .claude/skills/claude-to-deerflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "claude-to-deerflow", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/bytedance/deer-flow/tree/main/skills/public/claude-to-deerflowType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add bytedance/deer-flow --skill claude-to-deerflow -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install bytedance/deer-flow claude-to-deerflow --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/bytedance/deer-flow.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/public/claude-to-deerflow .agents/skills/claude-to-deerflow && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "claude-to-deerflow" agent skill from https://github.com/bytedance/deer-flow/tree/main/skills/public/claude-to-deerflow into .agents/skills/claude-to-deerflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "claude-to-deerflow", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add bytedance/deer-flow --skill claude-to-deerflow -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install bytedance/deer-flow claude-to-deerflow --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/bytedance/deer-flow.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/public/claude-to-deerflow .cursor/skills/claude-to-deerflow && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "claude-to-deerflow" agent skill from https://github.com/bytedance/deer-flow/tree/main/skills/public/claude-to-deerflow into .cursor/skills/claude-to-deerflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "claude-to-deerflow", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/bytedance/deer-flow.git --path skills/public/claude-to-deerflow--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add bytedance/deer-flow --skill claude-to-deerflow -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install bytedance/deer-flow claude-to-deerflow --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/bytedance/deer-flow.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/public/claude-to-deerflow .gemini/skills/claude-to-deerflow && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "claude-to-deerflow" agent skill from https://github.com/bytedance/deer-flow/tree/main/skills/public/claude-to-deerflow into .gemini/skills/claude-to-deerflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "claude-to-deerflow", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install bytedance/deer-flow claude-to-deerflowInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add bytedance/deer-flow --skill claude-to-deerflow -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/bytedance/deer-flow.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/public/claude-to-deerflow .github/skills/claude-to-deerflow && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "claude-to-deerflow" agent skill from https://github.com/bytedance/deer-flow/tree/main/skills/public/claude-to-deerflow into .github/skills/claude-to-deerflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "claude-to-deerflow", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add bytedance/deer-flow --skill claude-to-deerflow -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install bytedance/deer-flow claude-to-deerflow --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/bytedance/deer-flow.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/public/claude-to-deerflow .opencode/skills/claude-to-deerflow && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "claude-to-deerflow" agent skill from https://github.com/bytedance/deer-flow/tree/main/skills/public/claude-to-deerflow into .opencode/skills/claude-to-deerflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "claude-to-deerflow", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
claude-to-deerflowTalks to a running DeerFlow agent platform over its HTTP API to send research questions, stream replies, check health and manage models, skills, memory and uploads.
DeerFlow is an agent platform built on LangGraph, and it exposes two API surfaces behind an Nginx reverse proxy: a Gateway API for REST endpoints such as models, skills, memory and uploads, and a LangGraph-compatible API for threads, runs and streaming. The agent reads the `DEERFLOW_URL` variable, which defaults to `http://localhost:2026`, along with the optional gateway and LangGraph overrides, before making any request.
The main operation creates a thread and then streams a run, reading the server-sent events as they arrive, starting with run metadata. A health check hits `/health` first, and helper scripts `scripts/chat.sh` and `scripts/status.sh` wrap chatting and status checks. The skill also covers listing models, skills and agents, managing memory and uploading files to threads, so a long research task can be handed to DeerFlow.
12 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 8a3350a. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Ships 2 files in scripts/ (Shell), which the agent can run.
Shell commands in SKILL.md call:
curlbashFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md. Its commands use curl, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
DeerFlow HTTP API Client loads about 1.7k tokens when it runs. Until then it costs about 130 tokens; SKILL.md has 505 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
The full file from bytedance/deer-flow at commit 8a3350a, republished under its MIT licence (© bytedance). 505 words, ~1,713 tokens.
.claude/skills/claude-to-deerflow/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.Communicate with a running DeerFlow instance via its HTTP API. DeerFlow is an AI agent platform built on LangGraph that orchestrates sub-agents for research, code execution, web browsing, and more.
DeerFlow exposes two API surfaces behind an Nginx reverse proxy:
| Service | Direct Port | Via Proxy | Purpose |
|---|---|---|---|
| Gateway API | 8001 | $DEERFLOW_GATEWAY_URL | REST endpoints and embedded agent runtime |
| LangGraph-compatible API | 8001 | $DEERFLOW_LANGGRAPH_URL | Agent threads, runs, streaming |
All URLs are configurable via environment variables. Read these env vars before making any request.
| Variable | Default | Description |
|---|---|---|
DEERFLOW_URL | http://localhost:2026 | Unified proxy base URL |
DEERFLOW_GATEWAY_URL | ${DEERFLOW_URL} | Gateway API base (models, skills, memory, uploads) |
DEERFLOW_LANGGRAPH_URL | ${DEERFLOW_URL}/api/langgraph | LangGraph API base (threads, runs) |
When making curl calls, always resolve the URL like this:
# Resolve base URLs from env (do this FIRST before any API call)
DEERFLOW_URL="${DEERFLOW_URL:-http://localhost:2026}"
DEERFLOW_GATEWAY_URL="${DEERFLOW_GATEWAY_URL:-$DEERFLOW_URL}"
DEERFLOW_LANGGRAPH_URL="${DEERFLOW_LANGGRAPH_URL:-$DEERFLOW_URL/api/langgraph}"Verify DeerFlow is running:
curl -s "$DEERFLOW_GATEWAY_URL/health"This is the primary operation. It creates a thread and streams the agent's response.
Step 1: Create a thread
curl -s -X POST "$DEERFLOW_LANGGRAPH_URL/threads" \
-H "Content-Type: application/json" \
-d '{}'Response: {"thread_id": "<uuid>", ...}
Step 2: Stream a run
curl -s -N -X POST "$DEERFLOW_LANGGRAPH_URL/threads/<thread_id>/runs/stream" \
-H "Content-Type: application/json" \
-d '{
"assistant_id": "lead_agent",
"input": {
"messages": [
{
"type": "human",
"content": [{"type": "text", "text": "YOUR MESSAGE HERE"}]
}
]
},
"stream_mode": ["values", "messages-tuple"],
"stream_subgraphs": true,
"config": {
"recursion_limit": 1000
},
"context": {
"thinking_enabled": true,
"is_plan_mode": true,
"subagent_enabled": true,
"thread_id": "<thread_id>"
}
}'The response is an SSE stream. Each event has the format:
event: <event_type>
data: <json_data>Key event types:
metadata — run metadata including run_idvalues — full state snapshot with messages arraymessages-tuple — incremental message updates (AI text chunks, tool calls, tool results)end — stream is completeContext modes (set via context):
thinking_enabled: false, is_plan_mode: false, subagent_enabled: falsethinking_enabled: true, is_plan_mode: false, subagent_enabled: falsethinking_enabled: true, is_plan_mode: true, subagent_enabled: falsethinking_enabled: true, is_plan_mode: true, subagent_enabled: trueTo send follow-up messages, reuse the same thread_id from step 2 and POST another run
with the new message.
curl -s "$DEERFLOW_GATEWAY_URL/api/models"Returns: {"models": [{"name": "...", "provider": "...", ...}, ...]}
curl -s "$DEERFLOW_GATEWAY_URL/api/skills"Returns: {"skills": [{"name": "...", "enabled": true, ...}, ...]}
curl -s -X PUT "$DEERFLOW_GATEWAY_URL/api/skills/<skill_name>" \
-H "Content-Type: application/json" \
-d '{"enabled": true}'curl -s "$DEERFLOW_GATEWAY_URL/api/agents"Returns: {"agents": [{"name": "...", ...}, ...]}
curl -s "$DEERFLOW_GATEWAY_URL/api/memory"Returns user context, facts, and conversation history summaries.
curl -s -X POST "$DEERFLOW_GATEWAY_URL/api/threads/<thread_id>/uploads" \
-F "files=@/path/to/file.pdf"Supports PDF, PPTX, XLSX, DOCX — automatically converts to Markdown.
curl -s "$DEERFLOW_GATEWAY_URL/api/threads/<thread_id>/uploads/list"curl -s "$DEERFLOW_LANGGRAPH_URL/threads/<thread_id>/history"curl -s -X POST "$DEERFLOW_LANGGRAPH_URL/threads/search" \
-H "Content-Type: application/json" \
-d '{"limit": 20, "sort_by": "updated_at", "sort_order": "desc"}'For sending messages and collecting the full response, use the helper script:
bash /path/to/skills/claude-to-deerflow/scripts/chat.sh "Your question here"See scripts/chat.sh for the implementation. The script:
The stream returns SSE events. To extract the final AI response from a values event:
event: values blockdata JSONmessages array contains all messages; the last one with type: "ai" is the responsecontent field of that message is the AI's text reply© bytedance, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 2 other files (scripts) in skills/public/claude-to-deerflow of bytedance/deer-flow.
Open the folder on GitHubat commit 8a3350a
We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in bytedance/deer-flow, which our catalogue first saw on October 7, 2026.
DeerFlow HTTP API Client next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| DeerFlow HTTP API Client this skillbytedance/deer-flow | 84k | 1 repos | ~1.7k | Automated safety check: Pass | MIT | |
| Mission Control Agent APIbuilderz-labs/mission-control | 6.3k | — | ~2.1k | Automated safety check: Pass | MIT | |
| Agents Buildaws/agent-toolkit-for-aws | 2.8k | — | ~2.3k | Automated safety check: Notes | Apache-2.0 | |
| AI Agent Developmentaiskillstore/marketplace | 433 | 3 repos | ~1k | Automated safety check: Pass | None | |
| Lindy Reference Architecturejeremylongshore/tons-of-skills-marketplace | 2.8k | — | ~3.2k | Automated safety check: Pass | MIT | |
| Claw Multi AgentLeoYeAI/openclaw-master-skills | 2.2k | — | ~5.5k | Automated safety check: Pass | MIT |
builderz-labs/mission-control
Teaches an agent to use the Mission Control dashboard API: register, send heartbeats, fetch assigned tasks, report progress and disconnect, with API key auth.
aws/agent-toolkit-for-aws
A skill your agent uses to extend an existing agent project with memory, app integration, VPC, multi-agent, migration, model, browser, code interpreter, payments, or resource removal.
aiskillstore/marketplace
AI agent development workflow for building autonomous agents, multi-agent systems, and agent orchestration with CrewAI, LangGraph, and custom agents.
jeremylongshore/tons-of-skills-marketplace
Reference architectures for Lindy AI agent integrations. An agent skill from jeremylongshore/tons-of-skills-marketplace.
LeoYeAI/openclaw-master-skills
Multi-agent parallel orchestration for OpenClaw. An agent skill from LeoYeAI/openclaw-master-skills.
CoWork-OS/CoWork-OS
Multi-agent system research agent for CoWork OS. An agent skill from CoWork-OS/CoWork-OS.
bytedance/deer-flow
Deploys a project to Vercel with one script and no login, then returns a live preview URL and a claim link for moving the deployment into your own Vercel account.
bytedance/deer-flow
Researches a GitHub repository over four rounds using the GitHub API and web search, then writes a structured markdown report with timeline, metrics and Mermaid diagrams.
bytedance/deer-flow
Picks a suitable chart type from 26 options for your data, maps the data to that chart's parameters and generates a chart image through a JavaScript script.
bytedance/deer-flow
Analyzes uploaded Excel and CSV files with SQL through DuckDB, producing schema inspections, statistical summaries and exports to CSV, JSON or Markdown.
bytedance/deer-flow
Turns an image request into a structured JSON prompt and runs a bundled Python script to generate the picture, optionally guided by reference images.
bytedance/deer-flow
Walks through an end-to-end smoke test of a DeerFlow deployment: pull the latest code, deploy with Docker or locally, verify services, run health checks and write a report.
Works with
Categories
Talks to a running DeerFlow agent platform over its HTTP API to send research questions, stream replies, check health and manage models, skills, memory and uploads. DeerFlow is an agent platform built on LangGraph, and it exposes two API surfaces behind an Nginx reverse proxy: a Gateway API for REST endpoints such as models, skills, memory and uploads, and a LangGraph-compatible API for threads, runs and streaming. The agent reads the `DEERFLOW_URL` variable, which defaults to `http://localhost:2026`, along with the optional gateway and LangGraph overrides, before making any request.
DeerFlow HTTP API Client fits situations like: delegating a long research task to a running DeerFlow instance; checking that a DeerFlow server is up before sending work; listing the models, skills or agents available in DeerFlow; uploading a file to a DeerFlow thread for analysis.
Run `npx skills add bytedance/deer-flow --skill claude-to-deerflow -a claude-code`. Or copy the skill folder (skills/public/claude-to-deerflow in bytedance/deer-flow) into .claude/skills/claude-to-deerflow in your project. Claude Code loads it when a task matches its description.
Run `npx skills add bytedance/deer-flow --skill claude-to-deerflow -a codex`. Or copy the skill folder (skills/public/claude-to-deerflow in bytedance/deer-flow) into .agents/skills/claude-to-deerflow in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add bytedance/deer-flow --skill claude-to-deerflow -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/claude-to-deerflow, .gemini/skills/claude-to-deerflow, .github/skills/claude-to-deerflow and .opencode/skills/claude-to-deerflow in your project.
Going by SKILL.md and its folder, DeerFlow HTTP API Client needs a shell for the scripts in its folder and the command-line tools its instructions call (curl and bash). Our summary lists: A running DeerFlow instance; `curl` to call its HTTP API.
SKILL.md contains no URLs. Its commands use curl, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
DeerFlow HTTP API Client is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 1.7k tokens (SKILL.md is roughly 6.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with DeerFlow HTTP API Client: Mission Control Agent API (builderz-labs/mission-control, 6.3k stars), Agents Build (aws/agent-toolkit-for-aws, 2.8k stars), AI Agent Development (aiskillstore/marketplace, 433 stars) and Lindy Reference Architecture (jeremylongshore/tons-of-skills-marketplace, 2.8k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
bytedance (a GitHub organization) maintains it in bytedance/deer-flow, which has 83,674 GitHub stars. The repository holds 23 skills in this directory. The repository was last updated on October 11, 2026.
Source: bytedance/deer-flow on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.