# Multi Platform Messenger Bridge

> Unify WhatsApp, Telegram, and future channels with shared conversation context and message-quality assessment. Use for: bridge messengers, unified chat memory, cross-platform reply, WhatsApp responder.

- Skill: `stijnman/multi-platform-messenger-bridge` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add stijnman/multi-platform-messenger-bridge`
- Raw SKILL.md: https://api.skillmd.com/api/skills/stijnman/multi-platform-messenger-bridge/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- License: MIT
- Author: Stijnman (https://skillmd.com/u/stijnman)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/stijnman/multi-platform-messenger-bridge

---

# Multi Platform Messenger Bridge
## When to Use

- User says **bridge messengers** or task matches this capability
- User says **unified chat memory** or task matches this capability
- User says **cross-platform reply** or task matches this capability

## Workflow

1. Normalize message format across platforms (sender, channel, body, meta).
2. Route through whatsapp-message-rater (or platform equivalent).
3. Apply shared contact profile from semantic-memory-manager.
4. Dispatch reply via platform adapter; same HITL rules everywhere.

## References

Read `references/messenger-setup.md` when setup, backends, or rubric details are needed.

## Integrations

- `whatsapp-auto-responder`
- `whatsapp-message-rater`
- `semantic-memory-manager`
- `hitl-approver`

## Error Handling

| Failure | Response |
|---------|----------|
| Platform not configured | Read references/messenger-setup.md; guide setup. |
| Channel policy mismatch | Apply strictest policy across channels. |

## Gotchas

- Read references/messenger-setup.md before first use.

## Example

**Input:** User request matching triggers above.
**Output:** Structured result per workflow with integrations invoked as needed.