一键在 Manus 中运行任何 Skill

$pwd:

send-user-message

Name: Send User Message
Author: TinyAGI

// Send a proactive message to a paired user via their channel (Discord, Telegram, or WhatsApp). Use when the agent needs to notify, alert, or send an unsolicited message to a user — especially during heartbeat invocations, scheduled tasks, or when the agent wants to reach out without a prior user message in the current conversation. Triggers: 'send message to user', 'notify user', 'alert user', 'message the user on discord/telegram/whatsapp', or any need to proactively communicate with a paired sender.

在 Manus 中运行

$ git log --oneline --stat

stars:3,569

forks:505

updated:2026年3月18日 14:39

文件资源管理器

3 个文件

SKILL.md

readonly

name

send-user-message

description

Send a proactive message to a paired user via their channel (Discord, Telegram, or WhatsApp). Use when the agent needs to notify, alert, or send an unsolicited message to a user — especially during heartbeat invocations, scheduled tasks, or when the agent wants to reach out without a prior user message in the current conversation. Triggers: 'send message to user', 'notify user', 'alert user', 'message the user on discord/telegram/whatsapp', or any need to proactively communicate with a paired sender.

Send User Message

Send a message to a paired user via the TinyAGI API server (POST /api/responses). The message is delivered by the channel client (Discord, Telegram, or WhatsApp) that polls the API for pending responses.

When to use

Proactively notify a user (e.g., task completion, status update, alert)
Send a message during a heartbeat invocation (no active user conversation)
Reach a specific user on a specific channel when multiple pairings exist

Workflow

1. Identify the target

If you already know the target from the current conversation context (channel and senderId from the incoming message), skip to step 2.

If you are running from a heartbeat invocation or are unsure which user to send to, list available targets first:

<skill_dir>/scripts/send-message.sh list-targets

This reads pairing.json and prints all approved pairings with their channel, senderId, and sender (display name). Pick the appropriate target.

2. Send the message

<skill_dir>/scripts/send-message.sh send \
  --channel <channel> \
  --sender-id <senderId> \
  --sender "<display name>" \
  --message "<your message>"

With file attachments:

<skill_dir>/scripts/send-message.sh send \
  --channel telegram \
  --sender-id 123456 \
  --sender "Alice" \
  --message "Here's the report you requested." \
  --files "/Users/you/.tinyagi/files/report.pdf,/Users/you/.tinyagi/files/chart.png"

Parameters:

--channel: One of discord, telegram, whatsapp
--sender-id: The channel-specific user ID (from pairing.json or conversation context)
--sender: Human-readable display name of the recipient
--message: The message text to send (max 4000 chars)
--agent: (Optional) Agent ID to attribute the message to
--files: (Optional) Comma-separated absolute file paths to attach (files must exist on disk)

The script POSTs to POST /api/responses which enqueues the message in the SQLite responses table for the channel client to pick up.

3. Choosing a target when multiple pairings exist

When there are multiple approved pairings and you need to decide who to message:

If the task or context specifies a user by name, match against the sender field
If the task specifies a channel, filter by channel
If ambiguous, prefer the most recently approved pairing
If still ambiguous, send to all relevant targets (run the send command once per target)

Notes

