Token导航 LogoToken导航

Agent Skill · 前端设计

workflow-orchestrator(工作流程协调器)

workflow-orchestrator 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

workflow-orchestrator 是前端设计类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为需要联网;许可证信息还不明确,第三方扫描有提醒项,按安装量在前端设计类的 10,216 个 Skill 里排第 6,192。

总安装 541周安装 23GitHub Stars 1下载 190核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/wojons/skills --skill workflow-orchestrator

这个 Skill 是做什么的

前端设计类 Skill 关注页面结构、视觉规范和组件写法,输出通常是可运行的界面代码。

workflow-orchestrator 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息。适合在 Codex、Claude、Cursor、Gemini CLI 中围绕仓库状态进行整理。通过 npx skills add 命令从指定仓库安装,需结合原始 README 核验用法。

安装前建议确认权限范围、维护状态,以及是否会触发联网或命令执行。注意该技能当前无底部简介,功能依赖仓库内实现细节。

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

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/wojons/skills --skill workflow-orchestrator;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

    它需要需要联网,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

workflow-orchestrator 怎么安装?

在终端执行 npx skills add https://github.com/wojons/skills --skill workflow-orchestrator。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

workflow-orchestrator 支持哪些 AI 工具?

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

workflow-orchestrator 需要什么权限?

权限级别是需要联网。该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

workflow-orchestrator 是免费的吗?

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

workflow-orchestrator 用的人多吗?

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

workflow-orchestrator 安全吗?

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

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

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。

先想清楚的地方

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

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理前端设计类任务、又不想每次都手写提示词的人。

不太适合

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

前端设计类 Skill 对比

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

前端设计 · Codex、Claude

8,823,360126,072只读MIT通过
vercel-composition-patterns

Vercel 组合模式 · Codex、Claude

3,858,81625,893需要联网MIT通过
vercel-react-native-skills

Vercel React native skills 前端 · Codex、Claude

2,468,66425,878只读MIT通过
adapt

adapt 搜索 · Codex、Claude

2,027,04023,125操作浏览器未明确通过
bolder

bolder 分析 · Codex、Claude

2,004,28823,130只读未明确通过
workflow-orchestrator

工作流程协调器 · 本页

5411需要联网未明确有提醒

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

SKILL.md 原文

Workflow Orchestrator

Design, configure, and execute AI-driven development workflows (Ralph loops) that iterate until tasks complete successfully using configurable patterns, multi-agent coordination, and intelligent stop conditions.

When to use me

Use this skill when:

  • Building complex features requiring multiple AI agent passes
  • Implementing automated development workflows with verification steps
  • Coordinating parallel AI agents for different aspects of a task
  • Creating self-correcting loops that iterate until success criteria met
  • Designing workflow patterns for team consistency
  • Need to orchestrate multiple AI agents in sequence or parallel
  • Want to implement "Ralph loops" (AI workflows that feed failures back into input)

What I do

1. Workflow Pattern Selection

  • Analyze task requirements to recommend optimal workflow patterns
  • Match complexity levels with appropriate workflow types
  • Compare trade-offs between speed, cost, control, and quality
  • Select from proven patterns (simple, verified, planned, parallel, custom)

2. Configuration Generation

  • Generate YAML configurations for workflow execution
  • Define agent roles and responsibilities (builder, verifier, planner, merger)
  • Set success criteria and stop conditions for automated completion
  • Configure iteration limits and escape hatches for safety
  • Specify tool permissions and model selections per agent

3. Multi-Agent Coordination

  • Sequence agents for linear workflows (build → verify → plan)
  • Parallelize agents for concurrent execution
  • Merge results from multiple agent perspectives
  • Handle failures and retries with intelligent routing
  • Implement steering patterns (linear, conditional, parallel, unblocking)

4. Ralph Loop Implementation

  • Create feedback loops where failures inform subsequent attempts
  • Implement stop hooks to detect completion promises (<promise>...</promise>)
  • Build contextual pressure cookers that iterate toward success
  • Manage iteration limits to prevent infinite loops
  • Track progress and telemetry across workflow executions

