workflow-automator — Claude Code skill: what it does, how to install
The workflow-automator skill turns a description of a manual business process into an automation plan. It produces a Markdown document with diagrams, tool suggestions, and implementation steps.
MIT 285 installs ★ 440 updated 2026-10-20
npx skills add OneWave-AI/claude-skills --skill workflow-automator -a claude-codeWhat workflow-automator does
The skill maps the existing process, including its actors, task handoffs, decisions, delays, and failure points. It then lays out an automated flow with triggers, conditions, actions, human checkpoints, and error handling. When the process description is brief, it asks its clarifying questions together in one message.
It writes workflow-automation.md in the current working directory. The document includes Mermaid diagrams of the current and proposed flows, a time-savings table, tool recommendations, and phased implementation steps. Tools considered include Zapier, Make, n8n, custom code, and Power Automate.
The report estimates time saved, error reduction, throughput, costs, and ROI period. Those estimates depend on details such as workflow volume and frequency, so include them when describing the process.
What it helps with
- map the steps and handoffs in a manual process
- spot bottlenecks and error-prone decisions
- design an automated flow with failure handling
- compare automation platforms for a workflow
- estimate time savings and implementation costs
Example prompts for the agent
- Map our invoice approval process, including handoffs and delays, then create
workflow-automation.md. - Design an automated flow for the weekly report, with decision points and error handling.
- Compare Zapier, Make, and n8n for this process and outline the implementation phases.
How to install workflow-automator
1Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill workflow-automator -a claude-code2Manually: put the files in place
~/.claude/skills/workflow-automator/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/workflow-automator/
1Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill workflow-automator -a codex2Manually: put the files in place
.agents/skills/workflow-automator/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill workflow-automator -a cursor2Manually: put the files in place
.cursor/skills/workflow-automator/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install OneWave-AI/claude-skills workflow-automator2Manually: put the files in place
.github/skills/workflow-automator/SKILL.md1Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill workflow-automator -a gemini-cli2Platform CLI
gemini skills install https://github.com/OneWave-AI/claude-skills --path workflow-automatorManually: put the files in place
.devin/skills/workflow-automator/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill workflow-automator -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about workflow-automator
How do I install workflow-automator in Claude Code?
Run npx skills add OneWave-AI/claude-skills --skill workflow-automator -a claude-code. The skill file is placed at ~/.claude/skills/workflow-automator/SKILL.md.
What does workflow-automator do?
It maps a manual business process and designs an automated alternative. The resulting workflow-automation.md contains flow diagrams, tool recommendations, and an impact estimate.
Which automation platforms does it evaluate?
It compares Zapier, Make, n8n, custom code, and Power Automate, then recommends a primary platform and, when appropriate, a hybrid setup.
Source text
SKILL.md · MIT
--- name: workflow-automator description: Takes a manual business workflow description and designs the automated version. Maps current steps, handoffs, decision points, and bottlenecks. Designs automated flow with triggers, conditions, actions, and error handling. Outputs workflow-automation.md with before/after Mermaid diagrams, tool recommendations, implementation steps, and time savings estimate. tools: Read, Write, Glob, Grep, Bash, WebSearch, WebFetch model: inherit --- # Workflow Automator Transform a manual business workflow into an optimized automated system: map how work gets done today, then design a complete automated replacement with triggers, conditions, actions, branching, and error handling. Deliver a comprehensive `workflow-automation.md`. ## Contents - `references/intake.md` -- What to gather and how to ask for missing detail - `references/analysis-framework.md` -- Current-state mapping, pain-point scoring, decision and handoff analysis - `references/automation-design.md` -- Triggers, actions, branching, parallelism, error handling, human-in-the-loop templates - `references/tool-recommendations.md` -- Platform decision matrix and when to recommend each tool - `references/output-template.md` -- Full `workflow-automation.md` structure to fill in - `references/diagram-and-estimation-standards.md` -- Mermaid conventions and time/ROI estimation rules ## Workflow 1. **Intake.** Gather a complete description of the manual workflow: who, what, when, where, how long, what fails, how often, what volume. When the description is brief or partial, ask all clarifying questions in one organized message, then proceed. See `references/intake.md`. 2. **Map the current state.** Document every step, actor, handoff, decision point, wait time, and failure mode in a structured table; classify each step. See `references/analysis-framework.md`. 3. **Identify pain points.** Score each step on automation potential, impact, and risk. Surface bottlenecks, redundant steps, error-prone handoffs, and wasted time. See `references/analysis-framework.md`. 4. **Design the automated flow.** Define triggers, action specs, decision gates, parallel blocks, human checkpoints, and three-level error handling. See `references/automation-design.md`. 5. **Recommend tools.** Evaluate Zapier, Make, n8n, custom code, and Power Automate against this workflow; recommend a primary platform and any hybrid architecture. See `references/tool-recommendations.md`. 6. **Estimate impact.** Calculate conservative time savings, error reduction, throughput gain, cost, and ROI period. See `references/diagram-and-estimation-standards.md`. 7. **Deliver.** Generate the full `workflow-automation.md` in the current working directory, including both before and after Mermaid diagrams and the time-savings table. See `references/output-template.md` and `references/diagram-and-estimation-standards.md`. ## Output Rules - Always generate the full document, not a summary or abbreviated version. Make it self-contained enough to implement from alone. - Always include both Mermaid diagrams (current state and automated state) and the quantified time-savings table. - Use no emojis anywhere in the output. ## Quality Checklist Before delivering, verify: - [ ] Every manual step is mapped - [ ] Every decision point has explicit logic - [ ] Every handoff is analyzed - [ ] The automated flow handles all identified failure modes - [ ] Error handling exists at step, flow, and system levels - [ ] Human-in-the-loop checkpoints exist for high-risk decisions - [ ] Tool recommendations are justified with specific criteria - [ ] Time savings estimates are conservative and show the math - [ ] Cost analysis includes all ongoing costs - [ ] Implementation is phased with quick wins first - [ ] Both Mermaid diagrams render correctly - [ ] The document is self-contained and actionable - [ ] No emojis are used anywhere in the output
© OneWave-AI · MIT · OneWave-AI/claude-skills