阅读学术论文,评估主要论点、证据、研究方法、创新性及其与相关研究的关系,具体指出优点与不足,并整理成包含改进建议的评审。
- 了解论文成果与局限
- 起草同行评审意见
- 检查实验设计与可复现性
通过HTTP API向运行中的DeerFlow发送调研和分析请求,获取回答、继续对话并上传资料。还可查看模型、技能、智能体列表及服务运行状态。
Interact with DeerFlow AI agent platform via its HTTP API. Use this skill when the user wants to send messages or questions to DeerFlow for research/analysis, start a DeerFlow conversation thread, check DeerFlow status or health, list available models/skills/agents in DeerFlow, manage DeerFlow memory, upload files to DeerFlow threads, or delegate complex research tasks to DeerFlow. Also use when the user mentions deerflow, deer flow, or wants to run a deep research task that DeerFlow can handle.
向DeerFlow发送调研或分析请求,并获取回答。通过HTTP API这一供外部操作服务的接口,可以开始或继续对话、获取历史记录,以及查看模型、技能和智能体列表。也支持检查运行状态、启用或停用技能,以及查看已保存的记忆。
适合将复杂调研交给DeerFlow,或提交资料后针对内容提问。将PDF、PPTX、XLSX或DOCX文件上传到对话后,文件会自动转换为Markdown。复用对话编号,即可接着之前的交流继续提问。
连接的DeerFlow实例必须处于运行状态。连接地址可以通过环境变量配置,默认值为http://localhost:2026。不同处理模式会控制是否制定计划,以及是否使用辅助智能体。
本介绍由 AI(OpenAI Codex)根据公开的 SKILL.md 撰写。准确的规格请查看下方原文。
AI 仅根据 SKILL.md 的内容,从 4 个方面进行了评估。星标数和热度不计入评估。
总分按每项 A=25 分、B=15 分、C=5 分相加。 由 AI(OpenAI Codex)于 2026年10月21日 评估。仅供参考,安装前请同时查看原文。
安装前可以查看交给 AI 代理的指令内容。
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还没有评价。欢迎分享你的使用感受。
无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。
还没有评论。来写第一条吧。
阅读学术论文,评估主要论点、证据、研究方法、创新性及其与相关研究的关系,具体指出优点与不足,并整理成包含改进建议的评审。
检测可能阻塞Python异步处理的输入输出调用,并推动修复和补充测试。验证问题重现时测试确实失败、恢复修复后通过,以监测问题再次出现。
通过对话梳理工作、偏好及希望交由AI判断的范围,创建或更新规定AI伙伴行为的SOUL.md,并明确说话方式和表达异议的规则。
根据数据特点,从26种图表和示意图中选择合适的形式并生成图片,可展示时间变化、比较、分布和关联,并返回图片链接及生成时使用的完整配置。
阅读实际源代码,按项目规模编写或完善包含安装步骤与用法示例的README、API文档、架构图、开发者指南及变更日志。
为市场、竞争对手、消费者或财务调研设计章节、所需数据和图表计划,再将已收集的信息整理为包含对比、来源及战略启示的报告,并明确标注缺失数据。