Token导航 LogoToken导航TokenDH.com
效率需要联网clawhub未标认证来源可访问clear审计提醒

email-approval-workflow电子邮件审批工作流程

Agent Skill

email-approval-workflow 用于补充效率相关能力,适合在 OpenClaw 中需要让 Agent 承接效率相关任务时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

2,172

周安装

87

GitHub Stars

公开资料未说明

下载量

703
OpenClaw

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

MIT-0

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:email-approval-workflow(电子邮件审批工作流程)
来源仓库:https://github.com/stefanferreira/email-approval-workflow
安装命令:
openclaw skills install email-approval-workflow
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 OpenClaw 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

ClawHubOpenClaw
openclaw skills install email-approval-workflow

简介

电子邮件审批工作流程技能起草外部邮件供人工批准。

  • 适用于与外部方沟通,确保邮件内容的准确性和合规性。
  • 通过模板化流程提升沟通效率,适合在OpenClaw中辅助效率任务。
  • 安装命令为openclaw skills install email-approval-workflow,需确认权限和操作边界。
  • 建议参考原始README了解具体规则,注意维护状态和网络访问限制。

SKILL.md

name
email-approval-workflow
description
Draft external emails for human approval before sending. Use when communicating with external parties (support, competitions, businesses). Always draft first, send to Stef for approval, then send only after explicit approval.

Email Approval Workflow

Purpose

Ensure all external communications are reviewed and approved by Stef before sending. Prevents miscommunication, maintains professional standards, and allows for strategic input.

When to Use This Workflow

Use for:

  • Support tickets (Contabo, services, etc.)
  • Competition entries
  • Business inquiries
  • Partnership discussions
  • Any external communication

Do NOT use for:

  • Internal agent communications
  • System notifications
  • Automated reports (unless specified)

Workflow Steps

Step 1: Draft Creation

# Create draft in drafts/ folder
mkdir -p /root/.openclaw/workspace/drafts/
cat > /root/.openclaw/workspace/drafts/{purpose}_draft.md << 'EOF'
TO: recipient@example.com
FROM: Appropriate Agent <agent@domain.com>
CC: Stef Ferreira <stef.personal@gmail.com>
SUBJECT: Clear, descriptive subject
DATE: $(date +"%B %d, %Y")

[Professional email content]

Best regards,

[Agent Name]
[Organization]
[Email]
EOF

Step 2: Present for Approval

Present draft to Stef in current chat interface:
"Here's a draft email for [purpose]. Please review and approve:"

[Copy draft content]

Step 3: Await Approval

  • Wait for explicit "approved" or "send it" confirmation
  • If edits requested, update draft and resubmit
  • Never send without explicit approval

Step 4: Send Email

# After approval, send using email system
cd /root/.openclaw/workspace && \
python3 email_manager.py send \
  --to "recipient@example.com" \
  --subject "Approved Subject" \
  --body "$(cat /root/.openclaw/workspace/drafts/{purpose}_draft.md | tail -n +7)"

Step 5: Document

# Log sent email
echo "$(date -Iseconds)|{purpose}|{recipient}|SENT|APPROVED_BY_STEF" >> /root/.openclaw/workspace/email_log.csv

Draft Template

TO: [recipient@example.com]
FROM: [Agent Name] <[agent@domain.com]>
CC: Stef Ferreira <stef.personal@gmail.com>
SUBJECT: [Clear, descriptive subject]
DATE: [Month Day, Year]

[Professional greeting],

[Clear, concise message with:
1. Purpose/context
2. Specific request/information
3. Supporting details
4. Call to action
5. Appreciation]

[Professional closing],

[Agent Name]
[Organization/Role]
[Contact email]

Approval Triggers

Stef must explicitly say one of:

  • "Approved"
  • "Send it"
  • "Go ahead"
  • "Yes, send that"

NOT approved by:

  • "Looks good" (needs explicit send instruction)
  • "OK" (ambiguous)
  • Silence (never assume approval)

Examples

Example 1: Support Ticket Follow-up

TO: support@contabo.com
FROM: Ace <ace@SupplyStoreAfrica.com>
CC: Stef Ferreira <stef.personal@gmail.com>
SUBJECT: Re: [#16240135688]: Network issues on our VPS
DATE: March 31, 2026

Dear Svitlana,

Thank you for your prompt response. To help us plan, could you provide:

1. Estimated timeline for resolution?
2. Will you provide proactive updates?
3. Any specific workarounds we should implement?

Current status: DNS workaround working, intermittent connectivity continues.

Thank you for your assistance.

Best regards,

Ace
Supply Store Africa
ace@SupplyStoreAfrica.com

Example 2: Competition Entry

TO: competitions@company.com
FROM: Ace <ace@SupplyStoreAfrica.com>
CC: Stef Ferreira <stef.personal@gmail.com>
SUBJECT: Entry: [Competition Name]
DATE: March 31, 2026

Dear Competition Team,

Please accept my entry for the [Competition Name].

[Required entry details]

Thank you for this opportunity.

Best regards,

Ace
Supply Store Africa
ace@SupplyStoreAfrica.com

Error Handling

If email fails to send:

  1. Check network connectivity
  2. Verify email credentials
  3. Try alternative SMTP if configured
  4. Report failure to Stef with error details

If no response to approval request:

  1. Wait minimum 1 hour
  2. Send polite follow-up: "Just checking if you had a chance to review the draft?"
  3. Never send without approval

Integration with Agents

Ace (Competitions Agent)

  • Uses this workflow for all competition entries
  • Maintains draft folder: /root/.openclaw/workspace/agents/ace/drafts/

Lourens (SysAdmin)

  • Uses for support tickets, infrastructure communications
  • Maintains audit trail of all sent emails

Facet (CAD Specialist)

  • May use for technical inquiries with manufacturers/suppliers

Audit Trail

All emails tracked in:

  • /root/.openclaw/workspace/email_log.csv
  • Individual agent logs
  • Email system sent items

Related Skills

  • gmail-gog-setup - Email system configuration
  • secure-secret-sharing - For sharing draft links if needed
  • telegram-multi-bot - For approval notifications via Telegram

适合场景

01

OpenClaw 用户查找和安装 Skill 时

02

用户想查找某类 Agent Skill 时

03

需要根据任务场景推荐可安装能力包时

04

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

补充不同宿主或平台的使用分布数据

能力 5

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

OpenClaw

76.51%
按下载量换算538

安全审计

VirusTotal

可疑

ClawScan

通过

Static analysis

通过

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在 warning/failed 结果,不能写成本站确认安全。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills