工作流
多智能体研究流程
自动完成需要多数据源和综合分析的复杂主题深度研究。
工作流
多智能体研究流程
协调多个智能体分别执行网络搜索、文档分析、数据提取和综合总结，最终生成结构化研究报告。
适合场景
自动完成需要多数据源和综合分析的复杂主题深度研究。
页面类型
工作流
属性
深度研究 / 报告生成 / 团队协作
如何使用
把这个工作流作为起点，再根据自己的流程调整工具、提示词和复核步骤。
概览
多智能体研究流程 面向标准化周期性研究简报和市场扫描的团队。它关注的是协调多个智能体分别执行网络搜索、文档分析、数据提取和综合总结，最终生成结构化研究报告，页面目标不是罗列工具，而是把 Multi-Agent Research 工作流 变成可执行、可复查、可更新的工作流。
适合使用它的场景：自动完成需要多数据源和综合分析的复杂主题深度研究。稳定做法是先准备研究频率、主题范围、来源列表、证据表和报告模板，产出把来源转成已审核简报的可复用研究流程，并在扩大自动化范围前暴露来源规则不清，导致周期报告变成过期摘要。
为了避免低质程序化内容，这一页需要围绕“深度研究”给出具体步骤、证据、边界和人工审核点，让读者能直接判断是否适合自己的项目。
使用场景
- 用 多智能体研究流程 在团队定型工具栈前原型验证深度研究相关方案。
- 把 多智能体研究流程 做成内部检查清单，写清输入、权限、责任人、交付物和成功指标。
- 当客户、同事或 Agent 需要复现同一流程时，把它作为交接文档使用。
- 对比相邻工具或教程时，不只看功能宣传，而是比较简报产出耗时、来源复用率、遗漏更新率和审核修正数。
- 当模型、API、页面结构或业务流程变化后，重新刷新这一页，避免内容变成过期模板。
实施步骤
- 制定计划. 先把 多智能体研究流程 的任务边界写窄：谁触发、解决什么问题、允许使用哪些研究频率，以及遇到来源规则不清，导致周期报告变成过期摘要时必须停止。交给上线并监控前，补上一句可验收标准。
- 上线并监控. 写清运行频率和新鲜度规则。如果来源变化快于流程更新，先暂停自动化。
- 处理 Parallel research. 步骤要小到可以重跑。如果把来源转成已审核简报的可复用研究流程无法复现，先拆分任务再继续。
- 综合判断. 附上一个正例、一个反例，以及它们和 多智能体研究流程 的判断关系。
- 生成最小改动. 前几次生产运行保留人工兜底，避免来源规则不清，导致周期报告变成过期摘要静默影响用户。
配置步骤
- 先给 多智能体研究流程 画数据边界：哪些研究频率可以进入流程，哪些必须排除，最终结果存放在哪里。
- 为 深度研究 任务建立最小权限集，并写清哪个服务账号、MCP 服务或 Agent 可以执行哪类动作。
- 生成前先定义输出契约：必填字段、拒收格式、审核备注，以及把来源转成已审核简报的可复用研究流程交接到哪里。
- 建立失败记录，保存提取笔记、触发条件，以及出现来源规则不清时做出的处理决定。
- 真实运行后复盘简报产出耗时，只修改导致问题的提示词、路由、工具范围或来源清单。
快速判断
| 主要读者 | 标准化周期性研究简报和市场扫描的团队 |
|---|---|
| 输入材料 | 研究频率、主题范围、来源列表、证据表和报告模板 |
| 交付结果 | 把来源转成已审核简报的可复用研究流程 |
| 需要保留的证据 | 来源队列、提取笔记、综合判断、审核意见和最终简报 |
| 主要风险 | 来源规则不清，导致周期报告变成过期摘要 |
| 衡量指标 | 简报产出耗时、来源复用率、遗漏更新率和审核修正数 |
常见问题
多智能体研究流程 和普通 AI 工具清单有什么不同？
多智能体研究流程 围绕研究频率、主题范围、来源列表、证据表和报告模板、把来源转成已审核简报的可复用研究流程和来源队列、提取笔记、综合判断、审核意见和最终简报组织，读者能复现流程，而不是只看到功能摘要。
什么时候适合使用 多智能体研究流程？
当场景是“自动完成需要多数据源和综合分析的复杂主题深度研究”时最适合。前提是任务边界清楚，并且团队需要一种可重复运行、审核和改进的方法。
多智能体研究流程 上线前要检查什么？
检查权限范围、样例任务或测试、日志、失败兜底，以及来源规则不清，导致周期报告变成过期摘要是否被人工确认步骤拦住。
多智能体研究流程 应该怎么衡量效果？
持续记录简报产出耗时、来源复用率、遗漏更新率和审核修正数，用多次运行的数据判断价值，不要只根据一次成功演示做结论。
相关资源
123 results
0 saved
7 categories
123 resources
Updated index
Workflow Directory
Browse curated agents, MCP servers, templates, and workflow examples for real AI automation projects.
AI agent stack research
Find the right AI agents, MCP servers, and workflow templates
Agent Stack Library is a practical directory for people who are building real AI automation systems, not just collecting tool names. The site brings together AI agent frameworks, MCP servers, workflow templates, coding agents, browser automation tools, research workflows, and SaaS operations playbooks so you can compare an entire agent stack before committing to a toolchain.
A useful AI agent stack usually needs more than one model or one chat interface. Teams need a clear workflow, safe tool permissions, repeatable prompts, review checkpoints, and a way to measure whether the output is good enough for production. That is why the directory focuses on use cases such as AI coding agents, MCP server selection, SEO content workflows, browser QA, research assistants, internal tools, and multi-agent orchestration.
If you are evaluating MCP servers for AI agents, start with the task. A coding agent often needs GitHub access, a narrow filesystem scope, a test runner, and browser or DevTools verification. A research agent may need web search, document parsing, citation capture, memory, and a review step. A business operations agent may need CRM, email, calendar, spreadsheet, and audit logs. The best stack is the smallest one that completes the job safely.
AI agent workflow templates
Workflow templates help turn one-off prompts into repeatable systems. Each template should define the trigger, input context, agent role, connected tools, output format, human review step, and success metric. Browse the AI Agent Workflow Templates guide for SEO, coding, research, browser automation, and SaaS operations examples.
Office AI agent workflows
Office automation pages focus on concrete business tasks like Gmail email triage, daily email and calendar briefings, meeting notes to action items, meeting follow-up emails, and spreadsheet cleanup workflows.
MCP servers for AI agents
MCP servers connect agents to browsers, repositories, files, databases, memory, and business apps. Good MCP choices reduce custom integration work, but they also require clear permission boundaries. The Best MCP Servers for AI Agents guide explains how to pick a safe and useful tool stack.
AI coding agent workflow
Coding agents work best when they follow a normal engineering path: issue intake, repo context, plan, patch, tests, UI verification, pull request, and human review. The AI Coding Agent Workflow page gives a practical checklist for scoped code changes.
How to choose an agent stack
Start by deciding what the agent is allowed to do. Read-only workflows are easier to launch because the agent can gather context, summarize findings, and draft recommendations without touching production systems. Write-capable workflows need stricter guardrails: scoped credentials, test environments, logging, rollback procedures, and a human approval point before external actions.
Next, compare tools by workflow fit rather than popularity. An open-source agent framework may be perfect for a developer team that wants full control, while a managed automation platform may be better for operations teams that need quick integrations. A browser automation stack is useful for UI checks and web research, but it should not replace structured APIs when reliable APIs exist.
Finally, measure quality. Track task completion rate, review time, correction rate, cost per run, latency, and whether the output can be reused without heavy manual cleanup. A strong AI agent workflow is not the one with the most tools; it is the one that produces reliable output, exposes failures clearly, and lets humans stay in control where the risk is high.
What each directory category is for
The Agents category covers frameworks, SDKs, and agent products that help teams plan, call tools, manage memory, hand off work, or coordinate multiple specialist agents. Use this category when you are comparing LangGraph-style orchestration, coding agents, research agents, customer support agents, or open-source agent frameworks for a production project.
The MCP Tools category is focused on servers and integrations that let an AI agent interact with the outside world. These pages are useful when you need repository context, browser inspection, file access, databases, calendars, CRMs, or other business systems. Each MCP server should be judged by permission scope, reliability, setup effort, documentation quality, and how clearly failed tool calls are reported.
The Workflows and Templates categories are for readers who already know the job they want to automate. Instead of starting with a tool, start with a repeatable process: SEO content briefing, GitHub issue triage, browser QA, competitive research, sales lead enrichment, or support ticket summarization. From there, pick the smallest agent stack that can collect the right context, run the task, produce a reviewable output, and leave a log for future improvement.