feat: Hermes gateway agent skills — Telegram, Discord, Slack, WhatsApp

[tonyagents]

Summary

Adds four new skills that deploy the MoonPay CLI as a persistent messaging bot using Hermes Agent gateway — the open-source agent framework with built-in platform adapters for Telegram, Discord, Slack, WhatsApp, Signal, and more.

• moonpay-telegram — Deploy via Telegram (@Botfather token, long-poll or webhook mode)
• moonpay-discord — Deploy via Discord (bot token, Message Content Intent, Socket or HTTP)
• moonpay-slack — Deploy via Slack (Socket Mode, no public URL required)
• moonpay-whatsapp — Deploy via WhatsApp (Baileys QR-code bridge, no Meta API needed)

Each skill covers: Hermes install, platform bot creation, env config, a MoonPay CONTEXT.md system prompt, gateway start/stop/status, log paths, and an error-handling table.

How it works

# 1. Install Hermes
curl -fsSL https://raw.githubusercontent.com/NousResearch/hermes-agent/main/scripts/install.sh | bash

# 2. Set platform token (e.g. Telegram)
echo 'TELEGRAM_BOT_TOKEN=<token>' >> ~/.hermes/.env

# 3. Add MoonPay context
# (CONTEXT.md with mp CLI system prompt — included in each skill)

# 4. Start
hermes gateway start

Once running, users message the bot naturally and the agent calls mp commands on their behalf — wallets, swaps, prices, prediction markets.

Test plan

• Verify each SKILL.md passes frontmatter lint (name, description, tags present)
• Confirm Hermes install command is current (check NousResearch/hermes-agent README)
• Smoke-test Telegram skill end-to-end with a test bot token
• Check all mp commands reference valid CLI subcommands (mp --help)
• Verify cross-links to related skills resolve correctly

🤖 Generated with Claude Code

[kevarifin14]

D — Skills not registered in marketplace.json

Four new skills added but zero marketplace.json changes. Skills won't be discoverable by Claude Code without registration.

Blockers

1. marketplace.json missing — Add a new plugin block for these. Since they're Hermes gateway skills (not MoonPay CLI features directly), a dedicated block is the right structure:

   {
     "name": "hermes-skills",
     "description": "Deploy MoonPay CLI as a persistent gateway bot via Hermes Agent — Telegram, Discord, Slack, WhatsApp",
     "source": "./",
     "strict": false,
     "skills": [
       "./skills/moonpay-telegram",
       "./skills/moonpay-discord",
       "./skills/moonpay-slack",
       "./skills/moonpay-whatsapp"
     ]
   }

2. Naming ambiguity — These are moonpay-* named but the primary functionality is Hermes gateway deployment, not MoonPay CLI features. Two options:

   • Keep moonpay-{platform} names and clearly document they're Hermes-backed (current approach) — acceptable since they wrap the MoonPay CLI as a bot
   • Rename to hermes-{telegram,discord,slack,whatsapp} for semantic clarity

   Either is fine — pick one and make the marketplace block match.

Verified OK

• Hermes install script real: raw.githubusercontent.com/NousResearch/hermes-agent/main/scripts/install.sh ✓
• hermes --version/gateway/config set/whatsapp commands documented in Hermes README ✓
• All mp commands (mp wallet list, mp token swap, mp user retrieve) consistent with existing skills ✓
• No code, all instructional ✓
• Cross-references to moonpay-auth, moonpay-swap-tokens, moonpay-trading-automation valid ✓
• Clean diff, WhatsApp ToS note present ✓

Add marketplace.json and this is A- ready.