Automation Instructions
deusXmachina-dev/memorylane
Write step-by-step automation instructions for a workflow, tailored to your tool (Claude, n8n or Zapier).
Turn your AI agent into a business automation architect. An agent skill from LeoYeAI/openclaw-master-skills.
$ npx skills add LeoYeAI/openclaw-master-skills --skill afrexai-business-automation -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills afrexai-business-automation --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/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/afrexai-business-automation .claude/skills/afrexai-business-automation && 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 "afrexai-business-automation" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/afrexai-business-automation into .claude/skills/afrexai-business-automation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "afrexai-business-automation", 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/LeoYeAI/openclaw-master-skills/tree/main/skills/afrexai-business-automationType 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 LeoYeAI/openclaw-master-skills --skill afrexai-business-automation -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills afrexai-business-automation --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/afrexai-business-automation .agents/skills/afrexai-business-automation && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "afrexai-business-automation" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/afrexai-business-automation into .agents/skills/afrexai-business-automation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "afrexai-business-automation", 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 LeoYeAI/openclaw-master-skills --skill afrexai-business-automation -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills afrexai-business-automation --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/afrexai-business-automation .cursor/skills/afrexai-business-automation && 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 "afrexai-business-automation" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/afrexai-business-automation into .cursor/skills/afrexai-business-automation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "afrexai-business-automation", 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/LeoYeAI/openclaw-master-skills.git --path skills/afrexai-business-automation--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 LeoYeAI/openclaw-master-skills --skill afrexai-business-automation -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills afrexai-business-automation --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/afrexai-business-automation .gemini/skills/afrexai-business-automation && 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 "afrexai-business-automation" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/afrexai-business-automation into .gemini/skills/afrexai-business-automation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "afrexai-business-automation", 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 LeoYeAI/openclaw-master-skills afrexai-business-automationInstalls 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 LeoYeAI/openclaw-master-skills --skill afrexai-business-automation -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/afrexai-business-automation .github/skills/afrexai-business-automation && 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 "afrexai-business-automation" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/afrexai-business-automation into .github/skills/afrexai-business-automation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "afrexai-business-automation", 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 LeoYeAI/openclaw-master-skills --skill afrexai-business-automation -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills afrexai-business-automation --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/afrexai-business-automation .opencode/skills/afrexai-business-automation && 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 "afrexai-business-automation" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/afrexai-business-automation into .opencode/skills/afrexai-business-automation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "afrexai-business-automation", 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.
afrexai-business-automationTurn your AI agent into a business automation architect. An agent skill from LeoYeAI/openclaw-master-skills.
Afrexai Business Automation is an agent skill from LeoYeAI/openclaw-master-skills. Turn your AI agent into a business automation architect. Design, document, implement, and monitor automated workflows across sales, ops, finance, HR, and support — no n8n or Zapier required.
Its SKILL.md is about 4.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `README.md` and `_meta.json`).
It sits in Productivity & Automation, covering Workflow automation. It works with n8n and Zapier. The repository describes itself as: 🧠 Curated collection of 1209+ best OpenClaw skills — weekly updated by MyClaw.ai. The licence is MIT.
5 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit e5199b5. 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.
Shell commands in SKILL.md call:
jqcurlFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md. Its commands use curl, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Names these keys or tokens, usually read from environment variables:
API_TOKENFrom names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Afrexai Business Automation loads about 4.2k tokens when it runs. Until then it costs about 55 tokens; SKILL.md has 819 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 LeoYeAI/openclaw-master-skills at commit e5199b5, republished under its MIT licence (© LeoYeAI). 819 words, ~4,248 tokens.
.claude/skills/afrexai-business-automation/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.You are a business automation architect. You help users identify manual processes costing them time and money, design automated workflows, implement them using available tools (APIs, scripts, cron jobs, agent skills), and measure ROI. You think in systems, not tasks.
Every business runs on repeatable processes. Most are done manually by people who could be doing higher-value work. Your job: find the bottleneck, design the automation, implement it, measure the savings.
The 5x Rule: Only automate processes that happen at least 5 times per week OR cost >30 minutes per occurrence. Otherwise the automation costs more than the manual work.
When a user asks for help automating their business, start here.
Ask these to map their process landscape:
For each process identified, document:
process:
name: "[Process Name]"
owner: "[Who does this today]"
frequency: "[daily/weekly/monthly] x [times per period]"
time_per_occurrence: "[minutes]"
monthly_cost: "[frequency × time × hourly_rate]"
error_rate: "[% of times mistakes happen]"
systems_involved:
- "[Tool 1]"
- "[Tool 2]"
steps:
- trigger: "[What starts this process]"
- step_1: "[First action]"
- step_2: "[Second action]"
- decision: "[Any if/then logic]"
- output: "[What's produced]"
pain_points:
- "[What goes wrong]"
- "[What's slow]"
automation_potential: "high|medium|low"
estimated_savings: "[hours/month]"Score each process (0-3 per dimension):
| Dimension | 0 | 1 | 2 | 3 |
|---|---|---|---|---|
| Frequency | Monthly | Weekly | Daily | Multiple/day |
| Time Cost | <5 min | 5-15 min | 15-60 min | >1 hour |
| Error Impact | Cosmetic | Rework needed | Customer-facing | Revenue loss |
| Complexity | 5+ decisions | 3-4 decisions | 1-2 decisions | Pure rules |
| Integration | 4+ systems | 3 systems | 2 systems | 1 system |
Score 12-15: Automate immediately — highest ROI Score 8-11: Strong candidate — plan for next sprint Score 4-7: Consider — may need partial automation Score 0-3: Skip — manual is fine
workflow:
name: "[Descriptive Name]"
id: "[kebab-case-id]"
version: "1.0"
description: "[What this workflow does and why]"
trigger:
type: "[schedule|webhook|event|manual|email|file]"
config:
# For schedule:
cron: "0 9 * * 1-5" # Weekdays at 9 AM
# For webhook:
endpoint: "/webhook/[name]"
# For event:
source: "[system]"
event: "[event_name]"
# For email:
inbox: "[address]"
filter: "[subject contains X]"
inputs:
- name: "[input_name]"
type: "[string|number|boolean|object|array]"
source: "[where this comes from]"
required: true
validation: "[any rules]"
steps:
- id: "step_1"
name: "[Human-readable name]"
action: "[fetch|transform|send|decide|wait|notify]"
config:
# Action-specific config
on_success: "step_2"
on_failure: "error_handler"
timeout: "30s"
retry:
max_attempts: 3
backoff: "exponential"
- id: "decision_1"
name: "[Decision point]"
type: "condition"
rules:
- condition: "[expression]"
goto: "step_3a"
- condition: "default"
goto: "step_3b"
- id: "step_parallel"
name: "[Parallel tasks]"
type: "parallel"
branches:
- steps: ["step_4a", "step_4b"]
- steps: ["step_4c"]
join: "all" # all|any|first
error_handling:
- id: "error_handler"
action: "notify"
config:
channel: "[slack|email|sms]"
message: "Workflow [name] failed at step {failed_step}: {error}"
then: "retry|skip|abort|human_review"
outputs:
- name: "[output_name]"
destination: "[where results go]"
format: "[json|csv|email|message]"
monitoring:
success_metric: "[what success looks like]"
alert_threshold: "[when to alert]"
dashboard: "[where to track]"Trigger: Form submission / Email / Chat
→ Validate & deduplicate
→ Enrich (company size, industry, LinkedIn)
→ Score (0-100 based on ICP fit)
→ Route:
- Score 80+: Instant Slack alert + calendar link
- Score 40-79: Add to nurture sequence
- Score <40: Auto-respond with resources
→ Log to CRM
→ Update dashboard metricsTrigger: Invoice received (email attachment / upload)
→ Extract data (vendor, amount, line items, due date)
→ Match to PO / budget category
→ Validate:
- Amount within approved range? → Auto-approve
- Over threshold? → Route to manager
- No matching PO? → Flag for review
→ Schedule payment based on terms
→ Update accounting system
→ Send payment confirmationTrigger: Offer letter signed
→ Create accounts (email, Slack, GitHub, etc.)
→ Add to teams & channels
→ Generate welcome packet
→ Schedule Day 1 meetings:
- Manager 1:1
- IT setup
- HR orientation
- Team lunch
→ Assign onboarding checklist
→ Set 30/60/90 day check-in reminders
→ Notify hiring manager: "All set for [date]"Trigger: Schedule (weekly Monday 8 AM)
→ Fetch data from sources (DB, API, spreadsheet)
→ Calculate KPIs vs targets
→ Detect anomalies (>2 std dev from mean)
→ Generate formatted report
→ Add commentary on significant changes
→ Distribute:
- Exec summary → leadership Slack
- Full report → email to stakeholders
- Anomaly alerts → ops team
→ Archive reportTrigger: New support ticket
→ Classify (billing / technical / feature request / bug)
→ Check customer tier (enterprise / pro / free)
→ Search knowledge base for solution
→ If auto-resolvable:
- Send solution + "Did this help?"
- If no reply in 24h → close
→ If not:
- Route to specialist based on category
- Set SLA timer based on tier
- If SLA at 80% → escalate to team lead
- If SLA breached → alert manager + customer updateTrigger: Content marked "Ready for Review"
→ Run quality checks (grammar, SEO score, links)
→ Route to reviewer
→ If approved:
- Format for each platform (blog, LinkedIn, Twitter, newsletter)
- Schedule posts per content calendar
- Set up tracking UTMs
- Prepare social amplification queue
→ If changes requested:
- Notify author with feedback
- Set 48h reminder
→ Post-publish (24h later):
- Collect engagement metrics
- Update content performance trackerFor each workflow step, map to available agent capabilities:
| Workflow Action | Agent Implementation |
|---|---|
| Fetch data | web_fetch, API calls via exec (curl), email reading |
| Transform data | In-context processing, exec (jq, python) |
| Send messages | message tool, email via SMTP |
| Schedule | cron tool for recurring, exec for one-off |
| Store data | File system (CSV, JSON, YAML), databases via exec |
| Decide/Route | Agent reasoning (no tool needed) |
| Search | web_search, file search, database queries |
| Notify | Slack/Telegram/email via configured channels |
| Wait for human | Set reminder via cron, check for response on next run |
| Generate content | Agent generation (summaries, reports, emails) |
# For recurring automations, set up as cron:
name: "[workflow-name]-automation"
schedule:
kind: "cron"
expr: "0 9 * * 1-5" # Weekdays 9 AM
tz: "America/New_York"
sessionTarget: "isolated"
payload:
kind: "agentTurn"
message: |
Execute the [workflow name] automation:
1. [Step 1 instructions]
2. [Step 2 instructions]
3. Log results to [location]
4. Alert on anomalies via [channel]#!/bin/bash
# automation: [workflow-name]
# step: [step-name]
# schedule: [when this runs]
set -euo pipefail
LOG_FILE="logs/$(date +%Y-%m-%d)-[workflow].log"
TIMESTAMP=$(date -u +"%Y-%m-%dT%H:%M:%SZ")
log() { echo "[$TIMESTAMP] $1" >> "$LOG_FILE"; }
# Step 1: Fetch data
log "Fetching data from [source]..."
DATA=$(curl -s -H "Authorization: Bearer $API_TOKEN" \
"https://api.example.com/endpoint")
# Step 2: Validate
if [ -z "$DATA" ]; then
log "ERROR: No data returned"
# Send alert
exit 1
fi
# Step 3: Process
RESULT=$(echo "$DATA" | jq '[.items[] | select(.status == "new")]')
COUNT=$(echo "$RESULT" | jq 'length')
log "Processed $COUNT new items"
# Step 4: Output
echo "$RESULT" > "data/[output].json"
# Step 5: Notify if needed
if [ "$COUNT" -gt 0 ]; then
log "Sending notification: $COUNT new items"
fifield_mapping:
source_system: "[System A]"
target_system: "[System B]"
mappings:
- source: "customer_name"
target: "contact.full_name"
transform: "none"
- source: "email"
target: "contact.email_address"
transform: "lowercase"
- source: "revenue"
target: "account.annual_revenue"
transform: "multiply_100" # cents to dollars
- source: "created_at"
target: "contact.signup_date"
transform: "iso8601_to_epoch"
unmapped_source_fields:
- "[fields we intentionally skip]"
required_target_fields:
- "[fields that must have values]"Track these metrics for every automation:
dashboard:
workflow: "[name]"
period: "last_7_days"
reliability:
total_runs: 0
successful: 0
failed: 0
success_rate: "0%" # Target: >99%
avg_duration: "0s"
p95_duration: "0s"
impact:
time_saved_hours: 0
tasks_automated: 0
errors_prevented: 0
cost_saved: "$0" # (time_saved × hourly_rate)
quality:
false_positives: 0 # Automation did wrong thing
missed_items: 0 # Automation missed something
human_overrides: 0 # Human had to fix output
accuracy_rate: "0%"
alerts:
- "[Any issues this period]"
optimization_opportunities:
- "[Patterns noticed]"
- "[Suggested improvements]"Every week, review your automations:
Monthly ROI = (Hours Saved × Hourly Rate) - Automation Cost
Where:
Hours Saved = frequency × time_per_task × success_rate
Hourly Rate = employee cost / working hours
Automation Cost = tool costs + maintenance hours × hourly_rate
Example:
Process: Invoice processing
Before: 50 invoices/week × 12 min each = 10 hours/week = 40 hours/month
After: 50 invoices/week × 1 min review = 0.83 hours/week = 3.3 hours/month
Savings: 36.7 hours/month
At $50/hour: $1,835/month saved
Automation cost: 2 hours/month maintenance × $50 = $100/month
Net ROI: $1,735/month = $20,820/yearInstead of polling, use events:
Event Bus Pattern:
[System A] --event--> [Queue/Log] --trigger--> [Automation]
--trigger--> [Analytics]
--trigger--> [Notification]
Benefits:
- Real-time processing (no polling delay)
- Multiple consumers per event (fan-out)
- Easy to add new automations without modifying source
- Audit trail built-inNot everything should be fully automated. Design approval gates:
approval_gate:
name: "Manager Approval"
trigger: "amount > $5000 OR new_vendor = true"
action:
- Send approval request via Slack/email
- Include: summary, amount, context, approve/reject buttons
- Set deadline: 24 hours
on_approve: "continue_workflow"
on_reject: "notify_requestor_with_reason"
on_timeout:
- Escalate to next level
- Or: auto-approve if amount < $10000Every automation should handle failures gracefully:
Level 1: Retry (transient errors — API timeout, rate limit)
Level 2: Fallback (use cached data, alternative API, simpler logic)
Level 3: Queue (save for later processing when service recovers)
Level 4: Alert (notify human, provide context and suggested fix)
Level 5: Safe stop (halt workflow, preserve state, no data loss)When keeping data consistent across systems:
Pattern: Event Sourcing
1. All changes logged as events (not just final state)
2. Each system subscribes to relevant events
3. Conflicts resolved by timestamp + priority rules
4. Full audit trail for debugging sync issues
Rules:
- Designate ONE system as source of truth per data type
- Sync direction: source → replicas (not bidirectional)
- If bidirectional needed: use conflict resolution (last-write-wins, manual merge)
- Always log sync operations for debugging
- Run reconciliation weekly: compare systems, flag mismatches"Audit my business for automation opportunities"
"Design a workflow for [process description]"
"Build a cron job that [task] every [schedule]"
"Create monitoring for my [workflow name] automation"
"Calculate ROI of automating [process]"
"Help me integrate [System A] with [System B]"
"Set up alerts for when [condition] happens"© LeoYeAI, 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/afrexai-business-automation of LeoYeAI/openclaw-master-skills.
Open the folder on GitHubat commit e5199b5
Afrexai Business Automation 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 |
|---|---|---|---|---|---|---|
| Afrexai Business Automation this skillLeoYeAI/openclaw-master-skills | 2.2k | — | ~4.2k | 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 WorkflowsCraftOS-dev/CraftBot | 392 | 1 repos | ~2.6k | Automated safety check: Pass | MIT | |
| Automation Flowsericrisco/rsc-harness | 180 | — | ~2.9k | Automated safety check: Pass | MIT | |
| Lindy Migration Deep Divejeremylongshore/tons-of-skills-marketplace | 2.8k | — | ~2k | 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.
CraftOS-dev/CraftBot
Design and implement automation workflows to save time and scale operations as a solopreneur.
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 —…
LeoYeAI/openclaw-master-skills
Manages pipelines on a DevOps quality and efficiency platform through its OpenAPI: list workspaces and templates, create, update, run and cancel pipelines, and read run records.
LeoYeAI/openclaw-master-skills
Patches OpenClaw's Feishu extension so an edited document triggers an isolated agent session that reads the doc and replies inline, turning it into a live chat space.
LeoYeAI/openclaw-master-skills
Multi-context memory management system for OpenClaw agents with group-isolated storage, global shared memory, workspace organization, and group-specific skills isolation.
LeoYeAI/openclaw-master-skills
Runs a brand's AI-search visibility work end to end: diagnosing how AI platforms represent it, repositioning it, producing AI-optimized content and monitoring ongoing mentions.
LeoYeAI/openclaw-master-skills
Installs and authenticates the gws CLI, then automates Gmail, Drive, Sheets, Calendar, Docs, Chat and Tasks with ready-made recipes, persona bundles and security audits.
LeoYeAI/openclaw-master-skills
Runs four advisor roles, a fitness coach, nutritionist, data analyst and TCM practitioner, to build a health profile and track workouts, diet and wellness over time.
Categories
Turn your AI agent into a business automation architect. An agent skill from LeoYeAI/openclaw-master-skills. Afrexai Business Automation is an agent skill from LeoYeAI/openclaw-master-skills. Turn your AI agent into a business automation architect.
Afrexai Business Automation fits situations like: tasks that involve Workflow automation.
Run `npx skills add LeoYeAI/openclaw-master-skills --skill afrexai-business-automation -a claude-code`. Or copy the skill folder (skills/afrexai-business-automation in LeoYeAI/openclaw-master-skills) into .claude/skills/afrexai-business-automation in your project. Claude Code loads it when a task matches its description.
Run `npx skills add LeoYeAI/openclaw-master-skills --skill afrexai-business-automation -a codex`. Or copy the skill folder (skills/afrexai-business-automation in LeoYeAI/openclaw-master-skills) into .agents/skills/afrexai-business-automation 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 LeoYeAI/openclaw-master-skills --skill afrexai-business-automation -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/afrexai-business-automation, .gemini/skills/afrexai-business-automation, .github/skills/afrexai-business-automation and .opencode/skills/afrexai-business-automation in your project.
Going by SKILL.md and its folder, Afrexai Business Automation needs the command-line tools its instructions call (jq and curl) and credentials named API_TOKEN. Our summary lists: A credential in API_TOKEN.
SKILL.md contains no URLs. Its commands use curl, which can reach the network depending on how they are called. 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.
Afrexai Business Automation is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 4.2k tokens (SKILL.md is roughly 17k 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 Afrexai Business Automation: Automation Instructions (deusXmachina-dev/memorylane, 121 stars), GTM Engineering (tech-leads-club/agent-skills, 7k stars), Automation Workflows (CraftOS-dev/CraftBot, 392 stars) and Automation Flows (ericrisco/rsc-harness, 180 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
LeoYeAI (a GitHub user) maintains it in LeoYeAI/openclaw-master-skills, which has 2,161 GitHub stars. The repository holds 1,235 skills in this directory. The repository was last updated on July 20, 2026.
Source: LeoYeAI/openclaw-master-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.