v1.2.0: Fully identity-agnostic, support multiple notification platforms

This commit is contained in:
BarnacleBoy 2026-05-08 16:11:32 +00:00
parent 1541a6c238
commit 5ffa3e6762
2 changed files with 27 additions and 14 deletions

View file

@ -1,7 +1,7 @@
---
name: transfer-pack
description: "Send a transfer packet to a remote Hermes agent with file delivery and Discord notification."
version: 1.1.0
description: "Send a transfer packet to a remote Hermes agent with file delivery and notification support."
version: 1.2.0
metadata:
hermes:
tags: [transfer, agent-communication, scp, cron]
@ -9,13 +9,13 @@ metadata:
# Transfer Pack
Send a transfer packet (files + letter) to a remote Hermes Agent instance. The recipient agent reads the letter and responds via Discord.
Send a transfer packet (files + letter) to a remote Hermes Agent instance. The recipient agent reads the letter and responds via their configured notification platform.
## Prerequisites
- SSH key access to recipient agent's server
- `mcp_ssh` tool available (SSH-MCP)
- Both agents must have Hermes cron support
- Hermes cron support on both agents (for notifications)
## Configuration
@ -23,10 +23,11 @@ Before using, identify from context or AGENTS.md:
| Variable | Source |
|----------|--------|
| SENDER_NAME | Your agent name (e.g., BarnacleBoy, Lucy, CeeLo, MermaidMan) |
| SENDER_NAME | Your agent name |
| RECIPIENT_NAME | Target agent name from AGENTS.md |
| RECIPIENT_SSH_HOST | Tailscale address from AGENTS.md |
| RECIPIENT_SSH_USER | SSH username for recipient server |
| RECIPIENT_NOTIFICATION | Notification platform from AGENTS.md (discord/telegram/slack/none) |
| USER_NAME | Human operator's name (for acknowledgment) |
## Procedure