agentsclimarketplace

Workflow automator

Skill OneWave-AI/claude-skills/workflow-automator

172 production-ready Claude Code skills for sales, marketing, design, engineering, and AI agent architecture. Built and maintained by OneWave AI.

Install
npx -y skills add OneWave-AI/claude-skills --skill workflow-automator

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

What its author says it does

Copied from the file, not written here

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.

SKILL.md

3.8 KB, 748 tokens by cl100k_base, as published. Nobody here has run it

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

What ships with it: 6 files

18.9 KB alongside SKILL.md

references/

Gives 0 of the 12 instructions most automation workflows skills give in 748 tokens

Counted across 745 of the 1,008 authors here whose files we hold, read 2026-08-07

  • Write conventional commit messagesin 36 of 745, across 35 files
  • Delete branches after mergein 30 of 745, across 21 files
  • Make atomic commitsin 25 of 745, across 15 files
  • Write minimal code to pass testsin 22 of 745, across 10 files
  • Re-snapshot after navigation or DOM changesin 21 of 745, across 13 files
  • Use try-catch for error handlingin 20 of 745, across 8 files
  • Run tests before committingin 20 of 745, across 12 files
  • Write tests before implementationin 20 of 745, across 8 files
  • Configure branch protection rulesin 19 of 745, across 5 files
  • Explain the why in commit messagesin 19 of 745, across 9 files
  • Refactor code while tests remain greenin 19 of 745, across 6 files
  • Interact with elements using refsin 19 of 745, across 11 files

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 327,069. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.