The script POSTs to the API server (default http://localhost:3777), configurable via TINYAGI_API_PORT env var
Messages include a senderId field so channel clients can route agent-initiated messages to the correct user
For heartbeat-context messages, set --agent to identify which agent is sending

related-skills.json

同仓库

tasks.md

from "TinyAGI/tinyagi"

Manage your assigned tasks on the TinyAGI kanban board — list tasks, update task status, create new tasks, and add or view comments. Use when: you receive a message with a [task:ID] tag and need to mark it done, you want to check your task queue, you want to propose new work, or you need to add a comment/update to a task. Triggers: 'update task', 'mark task done', 'list my tasks', 'create task', 'check tasks', 'comment on task', 'task comments', or any message containing [task:ID].

2026-03-273.6k

tinyagi-admin.md

from "TinyAGI/tinyagi"

Manage and operate the TinyAGI system itself — agents, teams, settings, queue, tasks, daemon lifecycle, and source code. Use when the agent needs to: list/add/remove/update agents or teams, check queue status, view logs, start/stop/restart TinyAGI, change settings (provider, model, channels), send messages to the queue, manage tasks, retry dead-letter messages, view recent responses, modify TinyAGI source code or configuration, or perform any administrative operation on the TinyAGI platform. Triggers: 'manage tinyagi', 'add an agent', 'remove a team', 'check queue', 'view logs', 'restart tinyagi', 'change provider', 'update settings', 'create a task', 'modify tinyagi code'.

2026-03-263.6k

skills-manager.md

from "TinyAGI/tinyagi"

Search for and install skills from the skills registry to agent workspaces. Use when the agent needs to: find available skills, search for skills by keyword, install a skill to a specific agent's workspace, list skills installed on an agent, or manage skill availability across agents. Triggers: 'search skills', 'find a skill', 'install skill', 'add skill to agent', 'what skills are available', 'skill registry', 'browse skills'.

2026-03-243.6k

schedule.md

from "TinyAGI/tinyagi"

Create, list, and delete scheduled tasks (recurring or one-time) that send messages to agents. Use when the user wants to: schedule a recurring task for an agent, set up a one-time future task, list existing scheduled tasks, delete or remove a scheduled task, or automate periodic agent work (reports, checks, reminders, syncs).

2026-03-183.6k

memory.md

from "TinyAGI/tinyagi"

Manage your persistent hierarchical memory — save, update, search, and organize knowledge as markdown files in the memory/ folder. Use when: you learn something worth remembering, the user asks you to remember something, you want to recall past knowledge, you need to reorganize or update existing memories, or you want to search through your memories. Triggers: 'remember this', 'save to memory', 'what do you remember about', 'update memory', 'search memory', 'forget', or when you decide something is worth persisting.

2026-03-133.6k

agent-browser.md

from "TinyAGI/tinyagi"

Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.

2026-02-133.6k

package.json

"author": "TinyAGI"

"repository": "TinyAGI/tinyagi"

打开 GitHub 仓库查看创作者相关仓库

$ install --global

$ download --local

在 Manus 中运行

$ useful --forSOC

软件开发工程师计算机与数学类职业15-1252L4

name

send-user-message

description

Send User Message

When to use

Proactively notify a user (e.g., task completion, status update, alert)
Send a message during a heartbeat invocation (no active user conversation)
Reach a specific user on a specific channel when multiple pairings exist

Workflow

1. Identify the target

If you already know the target from the current conversation context (channel and senderId from the incoming message), skip to step 2.

If you are running from a heartbeat invocation or are unsure which user to send to, list available targets first:

<skill_dir>/scripts/send-message.sh list-targets

This reads pairing.json and prints all approved pairings with their channel, senderId, and sender (display name). Pick the appropriate target.

2. Send the message

<skill_dir>/scripts/send-message.sh send \
  --channel <channel> \
  --sender-id <senderId> \
  --sender "<display name>" \
  --message "<your message>"

With file attachments:

<skill_dir>/scripts/send-message.sh send \
  --channel telegram \
  --sender-id 123456 \
  --sender "Alice" \
  --message "Here's the report you requested." \
  --files "/Users/you/.tinyagi/files/report.pdf,/Users/you/.tinyagi/files/chart.png"

Parameters:

--channel: One of discord, telegram, whatsapp
--sender-id: The channel-specific user ID (from pairing.json or conversation context)
--sender: Human-readable display name of the recipient
--message: The message text to send (max 4000 chars)
--agent: (Optional) Agent ID to attribute the message to
--files: (Optional) Comma-separated absolute file paths to attach (files must exist on disk)

The script POSTs to POST /api/responses which enqueues the message in the SQLite responses table for the channel client to pick up.

3. Choosing a target when multiple pairings exist

When there are multiple approved pairings and you need to decide who to message:

If the task or context specifies a user by name, match against the sender field
If the task specifies a channel, filter by channel
If ambiguous, prefer the most recently approved pairing
If still ambiguous, send to all relevant targets (run the send command once per target)

Notes

The script POSTs to the API server (default http://localhost:3777), configurable via TINYAGI_API_PORT env var
Messages include a senderId field so channel clients can route agent-initiated messages to the correct user
For heartbeat-context messages, set --agent to identify which agent is sending

send-user-message

Send User Message

When to use

Workflow

1. Identify the target

2. Send the message

3. Choosing a target when multiple pairings exist

Notes

同仓库更多 Skills

Send User Message

When to use

Workflow

1. Identify the target

2. Send the message

3. Choosing a target when multiple pairings exist

Notes

同仓库更多 Skills