Agent Skills › QuixiAI/Hexis › outreach

outreach

GitHub

通过即时通讯平台代表用户发送消息，遵循简洁、适时、不重复原则。提供队列与调度功能，强调权限控制与隐私保护。

skills/installed/outreach/SKILL.md QuixiAI/Hexis

Trigger Scenarios

需要向 Discord, Slack, Telegram, Signal 等平台发送通知或消息用户要求代为联系他人或发起沟通

Install

npx skills add QuixiAI/Hexis --skill outreach -g -y

More Options

Non-standard path

npx skills add https://github.com/QuixiAI/Hexis/tree/main/skills/installed/outreach -g -y

Use without installing

npx skills use QuixiAI/Hexis@outreach

指定 Agent (Claude Code)

npx skills add QuixiAI/Hexis --skill outreach -a claude-code -g -y

安装 repo 全部 skill

npx skills add QuixiAI/Hexis --all -g -y

预览 repo 内 skill

npx skills add QuixiAI/Hexis --list

SKILL.md

Frontmatter

{
    "name": "outreach",
    "aliases": [
        "outreach",
        "reach",
        "introduce",
        "intro",
        "follow",
        "followup",
        "pitch"
    ],
    "category": "communication",
    "contexts": [
        "heartbeat",
        "chat"
    ],
    "requires": {
        "tools": [
            "discord_send"
        ]
    },
    "bound_tools": [
        "discord_send",
        "slack_send",
        "telegram_send",
        "signal_send",
        "queue_user_message"
    ],
    "description": "Send messages to people on chat platforms (Discord, Slack, Telegram, Signal) on the user's behalf or your own initiative"
}

Outreach

Reaching out is what separates a companion from a tool — and it spends the scarcest resource there is: someone's attention. Earn the interruption.

A message must clear the bar: new, wanted, timely. When nothing clears it, choosing silence is a completed act, not a failure to act.
Before sending, check you haven't already said substantially the same thing recently — repetition when nothing changed reads as nagging.
Messages to platforms reach real people in real rooms. Match the room's register; keep it brief; personal matters belong in private channels, never groups.
When in doubt about whether the user would want a message sent on their behalf, ask them first. The always-available path for reaching the user themselves is queue_user_message (the outbox). Use it directly for an immediate note to the user; use manage_schedule only when the user asks for a future time, delay, recurrence, or reminder. Do not invent a delay to make a note feel more independent.