5. Integration & Tooling

  • OpenCode server integration for HTTP-based workflows
  • SSE event streaming for real-time monitoring
  • TUI/UI dashboards for workflow visualization
  • Git hook integration for automated quality gates
  • Cost tracking and budgeting across agent executions

Workflow Patterns

Pattern 1: Builder Only (Simple)

Single Agent → Build → [Success?] → Done
                     ↓ No
                     Retry (max iterations)

Best for: Simple tasks, bug fixes, small features Agents: 1 (builder) Control: Low, Cost: Low, Speed: High

Pattern 2: Build + Verify

Builder → [Success?] → Verifier → [Pass?] → Done
           ↓ No                 ↓ No
           Retry                Feedback → Builder

Best for: Quality-critical work, production code Agents: 2 (builder, verifier) Control: Medium, Cost: Medium, Speed: Medium

Pattern 3: Build + Verify + Plan

Planner → Builder → Verifier → [Pass?] → Done
                            ↓ No
                            Feedback → Planner

Best for: Complex features, architectural changes Agents: 3+ (planner, builder, verifier) Control: High, Cost: High, Speed: Low

Pattern 4: Multi-Agent Pipeline

[Agent A] → [Merge]
[Agent B] → [Results] → Done
[Agent C] →

Best for: Multiple perspectives, comprehensive solutions Agents: 3+ parallel agents Control: High, Cost: High, Speed: Medium

Pattern 5: Custom Workflow

User-defined sequence of agents with custom routing logic.

Configuration Examples

Simple Builder Loop (builder-only.yaml):

workflow:
  version: "1.0"
  settings:
    max_iterations: 20
    stop_on_success: true

  loop:
    agent: builder
    task: "Build the requested feature"
    stop_condition: "<promise>BUILD_COMPLETE</promise>"
    tools:
      read: true
      write: true
      edit: true
      bash: true

Build + Verify Loop:

workflow:
  version: "1.0"

  agents:
    builder:
      role: "Build the feature"
      stop_condition: "<promise>BUILT</promise>"

    verifier:
      role: "Verify quality and correctness"
      stop_condition: "<promise>VERIFIED</promise>"

  sequence:
    - agent: builder
    - agent: verifier
      condition: "builder.stop_condition met"

  feedback:
    verifier_failed: "builder"

Multi-Agent Parallel Workflow:

workflow:
  version: "1.0"

  agents:
    frontend_specialist:
      role: "Implement UI components"

    backend_specialist:
      role: "Implement API and business logic"

    qa_specialist:
      role: "Test implementation"

  parallel:
    - frontend_specialist
    - backend_specialist

  sequence:
    - parallel: [frontend_specialist, backend_specialist]
    - agent: qa_specialist

  merger:
    agent: lead_developer
    task: "Merge parallel work into cohesive solution"

Examples

# Analyze project and suggest workflow pattern
npm run workflow:analyze -- --task "Add user authentication"

# Generate workflow configuration
npm run workflow:generate -- --pattern build-verify --output auth-workflow.yaml

# Execute workflow
npm run workflow:execute -- --config auth-workflow.yaml --max-iterations 20

# Monitor running workflow
npm run workflow:monitor -- --workflow-id auth-123

# List available patterns
npm run workflow:patterns -- --list

# Create custom workflow from template
npm run workflow:custom -- --agents "planner,builder,verifier" --sequence "sequential"

Output format

Workflow Analysis Report:

Workflow Orchestrator Analysis
──────────────────────────────
Task: Add user authentication to React/Node.js app
Date: 2026-02-26

Recommended Pattern: Build + Verify + Plan
Rationale: Authentication requires security review, testing, and planning

Pattern Comparison:
┌─────────────────┬─────────┬─────────┬─────────┬──────────┐
│ Pattern         │ Control │ Cost   │ Speed   │ Quality  │
├─────────────────┼─────────┼─────────┼─────────┼──────────┤
│ Builder Only    │ Low     │ $      │ Fast    │ Medium   │
│ Build + Verify  │ Medium  │ $$     │ Medium  │ High     │
│ Build+Verify+Plan│ High    │ $$$    │ Slow    │ Highest  │
│ Multi-Agent     │ Highest │ $$$$   │ Medium  │ Highest  │
└─────────────────┴─────────┴─────────┴─────────┴──────────┘

