Workflow Automation

Identify and automate repetitive tasks that eat your time. Designs no-code automation workflows that run reliably in the background, freeing you for higher-value work.

Usage

Describe your repetitive tasks, tools you use, and pain points. The skill produces:

• Automation Audit: Which of your tasks are automatable and the ROI of automating each
• Workflow Designs: Step-by-step automation blueprints with triggers, actions, and conditions
• Tool Recommendations: Best automation platform for your specific needs
• Integration Map: How your tools connect and where data flows
• Error Handling: What happens when automations fail and how to handle edge cases
• Monitoring Plan: How to verify automations are running correctly
• Build vs Buy: When to automate yourself vs when to use existing solutions

Examples

1. Sales Process: "Automate our sales workflow: new lead from website form → CRM entry → Slack notification → welcome email sequence → task creation for SDR follow-up."

1. Content Publishing: "Automate content distribution: blog post published → share to Twitter, LinkedIn, and newsletter → add to content library spreadsheet → notify team in Slack."

1. Client Onboarding: "Automate new client onboarding: signed contract → create project folder → send welcome email with questionnaire → schedule kickoff → add to billing system."

1. Personal Productivity: "Automate my personal workflows: save interesting articles to reading list, log completed tasks to weekly review sheet, backup important files."

Guidelines

• Automate the boring parts first — start with tasks you do 3+ times per week that follow a consistent pattern
• Calculate ROI before building: (Time saved per occurrence x frequency) vs (time to build + maintain)
• Start simple — a 3-step automation that works is better than a 20-step one that breaks
• Always include error notifications so you know when an automation fails
• Test automations with real data before going live — edge cases break automations
• Document your automations — if you get hit by a bus, someone needs to understand them
• Review automations quarterly — the tools and processes they connect will change over time