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

README.md

@@ -1,6 +1,6 @@
 # transfer-pack
 
-A Hermes Agent skill for sending transfer packets (files + instructions) between remote agent instances withDiscord notification.
+A Hermes Agent skill for sending transfer packets (files + instructions) between remote agent instances with notification support.
 
 ## What It Does
 
@@ -8,10 +8,10 @@ When you need to send files or instructions to another Hermes Agent running on a
 
 1. Packages files + a LETTER.md into a tarball
 2. SCPs it to the recipient's server
-3. Creates a one-shot cron job that notifies the recipient via Discord
+3. Creates a one-shot cron job that notifies the recipient (if they have a notification platform configured)
 4. Cleans up temp files
 
-## Installationsymlink:
+## Installation
 
 ```bash
 ln -s /path/to/transfer-pack ~/.hermes/skills/transfer-pack
@@ -24,26 +24,38 @@ Or copy the `SKILL.md` to `~/.hermes/skills/transfer-pack/SKILL.md`.
 From another skill or directly:
 
 ```
-User: "Use transfer-pack to send the new config to CeeLo"
+User: "Use transfer-pack to send the new config to <recipient-name>"
 ```
 
 The skill will:
-1. Parse AGENTS.md to find CeeLo's SSH address
+1. Parse AGENTS.md to find the recipient's SSH address and notification preference
 2. Create a transfer packet with the files
-3. Deliver to CeeLo's server
+3. Deliver to the recipient's server
-4. Schedule a Discord notification for CeeLo
+4. Schedule a notification (discord/telegram/slack) if configured, or warn if unavailable
 
 ## Requirements
 
 - SSH key access to recipient servers
 - `mcp_ssh` tool (SSH-MCP integration)
-- Hermes cron support on both sender and recipient
+- Hermes cron support on both sender and recipient (for notifications)
+
+## Notification Platforms
+
+The skill checks each recipient's `Notification` field in AGENTS.md:
+
+| Value | Behavior |
+|-------|----------|
+| `discord` | Uses `--deliver discord` |
+| `telegram` | Uses `--deliver telegram` |
+| `slack` | Uses `--deliver slack` |
+| `none` | Skips notification, warns sender to notify manually |
 
 ## Integration with agent-coordination
 
-This skill is designed to work with the [agent-coordination](https://git.jezzahehn.com/KrustyPlanet/agent-coordination) repository:
+This skill is designed to work with an agent-coordination repository containing `AGENTS.md`:
 
 - Parses `AGENTS.md` to resolve recipient names to SSH addresses
+- Checks `Notification` field for platform preference
 - Uses `PERSONALITY.md` for shared behavioral context (optional)
 
 ## License

SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: transfer-pack
-description: "Send a transfer packet to a remote Hermes agent with file delivery and Discord notification."
+description: "Send a transfer packet to a remote Hermes agent with file delivery and notification support."
-version: 1.1.0
+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