Agents Required:
1. Planner (architect authentication flow)
2. Builder (implement components and API)
3. Verifier (security and testing specialist)

Estimated:
- Iterations: 3-5
- Cost: $15-25
- Time: 45-60 minutes
- Success Probability: 85%

Configuration Generated: auth-workflow.yaml

Workflow Configuration:

workflow:
  name: "user-authentication"
  version: "1.1"
  created: "2026-02-26T18:00:00Z"

  settings:
    max_iterations: 20
    stop_on_success: true
    escape_hatch: true
    cost_limit: 50.00
    time_limit_minutes: 120

  agents:
    planner:
      model: "anthropic/claude-sonnet-4-20250514"
      temperature: 0.3
      role: "Plan authentication architecture"
      tools: ["read", "write", "question"]
      stop_condition: "<promise>PLAN_COMPLETE</promise>"

    builder:
      model: "anthropic/claude-sonnet-4-20250514"
      temperature: 0.7
      role: "Implement authentication components"
      tools: ["read", "write", "edit", "bash", "webfetch"]
      stop_condition: "<promise>BUILD_COMPLETE</promise>"

    verifier:
      model: "anthropic/claude-sonnet-4-20250514"
      temperature: 0.2
      role: "Verify security and functionality"
      tools: ["read", "bash", "question"]
      stop_condition: "<promise>VERIFIED</promise>"

  sequence:
    - agent: planner
    - agent: builder
      condition: "planner.stop_condition met"
    - agent: verifier
      condition: "builder.stop_condition met"

  feedback:
    verifier_failed:
      target: planner
      message: "Verification failed, replan needed"

    builder_stuck:
      target: planner
      message: "Builder stuck, needs guidance"

  success_criteria:
    - "All tests pass"
    - "Security review passed"
    - "API endpoints documented"
    - "User stories implemented"

  telemetry:
    track_costs: true
    track_iterations: true
    track_duration: true
    dashboard_url: "http://localhost:3000/dashboard"

Workflow Execution Log:

Workflow Execution: user-authentication
─────────────────────────────────────
Status: Running
Start Time: 2026-02-26T18:00:00Z
Current Iteration: 3/20
Cost: $8.75
Duration: 25m 30s

Agent Timeline:
00:00:00 - Planner started
00:05:15 - Planner completed: <promise>PLAN_COMPLETE</promise>
00:05:30 - Builder started
00:15:45 - Builder: Created 12 files, 457 lines
00:20:30 - Builder completed: <promise>BUILD_COMPLETE</promise>
00:20:45 - Verifier started
00:25:30 - Verifier: Running security checks

Current Agent: Verifier
Progress: 75%
Estimated Completion: 00:35:00

Success Criteria Status:
✅ Tests passing: 42/42 tests
🔍 Security review: In progress
📚 Documentation: 80% complete
👤 User stories: 3/4 implemented

Next: Verifier completion → Workflow success

Notes

  • Ralph loops work best with clear success criteria - vague goals lead to infinite loops
  • Start simple - use Builder Only pattern for small tasks before scaling up
  • Monitor costs - parallel agents and multiple iterations increase expense
  • Implement escape hatches - always have manual stop conditions
  • Use stop promises (<promise>...</promise>) for reliable completion detection
  • Consider feedback mechanisms - failed verification should inform subsequent attempts
  • Balance control vs. autonomy - more agents = more control but higher cost/complexity
  • Test workflows with simple tasks before applying to critical work
  • Document patterns for team consistency and knowledge sharing
  • Review telemetry to optimize workflow configurations over time

平台分布

Codex

36.47%
按下载量换算69

Claude

30.78%
按下载量换算58

Cursor

18.62%
按下载量换算35

Gemini CLI

8.91%
按下载量换算17

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

可疑

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

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

继续浏览同类 Skills