一键导入
ralphx-agent-workflow-orchestrator
Author safe RalphX Agent Workflow scripts that orchestrate durable delegated agents through the high-level workflow API.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Author safe RalphX Agent Workflow scripts that orchestrate durable delegated agents through the high-level workflow API.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Git commit conventions and workflow
Guide for breaking features into atomic, implementable tasks
TDD workflow and testing patterns
Guide for analyzing git diff and refining QA test plans
Guide for generating QA test steps with agent-browser commands
Narrow RalphX Agent Workspace bridge playbook for workflow events delivered into an existing Agent Workspace conversation.
| name | ralphx-agent-workflow-orchestrator |
| description | Author safe RalphX Agent Workflow scripts that orchestrate durable delegated agents through the high-level workflow API. |
| trigger | RalphX Agent Workflow authoring |
| disable-model-invocation | true |
| user-invocable | false |
Use this skill only in a conversation whose selected capability is Workflow.
Generate a deterministic JavaScript program for the bundled RalphX workflow runner. The program may use only the provided globals: args, meta, phase, log, agent, parallel, pipeline, and checkpoint helpers. It has no filesystem, shell, network, environment, process, import, or module access.
phase(name) before each phase.agent() call a stable logicalKey. A key must identify the same prompt and output schema across retries.args.result.content. Missing, null, extra (when disallowed), or type-invalid required results fail the workflow.maxConcurrency and maxInvocations metadata. Prefer the smallest useful fanout.parallel([{ prompt, logicalKey, agentName, schema, title }, ...]) only for independent agent work; this descriptor form is the backend-enforced concurrent fanout path. Use pipeline() when later work depends on earlier output.Call create_agent_workflow_script with the script, metadata, permission summary, and estimated fanout. This stores the script for user review; it never approves or starts it. Do not claim that a workflow is running until start_agent_workflow_run succeeds after the user-approved hash is present.
Use the run inspection and pause/resume/cancel tools for lifecycle management. Never expose or invent runner attempts, leases, transport frames, delegated job IDs, or recovery bookkeeping.