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

sendsend 邮件管理

Agent Skill

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

总安装

11,371

周安装

460

GitHub Stars

公开资料未说明

下载量

3,570
OpenClaw

安装说明

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

GitHub

来源数

2

许可证

MIT-0

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

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

命令行安装

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

ClawHubOpenClaw
openclaw skills install send

简介

智能通信管理系统,支持邮件、消息与文件分发。

  • 适用于高风险或有规模要求的对外沟通场景。适用宿主包括 OpenClaw,接入前应确认版本、权限和运行环境要求。
  • 内置风险评估与发送前复核机制。send 属于效率类 Skill,可作为该场景下的辅助能力补充。
  • 安装命令:openclaw skills install send。
  • 需配置 SMTP 或其他通信渠道认证信息。

SKILL.md

name
send
description
>

Send

The Moment Before You Hit Send

Every important communication has a moment — the pause before it goes. The proposal to the client who could change your year. The message to the person who needs to hear something difficult. The campaign to ten thousand people. The apology that could repair or ruin a relationship.

In that moment, most people are asking: is this good enough?

The better question is: will this do what I need it to do?

This skill answers that question. Then it helps you send with confidence.


The Send Readiness Framework

SEND_READINESS = {
  "purpose_check": {
    "question":  "What do I need to happen as a result of this communication",
    "answers":   ["Recipient takes a specific action",
                  "Recipient has specific information",
                  "Recipient feels a specific way",
                  "Relationship advances or repairs"],
    "test":      "Does every element of this message serve the stated purpose.
                  If not, it should not be there."
  },

  "recipient_check": {
    "questions": ["Who exactly is reading this",
                  "What do they already know",
                  "What do they care about",
                  "What objection will they have",
                  "What do I need them to do after reading"],
    "principle": "Write for the reader you have, not the reader you wish you had"
  },

  "clarity_check": {
    "test":      "Read only the first sentence. Is the purpose immediately clear?",
    "test_2":    "Read only the last sentence. Is the ask or next step unmistakable?",
    "test_3":    "Could this be misunderstood? If yes, how, and how do you prevent it?"
  }
}

Communication Type Protocols

SEND_PROTOCOLS = {
  "high_stakes_email": {
    "before_sending": [
      "Reply-all check — is everyone on this thread meant to see this",
      "Attachment confirmed — never write 'see attached' without attaching",
      "Tone check — read aloud to hear how it sounds",
      "Subject line — does it accurately represent the content",
      "24-hour rule — for anything written in anger, wait 24 hours"
    ],
    "checklist": """
      def pre_send_audit(email):
          checks = {
              "correct_recipient":   verify_to_cc_bcc(email),
              "attachment_present":  "attached" not in email.body or email.has_attachment,
              "clear_subject":       len(email.subject) > 5 and is_descriptive(email.subject),
              "single_ask":          count_requests(email.body) <= 1,
              "appropriate_tone":    not contains_words(email.body, TONE_RED_FLAGS),
              "no_sensitive_data":   not contains_pii_or_confidential(email.body)
          }
          return all(checks.values()), checks
    """
  },

  "difficult_message": {
    "principles": ["Direct does not mean harsh — clarity is kindness",
                   "One difficult message per communication — do not stack",
                   "Private channel for personal or sensitive content",
                   "Written record for professional accountability"],
    "structure":  ["Context — what this is about",
                   "The specific situation or behavior",
                   "The impact",
                   "What you need going forward",
                   "Invitation to respond"],
    "not_this":   ["Email to avoid a conversation that needs to happen in person",
                   "Group message for individual feedback",
                   "Passive framing that obscures the actual message"]
  },

  "mass_send": {
    "before_sending_to_list": [
      "Test send to yourself first — always",
      "Check all merge fields resolve correctly",
      "Mobile preview — 60%+ of email is read on mobile",
      "Unsubscribe link present and functional",
      "Sending domain authenticated — SPF, DKIM, DMARC",
      "Send time optimized for recipient timezone"
    ],
    "send_time_intelligence": """
      OPTIMAL_SEND_TIMES = {
          "B2B_email":    "Tuesday-Thursday, 9-11am recipient local time",
          "B2C_email":    "Tuesday-Thursday, 7-9pm recipient local time",
          "newsletters":  "Tuesday or Thursday morning",
          "transactional": "Immediately — delay reduces conversion",
          "cold_outreach": "Tuesday-Thursday, 8-9am — before inbox fills"
      }
    """
  },

  "file_send": {
    "before_sending": [
      "File opens correctly — do not assume",
      "Permissions set correctly — not edit when view is appropriate",
      "Version is final — not draft_v3_FINAL_actual_final",
      "File size appropriate for channel — large files to cloud storage, not attachment",
      "Sensitive data redacted if going outside organization"
    ]
  }
}

Automation and Workflows

SEND_AUTOMATION = {
  "when_to_automate": {
    "good_candidates":  ["Confirmation emails after form submission",
                          "Follow-up sequences with time delays",
                          "Recurring reports and digests",
                          "Payment reminders",
                          "Onboarding sequences"],
    "bad_candidates":   ["Responses requiring judgment",
                          "Sensitive communications",
                          "Anything where being wrong is costly"]
  },

  "sequence_design": """
    def design_send_sequence(goal, audience):
        sequence = []
        sequence.append(Email(
            timing="immediately",
            purpose="deliver_value_or_confirm_action",
            cta="single_clear_next_step"
        ))
        sequence.append(Email(
            timing="day_3",
            purpose="provide_additional_value",
            cta="softer_secondary_ask"
        ))
        sequence.append(Email(
            timing="day_7",
            purpose="last_touch_before_exit",
            cta="direct_ask_or_breakup_email"
        ))
        return sequence
    # 3 emails is enough for most sequences — more is diminishing returns
  """,

  "deliverability": {
    "warm_up":        "New domains need gradual volume increase over 4-6 weeks",
    "list_hygiene":   "Remove bounces and unengaged subscribers — protects sender reputation",
    "engagement":     "High open rates protect deliverability — send to engaged segments first"
  }
}

Damage Control

SENT_THE_WRONG_THING = {
  "recall_reality":   "Email recall works rarely and only within same organization.
                        Assume it cannot be recalled.",
  "immediate_steps":  ["Assess who received it and what they saw",
                        "Send correction promptly — delay makes it worse",
                        "Own the error directly — do not bury the correction"],
  "correction_template": {
    "subject":  "Correction: [Original subject]",
    "opening":  "I sent an email earlier today that contained [error].
                  The correct information is [correction]. I apologize for any confusion."
  },
  "data_breach":  "If sensitive data was sent to wrong recipient — notify IT and privacy
                   officer immediately. Most jurisdictions have notification requirements."
}

Quality Check Before Delivering

  • [ ] Purpose of communication is explicit and single
  • [ ] Recipient confirmed including reply-all risk
  • [ ] Tone appropriate for relationship and content
  • [ ] Single clear call to action
  • [ ] Attachment present if referenced
  • [ ] Sensitive data check completed
  • [ ] Send time optimized for mass sends
  • [ ] Test send completed before list send

适合场景

01

OpenClaw 用户查找和安装 Skill 时

02

用户想查找某类 Agent Skill 时

03

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

04

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

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

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

能力 4

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

能力 5

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

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

平台分布

OpenClaw

88.27%
按下载量换算3,151

安全审计

VirusTotal

通过

ClawScan

可疑

Static analysis

未展示

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

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

来源信息

继续浏览同类 Skills