菜单
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.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/johnalbertini14-glitch/openclaw-skills --skill afrexai-business-automation命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
基于 SOC 职业分类
正在显示 SKILL.md
| name | afrexai-business-automation |
| description | 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. |
| auto_trigger | false |
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 metrics
Trigger: 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 confirmation
Trigger: 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 report
Trigger: 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 update
Trigger: 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 tracker
For 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"
fi
field_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/year
Instead 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-in
Not 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 < $10000
Every 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"