Automation Instructions
deusXmachina-dev/memorylane
Write step-by-step automation instructions for a workflow, tailored to your tool (Claude, n8n or Zapier).
Design and implement automation workflows to save time and scale operations as a solopreneur.
$ npx skills add CraftOS-dev/CraftBot --skill automation-workflows -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install CraftOS-dev/CraftBot automation-workflows --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ 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-srcUse ~/.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/
Install the "automation-workflows" agent skill from https://github.com/CraftOS-dev/CraftBot/tree/main/skills/automation-workflows into .claude/skills/automation-workflows/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "automation-workflows", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/CraftOS-dev/CraftBot/tree/main/skills/automation-workflowsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add CraftOS-dev/CraftBot --skill automation-workflows -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install CraftOS-dev/CraftBot automation-workflows --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/CraftOS-dev/CraftBot.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/automation-workflows .agents/skills/automation-workflows && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "automation-workflows" agent skill from https://github.com/CraftOS-dev/CraftBot/tree/main/skills/automation-workflows into .agents/skills/automation-workflows/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "automation-workflows", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add CraftOS-dev/CraftBot --skill automation-workflows -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install CraftOS-dev/CraftBot automation-workflows --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/CraftOS-dev/CraftBot.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/automation-workflows .cursor/skills/automation-workflows && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "automation-workflows" agent skill from https://github.com/CraftOS-dev/CraftBot/tree/main/skills/automation-workflows into .cursor/skills/automation-workflows/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "automation-workflows", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/CraftOS-dev/CraftBot.git --path skills/automation-workflows--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add CraftOS-dev/CraftBot --skill automation-workflows -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install CraftOS-dev/CraftBot automation-workflows --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/CraftOS-dev/CraftBot.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/automation-workflows .gemini/skills/automation-workflows && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "automation-workflows" agent skill from https://github.com/CraftOS-dev/CraftBot/tree/main/skills/automation-workflows into .gemini/skills/automation-workflows/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "automation-workflows", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install CraftOS-dev/CraftBot automation-workflowsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add CraftOS-dev/CraftBot --skill automation-workflows -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/CraftOS-dev/CraftBot.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/automation-workflows .github/skills/automation-workflows && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "automation-workflows" agent skill from https://github.com/CraftOS-dev/CraftBot/tree/main/skills/automation-workflows into .github/skills/automation-workflows/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "automation-workflows", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add CraftOS-dev/CraftBot --skill automation-workflows -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install CraftOS-dev/CraftBot automation-workflows --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/CraftOS-dev/CraftBot.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/automation-workflows .opencode/skills/automation-workflows && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "automation-workflows" agent skill from https://github.com/CraftOS-dev/CraftBot/tree/main/skills/automation-workflows into .opencode/skills/automation-workflows/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "automation-workflows", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
automation-workflowsDesign 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. 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.
7 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit b50970c. It shows what the files ask for, not the result of running them.
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.
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.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
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.
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.
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.
The full file from CraftOS-dev/CraftBot at commit b50970c, republished under its MIT licence (© CraftOS-dev). 948 words, ~2,579 tokens.
.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.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.
Not every task should be automated. Start by finding the highest-value opportunities.
Automation audit (spend 1 hour on this):
Track every task you do for a week (use a notebook or simple spreadsheet)
For each task, note:
Calculate time cost per task:
Time Cost = (Minutes per task × Frequency per month) / 60Example: 15 min task done 20x/month = 5 hours/month
Sort by time cost (highest to lowest)
Good candidates for automation:
Examples:
Low-hanging fruit checklist (start here):
Three main options for no-code automation. Pick based on complexity and budget.
Tool comparison:
| Tool | Best For | Pricing | Learning Curve | Power Level |
|---|---|---|---|---|
| Zapier | Simple, 2-3 step workflows | $20-50/month | Easy | Low-Medium |
| Make (Integromat) | Visual, multi-step workflows | $9-30/month | Medium | Medium-High |
| n8n | Complex, developer-friendly, self-hosted | Free (self-hosted) or $20/month | Medium-Hard | High |
Selection guide:
Recommendation for solopreneurs: Start with Zapier (easiest to learn). Graduate to Make or n8n when you hit Zapier's limits.
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 meDesign principles:
Now implement it in your chosen tool.
Build workflow (Zapier example):
Testing checklist:
Common issues and fixes:
| Issue | Cause | Fix |
|---|---|---|
| Workflow doesn't trigger | Trigger conditions too narrow | Check filter settings, broaden criteria |
| Action fails | API rate limit or permissions | Add delay between actions, re-authenticate |
| Data missing or incorrect | Field mapping wrong | Double-check which fields are mapped |
| Workflow runs multiple times | Duplicate triggers | De-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.
Automations aren't set-it-and-forget-it. They break. Tools change. APIs update. You need a maintenance plan.
Weekly check (5 min):
Monthly audit (15 min):
Where to store workflow documentation:
Error handling setup:
Once you've automated the basics, consider these higher-leverage workflows:
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)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 liveTRIGGER: 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 customersTRIGGER: 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]"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 itRule: Focus on automations with payback < 3 months. Those are your highest-leverage investments.
© 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
SKILL.md and 2 other files in skills/automation-workflows of CraftOS-dev/CraftBot.
Open the folder on GitHubat commit b50970c
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.
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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Automation Workflows this skillCraftOS-dev/CraftBot | 392 | 1 repos | ~2.6k | Automated safety check: Pass | MIT | |
| Automation InstructionsdeusXmachina-dev/memorylane | 121 | — | ~1.1k | Automated safety check: Pass | GPL-3.0 | |
| GTM Engineeringtech-leads-club/agent-skills | 7k | — | ~4.8k | Automated safety check: Pass | Custom licence | |
| Automation Flowsericrisco/rsc-harness | 167 | — | ~2.9k | Automated safety check: Pass | MIT | |
| Lindy Migration Deep Divejeremylongshore/tons-of-skills-marketplace | 2.8k | — | ~2k | Automated safety check: Pass | MIT | |
| Automation Strategyericrisco/rsc-harness | 167 | — | ~3.3k | Automated safety check: Pass | MIT |
deusXmachina-dev/memorylane
Write step-by-step automation instructions for a workflow, tailored to your tool (Claude, n8n or Zapier).
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.
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…
jeremylongshore/tons-of-skills-marketplace
Advanced migration strategies for moving to Lindy AI from other platforms.
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 —…
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…
CraftOS-dev/CraftBot
Captures learnings, errors, and corrections to enable continuous improvement.
CraftOS-dev/CraftBot
Fetch and display BBC News stories from various sections and regions via RSS feeds.
CraftOS-dev/CraftBot
Read, search, and manage Outlook emails and calendar via Microsoft Graph API.
CraftOS-dev/CraftBot
Generate/edit images with Nano Banana Pro (Gemini 3 Pro Image).
CraftOS-dev/CraftBot
Context retrieval layer for AI agents across users' applications.
CraftOS-dev/CraftBot
Manage and configure Telegram bots for OpenClaw. An agent skill from CraftOS-dev/CraftBot.
Categories
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.
Automation Workflows fits situations like: identifying repetitive tasks to automate; building workflows across tools; setting up triggers and actions; optimizing existing automations.
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.
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.
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.
SKILL.md names no scripts, command-line tools or credentials: Automation Workflows is instructions for the agent only.
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.
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.
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.
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.
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.
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.