Messaging Adapter Parity
Apps & Automationmessaging-adapter-parityMessaging Adapter Parity is an Agent Skill for apps & automation published in the spacedriveapp/spacebot repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
This skill should be used when the user asks to change "Slack adapter", "Telegram adapter", "Discord adapter", "Webhook adapter", "status delivery", "message routing", or "delivery receipts". Enforces cross-adapter parity and explicit delivery semantics.
QUICK START
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/spacedriveapp/spacebot/blob/HEAD/.agents/skills/messaging-adapter-parity/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/messaging-adapter-parity, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
Messaging Adapter Parity
Goal
Prevent adapter-specific regressions by validating behavior contracts across messaging backends.
Contract Areas
- User-visible reply behavior
- Status update behavior (
surfacedvsnot surfaced) - Delivery receipt ack/failure semantics
- Retry behavior and bounded backoff
- Error mapping and logging clarity
Parity Checklist
- For every changed adapter path, compare expected behavior with at least one other adapter.
- If an adapter intentionally does not surface a status, ensure receipt handling still converges correctly.
- Ensure unsupported features degrade gracefully and predictably.
- Ensure worker terminal notices cannot loop indefinitely.
Verification Checklist
- Run targeted tests for the touched adapter.
- Run targeted tests for receipt ack/failure paths.
- Run at least one parity comparison check across adapters.
- Run broad gate checks after targeted checks pass.
Required Handoff
- Adapter paths changed
- Contract decisions made
- Receipt behavior outcomes
- Verification evidence
- Residual parity gaps