Token导航 LogoToken导航

Agent Skill · 研究检索

agent-workflow-builder(Agent 工作流程构建器)

agent-workflow-builder 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

agent-workflow-builder 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为只读;许可证信息还不明确,第三方扫描有提醒项,按安装量在研究检索类的 73,675 个 Skill 里排第 24,381。

总安装 4,037周安装 175GitHub Stars 3下载 1,446核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:agent-workflow-builder(Agent 工作流程构建器)
来源仓库:https://github.com/jmsktm/claude-settings
仓库路径:skills/agent-workflow-builder
安装命令:
npx skills add https://github.com/jmsktm/claude-settings --skill 'Agent Workflow Builder'
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/jmsktm/claude-settings --skill 'Agent Workflow Builder'

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

agent-workflow-builder 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中快速定位候选结果。适用于需要根据关键词或任务场景进行信息整理的场景,如研究、开发或协作流程梳理。

通过 npx skills add 命令从 GitHub 仓库安装,需指定技能名称和仓库地址。安装前建议确认权限范围和维护状态,避免触发不必要的联网或文件操作。可结合原始 README 进一步核验具体用法和功能边界。

来源仓库内路径:skills/agent-workflow-builder

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/jmsktm/claude-settings --skill 'Agent Workflow…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它标注为只读,先用只读任务试一次,确认行为符合预期再扩大使用范围。

常见问题

6 条

agent-workflow-builder 怎么安装?

在终端执行 npx skills add https://github.com/jmsktm/claude-settings --skill 'Agent Workflow Builder'。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

agent-workflow-builder 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

agent-workflow-builder 需要什么权限?

权限级别是只读。该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

agent-workflow-builder 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

agent-workflow-builder 用的人多吗?

公开数据是累计安装 4,037 次,近一周安装 175 次,下载 1,446 次,GitHub 3 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

agent-workflow-builder 安全吗?

第三方扫描有提醒项,说明存在需要人工确认的行为。安装前请打开源码看清它读了什么、联网到哪里。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 标注为只读权限,试用阶段不容易误改本地文件。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方扫描存在提醒项或未通过项,需要人工逐条确认。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。
  • 只想先试试效果、不希望它改动本地文件的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
agent-workflow-builder

Agent 工作流程构建器 · 本页

4,0373只读未明确有提醒

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

Agent Workflow Builder

The Agent Workflow Builder skill guides you through designing and implementing multi-agent AI systems that can plan, reason, use tools, and collaborate to accomplish complex tasks. Modern AI applications increasingly rely on agentic architectures where LLMs act as reasoning engines that orchestrate actions rather than just generate text.

This skill covers agent design patterns, tool integration, state management, error handling, and human-in-the-loop workflows. It helps you build robust agent systems that can handle real-world complexity while maintaining safety and controllability.

Whether you are building autonomous assistants, workflow automation, or complex reasoning systems, this skill ensures your agent architecture is well-designed and production-ready.

Core Workflows

Workflow 1: Design Agent Architecture

  1. Define the agent's scope:

- What tasks should it handle autonomously? - What requires human approval? - What is explicitly out of scope?

  1. Choose architecture pattern: Pattern Description Use When Single Agent One LLM with tools Simple tasks, clear scope Router Agent Classifies and delegates Multiple distinct domains Sequential Chain Agents in order Pipeline processing Hierarchical Manager + worker agents Complex, decomposable tasks Collaborative Peer agents discussing Requires diverse expertise
  2. Design tool set:

- What capabilities does the agent need? - How are tools defined and documented? - What are the safety boundaries?

  1. Plan state management:

- Conversation history - Task state and progress - External system state

  1. Document architecture decisions

Workflow 2: Implement Agent Loop

  1. Build core agent loop: class Agent: def __init__(self, llm, tools, system_prompt): self.llm = llm self.tools = {t.name: t for t in tools} self.system_prompt = system_prompt async def run(self, user_input, max_steps=10): messages = [{"role": "system", "content": self.system_prompt}, {"role": "user", "content": user_input}] for step in range(max_steps): response = await self.llm.chat(messages, tools=self.tools) if response.tool_calls: # Execute tools for call in response.tool_calls: result = await self.execute_tool(call) messages.append({"role": "tool", "content": result}) else: # Final response return response.content raise MaxStepsExceeded() async def execute_tool(self, call): tool = self.tools[call.name] return await tool.execute(call.arguments)
  2. Implement tools with clear interfaces
  3. Add error handling and retries
  4. Include logging and observability
  5. Test with diverse scenarios

Workflow 3: Build Multi-Agent System

  1. Define agent roles: agents = {"planner": Agent(llm=gpt4, tools=[search, create_task], system_prompt="You decompose complex tasks into steps..."), "researcher": Agent(llm=claude, tools=[web_search, read_document], system_prompt="You gather and synthesize information..."), "executor": Agent(llm=gpt4, tools=[code_interpreter, file_system], system_prompt="You execute tasks and produce outputs..."), "reviewer": Agent(llm=claude, tools=[validate, provide_feedback], system_prompt="You review work for quality and correctness...")}
  2. Implement orchestration:

