Agent
The Agency AI 专家团队
需要工程、创意、战略等不同领域 AI 专家的团队，而不是一个万金油式的编码助手
Agents
The Agency AI 专家团队
102k 星的 AI 专家团队，不是提示词库，是 32+ 个独立 AI 代理的完整人格与工作流定义。工程部覆盖前端、后端、DevOps、QA、安全审查；创意部负责文案、品牌语调、社媒策略；战略部做竞品分析、路线图规划和干系人沟通。兼容 Claude Code、Cursor、Gemini...
适合场景
需要工程、创意、战略等不同领域 AI 专家的团队，而不是一个万金油式的编码助手
页面类型
Agents
属性
多代理协作 / 32+专家
如何使用
把这个工作流作为起点，再根据自己的流程调整工具、提示词和复核步骤。
概览
The Agency AI 专家团队 面向审查 PR、diff 和 AI 生成代码的工程团队。它关注的是102k 星的 AI 专家团队，不是提示词库，是 32+ 个独立 AI 代理的完整人格与工作流定义。工程部覆盖前端、后端、DevOps、QA、安全审查；创意部负责文案、品牌语调、社媒策略；战略部做竞品分析、路线图规划和干系人沟通。兼容 Claude Code、Cursor、Gemini CLI、OpenCode、Aider、Windsurf、Copilot、Kimi Code 等主流工具，安装脚本自动检测并接入，页面目标不是罗列工具，而是把 The Agency — AI Agents Roster 变成可执行、可复查、可更新的工作流。
适合使用它的场景：需要工程、创意、战略等不同领域 AI 专家的团队，而不是一个万金油式的编码助手。稳定做法是先准备PR diff、变更文件、测试输出、代码归属规则和审查清单，产出按风险排序的审查意见、复现说明和建议测试，并在扩大自动化范围前暴露漏掉回归，或用模糊反馈阻塞无害改动。
为了避免低质程序化内容，这一页需要围绕“多代理协作”给出具体步骤、证据、边界和人工审核点，让读者能直接判断是否适合自己的项目。
使用场景
- 用 The Agency AI 专家团队 在团队定型工具栈前埋点记录多代理协作相关方案。
- 把 The Agency AI 专家团队 做成内部检查清单，写清输入、权限、责任人、交付物和成功指标。
- 当客户、同事或 Agent 需要复现同一流程时，把它作为交接文档使用。
- 对比相邻工具或教程时，不只看功能宣传，而是比较真实问题命中率、逃逸回归率、审查延迟和评论有用度。
- 当模型、API、页面结构或业务流程变化后，重新刷新这一页，避免内容变成过期模板。
实施步骤
- 处理 Install via script. 逐项列出连接、读写范围、样例参数和回滚办法。把代码行位置放在配置旁边，便于复查。
- 限制工具权限. 从最小可用权限开始。Agent 只接触产出复现说明必需的工具，需要扩大权限时再人工处理。
- 处理 Assign specialists by domain. 步骤要小到可以重跑。如果建议测试无法复现，先拆分任务再继续。
- 处理 Activate Agent. 附上一个正例、一个反例，以及它们和 The Agency AI 专家团队 的判断关系。
- 处理 Agent follows personality + 工作流 spec. 说明为什么选这种编排方式，也写出没有选的替代方案，尤其当真实问题命中率是主要判断依据时。
- 处理 Delivers with templates and metrics. 从一个明确输入和一个明确结果开始。以PR diff为来源，并留下代码行位置给下一步检查。
配置步骤
- 先给 The Agency AI 专家团队 画数据边界：哪些PR diff可以进入流程，哪些必须排除，最终结果存放在哪里。
- 为 多代理协作 任务建立最小权限集，并写清哪个服务账号、MCP 服务或 Agent 可以执行哪类动作。
- 生成前先定义输出契约：必填字段、拒收格式、审核备注，以及按风险排序的审查意见、复现说明和建议测试交接到哪里。
- 建立失败记录，保存失败场景、触发条件，以及出现用模糊反馈阻塞无害改动时做出的处理决定。
- 真实运行后复盘逃逸回归率，只修改导致问题的提示词、路由、工具范围或来源清单。
快速判断
| 主要读者 | 审查 PR、diff 和 AI 生成代码的工程团队 |
|---|---|
| 输入材料 | PR diff、变更文件、测试输出、代码归属规则和审查清单 |
| 交付结果 | 按风险排序的审查意见、复现说明和建议测试 |
| 需要保留的证据 | 代码行位置、失败场景、测试缺口、安全顾虑和审核决定 |
| 主要风险 | 漏掉回归，或用模糊反馈阻塞无害改动 |
| 衡量指标 | 真实问题命中率、逃逸回归率、审查延迟和评论有用度 |
常见问题
The Agency AI 专家团队 和普通 AI 工具清单有什么不同？
The Agency AI 专家团队 围绕PR diff、变更文件、测试输出、代码归属规则和审查清单、按风险排序的审查意见、复现说明和建议测试和代码行位置、失败场景、测试缺口、安全顾虑和审核决定组织，读者能复现流程，而不是只看到功能摘要。
什么时候适合使用 The Agency AI 专家团队？
当场景是“需要工程、创意、战略等不同领域 AI 专家的团队，而不是一个万金油式的编码助手”时最适合。前提是任务边界清楚，并且团队需要一种可重复运行、审核和改进的方法。
The Agency AI 专家团队 上线前要检查什么？
检查权限范围、样例任务或测试、日志、失败兜底，以及漏掉回归，或用模糊反馈阻塞无害改动是否被人工确认步骤拦住。
The Agency 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.