animal-messenger

Automate asynchronous message delivery across webhooks, batch email, and pub/sub channels.

105|13|Updated Mar 9, 2026

Search Tags:#messaging #asynchronous #webhook #idempotency #delivery #retry #dead-letter

Ready to run

npx skills add https://github.com/Hmbown/Wizards-of-the-Ghosts --skill animal-messenger

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: animal-messenger
Source: https://github.com/Hmbown/Wizards-of-the-Ghosts/tree/main/generated/hermes/messaging-and-coordination/animal-messenger
Command: npx skills add https://github.com/Hmbown/Wizards-of-the-Ghosts --skill animal-messenger

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Asynchronous delivery paths can be unreliable or hard to coordinate, risking lost or duplicate messages and fragile integrations.

Core Features & Use Cases

Handles fire-and-forget delivery with retries and dead-letter support across webhooks, batch email, and pub/sub systems.
Ensures idempotent delivery and clear signaling of success, delay, or failure to downstream services.
Typical Use Case: integrate with a webhook-based workflow where messages may arrive late but must eventually succeed.

Quick Start

Configure Animal Messenger with a target channel and a retry policy to ensure eventual delivery and reliable handoffs.

Frequently Asked Questions about animal-messenger

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I ensure reliable asynchronous message delivery across webhooks?▼

Reliable asynchronous message delivery across webhooks requires configuring a target channel and a retry policy to ensure eventual delivery, manage late-arriving messages, and coordinate reliable handoffs.

What is dead-letter support and when do I need it for pub/sub channels?▼

Dead-letter support captures messages that fail asynchronous delivery after exhausting retries, providing clear failure signaling to downstream pub/sub systems when messages cannot be successfully processed.

How do I prevent duplicate messages in an asynchronous batch email workflow?▼

Preventing duplicate messages in batch email workflows requires idempotent delivery, which ensures that repeated retry attempts process safely without generating duplicate downstream messages.

Can I use fire-and-forget delivery for integrations where timing is tolerant but reliability matters?▼

Yes, fire-and-forget delivery suits integrations where timing is tolerant but reliability matters by enforcing idempotent delivery, automated retries, and explicit success, delay, or failure signaling across asynchronous paths.

How do I compose a message contract for asynchronous delivery?▼

Composing a message contract for asynchronous delivery involves defining delivery assumptions, explicit deliverables, and privacy safety requirements to coordinate reliable handoffs across webhook queues and pub/sub channels.