- How do agents communicate? - Who decides what runs when? - How is work passed between agents?

  1. Manage shared state:

- Task board or work queue - Shared memory or context - Artifact storage

  1. Handle failures gracefully
  2. Add human checkpoints where needed

Quick Reference

ActionCommand/Trigger
Design agent"Design an agent for [task]"
Add tools"What tools for [agent type]"
Build multi-agent"Build multi-agent system for [goal]"
Handle errors"Agent error handling patterns"
Add human-in-loop"Add human approval to agent workflow"
Debug agent"Debug agent workflow"

Best Practices

  • Start Simple: Single agent with tools before multi-agent

- Prove value with minimal complexity - Add agents only when necessary - Each agent should have clear, distinct responsibility

  • Design Tools Carefully: Tools are the agent's hands

- Clear, descriptive names and documentation - Well-defined input/output schemas - Proper error handling and messages - Idempotent operations where possible

  • Limit Agent Autonomy: Constrain the blast radius

- Define what agents cannot do - Require approval for high-impact actions - Implement spending/rate limits - Log all actions for audit

  • Manage State Explicitly: Don't rely on LLM memory alone

- Persist conversation and task state - Summarize long contexts to fit windows - Track what has been tried/completed

  • Fail Gracefully: Agents will encounter errors

- Clear error messages for the agent to reason about - Retry logic with backoff - Fallback strategies - Human escalation paths

  • Observe Everything: Debugging agents is hard

- Log all LLM calls and tool invocations - Track reasoning chains and decisions - Measure success rates by task type

Advanced Techniques

ReAct Pattern (Reasoning + Acting)

Structure agent thinking explicitly:

REACT_PROMPT = """
You are an agent that solves tasks step by step.

For each step:
1. Thought: Analyze the current situation and decide what to do
2. Action: Choose a tool and provide arguments
3. Observation: Review the tool result

Continue until you can provide a final answer.

Available tools: {tool_descriptions}

Current task: {task}

Begin:
"""

Planning Agent with Task Decomposition

Break complex tasks into manageable steps:

class PlanningAgent:
    async def solve(self, task):
        # Step 1: Create plan
        plan = await self.create_plan(task)

        # Step 2: Execute each step
        results = []
        for step in plan.steps:
            result = await self.execute_step(step, context=results)
            results.append(result)

            # Replan if needed
            if result.status == "blocked":
                plan = await self.replan(task, results)

        # Step 3: Synthesize final output
        return await self.synthesize(task, results)

Reflection and Self-Correction

Let agents review and improve their work:

async def solve_with_reflection(self, task, max_attempts=3):
    for attempt in range(max_attempts):
        # Generate solution
        solution = await self.generate_solution(task)

        # Self-critique
        critique = await self.critique_solution(task, solution)

        if critique.is_acceptable:
            return solution

        # Improve based on critique
        task = f"{task}\n\nPrevious attempt issues: {critique.issues}"

    return solution  # Return best effort

Human-in-the-Loop Checkpoints

Integrate human approval into workflows:

class HumanApprovalTool:
    async def execute(self, action_description, risk_level):
        if risk_level == "low":
            return {"approved": True, "auto": True}

        # Send to approval queue
        approval_request = await self.create_request(action_description)

        # Wait for human response (with timeout)
        response = await self.wait_for_approval(
            approval_request.id,
            timeout_minutes=30
        )

        return {
            "approved": response.approved,
            "feedback": response.feedback,
            "auto": False
        }

Memory Management

Handle long conversations and context:

class AgentMemory:
    def __init__(self, max_tokens=8000):
        self.max_tokens = max_tokens
        self.messages = []
        self.summaries = []

    def add(self, message):
        self.messages.append(message)

        if self.token_count() > self.max_tokens:
            self.compress()

    def compress(self):
        # Summarize older messages
        old_messages = self.messages[:-5]  # Keep recent
        summary = summarize(old_messages)

        self.summaries.append(summary)
        self.messages = self.messages[-5:]

    def get_context(self):
        return {
            "summaries": self.summaries,
            "recent_messages": self.messages
        }

Common Pitfalls to Avoid

  • Building multi-agent systems when a single agent suffices
  • Giving agents too much autonomy without safety bounds
  • Not handling tool failures and edge cases
  • Forgetting that LLMs can hallucinate tool calls
  • Infinite loops when agents get stuck
  • Not logging enough to debug agent behavior
  • Assuming agents will follow instructions perfectly
  • Ignoring cost (token usage) in agent loops

平台分布

Codex

35.01%
按下载量换算506

Claude

29.63%
按下载量换算428

Cursor

22.63%
按下载量换算327

Gemini CLI

9.22%
按下载量换算133

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

可疑

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在提醒或未通过项,安装前请自行复核。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills