Agent skill

Automation Workflows

by CraftOS-dev in CraftOS-dev/CraftBot

Design and implement automation workflows to save time and scale operations as a solopreneur.

MITAuto-check passedProductivity & Automation

Install Automation Workflows

skills CLI
$ npx skills add CraftOS-dev/CraftBot --skill automation-workflows -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install CraftOS-dev/CraftBot automation-workflows --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/CraftOS-dev/CraftBot.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/automation-workflows .claude/skills/automation-workflows && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
automation-workflows
GitHub stars
392
Used in
1 other repo
Token cost
~2.6k tokens
SKILL.md length
948 words
Files
3
Skills in repo
89
Repo updated
First seen
Licence
MIT

At a glance

Design and implement automation workflows to save time and scale operations as a solopreneur.

  • Works in 7 steps: Identify What to Automate → Choose Your Automation Tool → Design Your Workflow → …
  • Identifying repetitive tasks to automate
  • SKILL.md covers Overview, Step 1: Identify What to…, Step 2: Choose Your Automation… and Step 3: Design Your Workflow, plus 5 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Automation Workflows is an agent skill from CraftOS-dev/CraftBot. Design and implement automation workflows to save time and scale operations as a solopreneur. Use when identifying repetitive tasks to automate, building workflows across tools, setting up triggers and actions, or optimizing existing automations. Covers automation opportunity identification, workflow design, tool selection (Zapier, Make, n8n), testing, and maintenance. Trigger on "automate", "automation", "workflow automation", "save time", "reduce manual work", "automate my business", "no-code automation".

Its SKILL.md is about 2.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files (for example `.clawhub/origin.json` and `_meta.json`).

It sits in Productivity & Automation, covering Workflow automation. It works with Zapier and n8n. The repository describes itself as: One agent. Every kind of work. The licence is MIT.

When your agent uses it

  • Identifying repetitive tasks to automate
  • Building workflows across tools
  • Setting up triggers and actions
  • Optimizing existing automations

Example prompts

  • “automate”
  • “automation”
  • “workflow automation”
  • “/automation-workflows”

Workflow steps

7 steps, taken from the step headings in SKILL.md.

  1. Identify What to Automate
  2. Choose Your Automation Tool
  3. Design Your Workflow
  4. Build and Test Your Workflow
  5. Monitor and Maintain Automations
  6. Advanced Automation Ideas
  7. Calculate Automation ROI

What it can do on your machine

Read from SKILL.md and the folder at commit b50970c. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Automation Workflows loads about 2.6k tokens when it runs. Until then it costs about 133 tokens; SKILL.md has 948 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~133
When it runs · the whole SKILL.md, loaded when a task matches
~2.6k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from CraftOS-dev/CraftBot at commit b50970c, republished under its MIT licence (© CraftOS-dev). 948 words, ~2,579 tokens.

Download SKILL.mdSave it as .claude/skills/automation-workflows/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
automation-workflows
description
Design and implement automation workflows to save time and scale operations as a solopreneur. Use when identifying repetitive tasks to automate, building workflows across tools, setting up triggers and actions, or optimizing existing automations. Covers automation opportunity identification, workflow design, tool selection (Zapier, Make, n8n), testing, and maintenance. Trigger on "automate", "automation", "workflow automation", "save time", "reduce manual work", "automate my business", "no-code automation".

Automation Workflows

Overview

As a solopreneur, your time is your most valuable asset. Automation lets you scale without hiring. The goal is simple: automate anything you do more than twice a week that doesn't require creative thinking. This playbook shows you how to identify automation opportunities, design workflows, and implement them without writing code.


Step 1: Identify What to Automate

Not every task should be automated. Start by finding the highest-value opportunities.

Automation audit (spend 1 hour on this):

  1. Track every task you do for a week (use a notebook or simple spreadsheet)

  2. For each task, note:

    • How long it takes
    • How often you do it (daily, weekly, monthly)
    • Whether it's repetitive or requires judgment
  3. Calculate time cost per task:

    Time Cost = (Minutes per task × Frequency per month) / 60

    Example: 15 min task done 20x/month = 5 hours/month

  4. Sort by time cost (highest to lowest)

Good candidates for automation:

  • Repetitive (same steps every time)
  • Rule-based (no complex judgment calls)
  • High-frequency (daily or weekly)
  • Time-consuming (takes 10+ minutes)

Examples:

  • ✅ Sending weekly reports to clients (same format, same schedule)
  • ✅ Creating invoices after payment
  • ✅ Adding new leads to CRM from form submissions
  • ✅ Posting social media content on a schedule
  • ❌ Conducting customer discovery interviews (requires nuance)
  • ❌ Writing custom proposals for clients (requires creativity)

Low-hanging fruit checklist (start here):

  • Email notifications for form submissions
  • Auto-save form responses to spreadsheet
  • Schedule social posts in advance
  • Auto-create invoices from payment confirmations
  • Sync data between tools (CRM ↔ email tool ↔ spreadsheet)

Step 2: Choose Your Automation Tool

Three main options for no-code automation. Pick based on complexity and budget.

Tool comparison:

ToolBest ForPricingLearning CurvePower Level
ZapierSimple, 2-3 step workflows$20-50/monthEasyLow-Medium
Make (Integromat)Visual, multi-step workflows$9-30/monthMediumMedium-High
n8nComplex, developer-friendly, self-hostedFree (self-hosted) or $20/monthMedium-HardHigh

Selection guide:

  • Budget < $20/month → Try Zapier free tier or n8n self-hosted
  • Need visual workflow builder → Make
  • Simple 2-step workflows → Zapier
  • Complex workflows with branching logic → Make or n8n
  • Want full control and customization → n8n

Recommendation for solopreneurs: Start with Zapier (easiest to learn). Graduate to Make or n8n when you hit Zapier's limits.


Step 3: Design Your Workflow

Before building, map out the workflow on paper or a whiteboard.

Workflow design template:

TRIGGER: What event starts the workflow?
  Example: "New row added to Google Sheet"

CONDITIONS (optional): Should this workflow run every time, or only when certain conditions are met?
  Example: "Only if Status column = 'Approved'"

ACTIONS: What should happen as a result?
  Step 1: [action]
  Step 2: [action]
  Step 3: [action]

ERROR HANDLING: What happens if something fails?
  Example: "Send me a Slack message if action fails"

Example workflow (lead capture → CRM → email):

TRIGGER: New form submission on website

CONDITIONS: Email field is not empty

ACTIONS:
  Step 1: Add lead to CRM (e.g., Airtable or HubSpot)
  Step 2: Send welcome email via email tool (e.g., ConvertKit)
  Step 3: Create task in project management tool (e.g., Notion) to follow up in 3 days
  Step 4: Send me a Slack notification: "New lead: [Name]"

ERROR HANDLING: If Step 1 fails, send email alert to me

Design principles:

  • Keep it simple — start with 2-3 steps, add complexity later
  • Test each step individually before chaining them together
  • Add delays between actions if needed (some APIs are slow)
  • Always include error notifications so you know when things break

Step 4: Build and Test Your Workflow

Now implement it in your chosen tool.

Build workflow (Zapier example):

  1. Choose trigger app (e.g., Google Forms, Typeform, website form)
  2. Connect your account (authenticate via OAuth)
  3. Test trigger (submit a test form to make sure data comes through)
  4. Add action (e.g., "Add row to Google Sheets")
  5. Map fields (match form fields to spreadsheet columns)
  6. Test action (run test to verify row is added correctly)
  7. Repeat for additional actions
  8. Turn on workflow (Zapier calls this "turn on Zap")

Testing checklist:

  • Submit test data through the trigger
  • Verify each action executes correctly
  • Check that data maps to the right fields
  • Test with edge cases (empty fields, special characters, long text)
  • Test error handling (intentionally cause a failure to see if alerts work)

Common issues and fixes:

IssueCauseFix
Workflow doesn't triggerTrigger conditions too narrowCheck filter settings, broaden criteria
Action failsAPI rate limit or permissionsAdd delay between actions, re-authenticate
Data missing or incorrectField mapping wrongDouble-check which fields are mapped
Workflow runs multiple timesDuplicate triggersDe-duplicate based on unique ID

Rule: Test with real data before relying on an automation. Don't discover bugs when a real customer is involved.


Show full SKILL.md (332 more words)Show less

Step 5: Monitor and Maintain Automations

Automations aren't set-it-and-forget-it. They break. Tools change. APIs update. You need a maintenance plan.

Weekly check (5 min):

  • Scan workflow logs for errors (most tools show a log of runs + failures)
  • Address any failures immediately

Monthly audit (15 min):

  • Review all active workflows
  • Check: Is this still being used? Is it still saving time?
  • Disable or delete unused workflows (they clutter your dashboard and can cause confusion)
  • Update any workflows that depend on tools you've switched away from

Where to store workflow documentation:

  • Create a simple doc (Notion, Google Doc) for each workflow
  • Include: What it does, when it runs, what apps it connects, how to troubleshoot
  • If you have 10+ workflows, this doc will save you hours when something breaks

Error handling setup:

  • Route all error notifications to one place (Slack channel, email inbox, or task manager)
  • Set up: "If any workflow fails, send a message to [your error channel]"
  • Review errors weekly and fix root causes

Step 6: Advanced Automation Ideas

Once you've automated the basics, consider these higher-leverage workflows:

Client onboarding automation
TRIGGER: New client signs contract (via DocuSign, HelloSign)
ACTIONS:
  1. Create project in project management tool
  2. Add client to CRM with "Active" status
  3. Send onboarding email sequence
  4. Create invoice in accounting software
  5. Schedule kickoff call on calendar
  6. Add client to Slack workspace (if applicable)
Content distribution automation
TRIGGER: New blog post published on website (via RSS or webhook)
ACTIONS:
  1. Post link to LinkedIn with auto-generated caption
  2. Post link to Twitter as a thread
  3. Add post to email newsletter draft (in email tool)
  4. Add to content calendar (Notion or Airtable)
  5. Send notification to team (Slack) that post is live
Customer health monitoring
TRIGGER: Every Monday at 9am (scheduled trigger)
ACTIONS:
  1. Pull usage data for all customers from database (via API)
  2. Flag customers with <50% of average usage
  3. Add flagged customers to "At Risk" segment in CRM
  4. Send re-engagement email campaign to at-risk customers
  5. Create task for me to personally reach out to top 10 at-risk customers
Invoice and payment tracking
TRIGGER: Payment received (Stripe webhook)
ACTIONS:
  1. Mark invoice as paid in accounting software
  2. Send receipt email to customer
  3. Update CRM: customer status = "Paid"
  4. Add revenue to monthly dashboard (Google Sheets or Airtable)
  5. Send me a Slack notification: "Payment received: $X from [Customer]"

Step 7: Calculate Automation ROI

Not every automation is worth the time investment. Calculate ROI to prioritize.

ROI formula:

Time Saved per Month (hours) = (Minutes per task / 60) × Frequency per month
Cost = (Setup time in hours × $50/hour) + Tool cost per month
Payback Period (months) = Setup cost / Monthly time saved value

If payback period < 3 months → Worth it
If payback period > 6 months → Probably not worth it (unless it unlocks other value)

Example:

Task: Manually copying form submissions to CRM (15 min, 20x/month = 5 hours/month saved)
Setup time: 1 hour
Tool cost: $20/month (Zapier)
Payback: ($50 setup cost) / ($250/month value saved) = 0.2 months → Absolutely worth it

Rule: Focus on automations with payback < 3 months. Those are your highest-leverage investments.


Automation Mistakes to Avoid

  • Automating before optimizing. Don't automate a bad process. Fix the process first, then automate it.
  • Over-automating. Not everything needs to be automated. If a task is rare or requires judgment, do it manually.
  • No error handling. If an automation breaks and you don't know, it causes silent failures. Always set up error alerts.
  • Not testing thoroughly. A broken automation is worse than no automation — it creates incorrect data or missed tasks.
  • Building too complex too fast. Start with simple 2-3 step workflows. Add complexity only when the simple version works perfectly.
  • Not documenting workflows. Future you will forget how this works. Write it down.

© CraftOS-dev, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files in skills/automation-workflows of CraftOS-dev/CraftBot.

  • SKILL.md
  • .clawhub/origin.json
  • _meta.json

Open the folder on GitHubat commit b50970c

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in CraftOS-dev/CraftBot, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Automation Workflows next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Automation Workflows compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Automation Workflows this skillCraftOS-dev/CraftBot3921 repos~2.6kAutomated safety check: PassMIT
Automation InstructionsdeusXmachina-dev/memorylane121—~1.1kAutomated safety check: PassGPL-3.0
GTM Engineeringtech-leads-club/agent-skills7k—~4.8kAutomated safety check: PassCustom licence
Automation Flowsericrisco/rsc-harness167—~2.9kAutomated safety check: PassMIT
Lindy Migration Deep Divejeremylongshore/tons-of-skills-marketplace2.8k—~2kAutomated safety check: PassMIT
Automation Strategyericrisco/rsc-harness167—~3.3kAutomated safety check: PassMIT

Similar skills

  • Automation Instructions

    deusXmachina-dev/memorylane

    Write step-by-step automation instructions for a workflow, tailored to your tool (Claude, n8n or Zapier).

    121 GitHub stars~1.1k tokensUpdated yesterday
    Productivity & AutomationAuto-check passed
  • GTM Engineering

    tech-leads-club/agent-skills

    Designs go-to-market automation and AI agent workflows for revenue teams, built on the idea that architecture and context matter more than any single tool.

    7k GitHub stars~4.8k tokensUpdated 18 days ago
    Productivity & AutomationAuto-check passed
  • Automation Flows

    ericrisco/rsc-harness

    A skill your agent uses when building or fixing a no-code automation on n8n, Make, or Zapier — trigger to multi-app steps with data mapping, dedup, retries and an error path — or picking the…

    167 GitHub stars~2.9k tokensUpdated today
    Productivity & AutomationAuto-check passed
  • Lindy Migration Deep Dive

    jeremylongshore/tons-of-skills-marketplace

    Advanced migration strategies for moving to Lindy AI from other platforms.

    2.8k GitHub stars~2k tokensUpdated today
    Productivity & AutomationAuto-check passed
  • Automation Strategy

    ericrisco/rsc-harness

    A skill your agent uses when deciding whether a process is worth automating, sizing ROI and build-vs-buy, choosing an automation platform, or diagnosing why a fleet of automations keeps breaking —…

    167 GitHub stars~3.3k tokensUpdated today
    Productivity & AutomationAuto-check passed
  • N8n

    ericrisco/rsc-harness

    A skill your agent uses when operating a live n8n instance programmatically — its REST API ({host}/api/v1, X-N8N-API-KEY) or the n8n-mcp server — to create, validate, test, activate, update, delete…

    167 GitHub stars~2.6k tokensUpdated today
    Productivity & AutomationAuto-check: notes

More from CraftOS-dev/CraftBot

All 89 skills in this repo
  • Self Improvement

    CraftOS-dev/CraftBot

    Captures learnings, errors, and corrections to enable continuous improvement.

    392 GitHub starsUsed in 5 repos~4.9k tokens
    Auto-check passed
  • Bbc News

    CraftOS-dev/CraftBot

    Fetch and display BBC News stories from various sections and regions via RSS feeds.

    392 GitHub starsUsed in 2 repos~555 tokens
    Auto-check passed
  • Outlook

    CraftOS-dev/CraftBot

    Read, search, and manage Outlook emails and calendar via Microsoft Graph API.

    392 GitHub starsUsed in 2 repos~1.8k tokens
    Auto-check passed
  • Nano Banana Pro

    CraftOS-dev/CraftBot

    Generate/edit images with Nano Banana Pro (Gemini 3 Pro Image).

    392 GitHub starsUsed in 6 repos~1.4k tokens
    Auto-check passed
  • Airweave

    CraftOS-dev/CraftBot

    Context retrieval layer for AI agents across users' applications.

    392 GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed
  • Telegram Bot Manager

    CraftOS-dev/CraftBot

    Manage and configure Telegram bots for OpenClaw. An agent skill from CraftOS-dev/CraftBot.

    392 GitHub stars~836 tokensUpdated yesterday
    Auto-check passed

Works with

Questions about Automation Workflows

What does Automation Workflows do?

Design and implement automation workflows to save time and scale operations as a solopreneur. Automation Workflows is an agent skill from CraftOS-dev/CraftBot. Design and implement automation workflows to save time and scale operations as a solopreneur.

When should I use Automation Workflows?

Automation Workflows fits situations like: identifying repetitive tasks to automate; building workflows across tools; setting up triggers and actions; optimizing existing automations.

How do I install Automation Workflows in Claude Code?

Run `npx skills add CraftOS-dev/CraftBot --skill automation-workflows -a claude-code`. Or copy the skill folder (skills/automation-workflows in CraftOS-dev/CraftBot) into .claude/skills/automation-workflows in your project. Claude Code loads it when a task matches its description.

How do I install Automation Workflows in Codex?

Run `npx skills add CraftOS-dev/CraftBot --skill automation-workflows -a codex`. Or copy the skill folder (skills/automation-workflows in CraftOS-dev/CraftBot) into .agents/skills/automation-workflows in your project. Codex loads it when a task matches its description.

Can I use Automation Workflows in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add CraftOS-dev/CraftBot --skill automation-workflows -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/automation-workflows, .gemini/skills/automation-workflows, .github/skills/automation-workflows and .opencode/skills/automation-workflows in your project.

What does Automation Workflows need to run?

SKILL.md names no scripts, command-line tools or credentials: Automation Workflows is instructions for the agent only.

Does Automation Workflows access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Automation Workflows safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Automation Workflows use?

Automation Workflows is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Automation Workflows use?

About 2.6k tokens (SKILL.md is roughly 10k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Automation Workflows?

Skills that share tags, products or a category with Automation Workflows: Automation Instructions (deusXmachina-dev/memorylane, 121 stars), GTM Engineering (tech-leads-club/agent-skills, 7k stars), Automation Flows (ericrisco/rsc-harness, 167 stars) and Lindy Migration Deep Dive (jeremylongshore/tons-of-skills-marketplace, 2.8k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Automation Workflows?

CraftOS-dev (a GitHub user) maintains it in CraftOS-dev/CraftBot, which has 392 GitHub stars. The repository holds 89 skills in this directory. The repository was last updated on October 7, 2026.

Source: CraftOS-dev/CraftBot on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.