transfer-pack/README.md

63 lines
No EOL
1.8 KiB
Markdown

# transfer-pack
A Hermes Agent skill for sending transfer packets (files + instructions) between remote agent instances with notification support.
## What It Does
When you need to send files or instructions to another Hermes Agent running on a different machine, this skill:
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 (if they have a notification platform configured)
4. Cleans up temp files
## Installation
```bash
ln -s /path/to/transfer-pack ~/.hermes/skills/transfer-pack
```
Or copy the `SKILL.md` to `~/.hermes/skills/transfer-pack/SKILL.md`.
## Usage
From another skill or directly:
```
User: "Use transfer-pack to send the new config to <recipient-name>"
```
The skill will:
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 the recipient's server
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 (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 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
MIT