- AgentHub: 13 files updated with non-engineering examples (content drafts, research, strategy) — engineering stays primary, cross-domain secondary - AgentHub: 7 slash commands, 5 Python scripts, 3 references, 1 agent, dry_run.py validation (57 checks) - Marketplace: agenthub entry added with cross-domain keywords, engineering POWERFUL updated (25→30), product (12→13), counts synced across all configs - SEO: generate-docs.py now produces keyword-rich <title> tags and meta descriptions using SKILL.md frontmatter — "Claude Code Skills" in site_name propagates to all 276 HTML pages - SEO: per-domain title suffixes (Agent Skill for Codex & OpenClaw, etc.), slug-as-title cleanup, domain label stripping from titles - Broken links: 141→0 warnings — new rewrite_skill_internal_links() converts references/, scripts/, assets/ links to GitHub source URLs; skills/index.md phantom slugs fixed (6 marketing, 7 RA/QM) - Counts synced: 204 skills, 266 tools, 382 refs, 16 agents, 17 commands, 21 plugins — consistent across CLAUDE.md, README.md, docs/index.md, marketplace.json, getting-started.md, mkdocs.yml - Platform sync: Codex 163 skills, Gemini 246 items, OpenClaw compatible Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2.9 KiB
2.9 KiB
title, description
| title | description |
|---|---|
| Agent Workflow Designer — Agent Skill for Codex & OpenClaw | Agent Workflow Designer. Agent skill for Claude Code, Codex CLI, Gemini CLI, OpenClaw. |
Agent Workflow Designer
:material-rocket-launch: Engineering - POWERFUL
:material-identifier: `agent-workflow-designer`
:material-github: Source
Install:
claude /plugin install engineering-advanced-skills
Tier: POWERFUL
Category: Engineering
Domain: Multi-Agent Systems / AI Orchestration
Overview
Design production-grade multi-agent workflows with clear pattern choice, handoff contracts, failure handling, and cost/context controls.
Core Capabilities
- Workflow pattern selection for multi-step agent systems
- Skeleton config generation for fast workflow bootstrapping
- Context and cost discipline across long-running flows
- Error recovery and retry strategy scaffolding
- Documentation pointers for operational pattern tradeoffs
When to Use
- A single prompt is insufficient for task complexity
- You need specialist agents with explicit boundaries
- You want deterministic workflow structure before implementation
- You need validation loops for quality or safety gates
Quick Start
# Generate a sequential workflow skeleton
python3 scripts/workflow_scaffolder.py sequential --name content-pipeline
# Generate an orchestrator workflow and save it
python3 scripts/workflow_scaffolder.py orchestrator --name incident-triage --output workflows/incident-triage.json
Pattern Map
sequential: strict step-by-step dependency chainparallel: fan-out/fan-in for independent subtasksrouter: dispatch by intent/type with fallbackorchestrator: planner coordinates specialists with dependenciesevaluator: generator + quality gate loop
Detailed templates: references/workflow-patterns.md
Recommended Workflow
- Select pattern based on dependency shape and risk profile.
- Scaffold config via
scripts/workflow_scaffolder.py. - Define handoff contract fields for every edge.
- Add retry/timeouts and output validation gates.
- Dry-run with small context budgets before scaling.
Common Pitfalls
- Over-orchestrating tasks solvable by one well-structured prompt
- Missing timeout/retry policies for external-model calls
- Passing full upstream context instead of targeted artifacts
- Ignoring per-step cost accumulation
Best Practices
- Start with the smallest pattern that can satisfy requirements.
- Keep handoff payloads explicit and bounded.
- Validate intermediate outputs before fan-in synthesis.
- Enforce budget and timeout limits in every step.