bluebubbles

This is a developer-oriented skill and should be judged that way: it lays out where each piece lives (channel implementation, webhook handler, send and probe helpers, runtime bridge, catalog entry) and which internal helpers to call instead of hand-rolling API requests. That last instruction is the valuable one, because a plugin that bypasses the shared probe and send helpers tends to drift from the rest of the integration. Rating is three because it assumes a working knowledge of the extension package layout and offers little for someone who only wants messages to arrive; there is no troubleshooting path for the common failure where the webhook registers but nothing is delivered. Best used alongside the channel plugin's own runtime logs, and treat the catalog entry as the thing to update whenever onboarding needs to find the plugin.

Use case: Maintaining or extending the messaging channel plugin rather than configuring it as an end user.

# Work through the plugin's own helpers, never the raw transport This skill is about building and updating a chat channel plugin, and its organisation tells you how to work on it. The plugin is laid out as an extension package with a channel implementation, a webhook monitor, REST helpers and a runtime bridge — and the skill is explicit that the helpers should be used instead of issuing raw requests. ## Learn the layout before editing anything The entry point, the channel implementation and the webhook monitor are separate files, and inbound events arrive through a handler registered at runtime. If you edit a helper without knowing which of these calls it, you will fix one path and leave the other broken. ## Use the provided helpers Inbound media, reactions, typing indicators and read receipts each have their own helper. Reimplementing one of those with a direct request bypasses the timeout handling and error mapping that the helper already implements, which is how a plugin ends up with one robust path and three fragile ones. ## Register the webhook through the sanctioned entry point Inbound webhooks must be registered through the plugin's registration API rather than patched in beside it. A handler registered outside that path will work in testing and disappear on reload. ## Health checks belong in the probe helper There is a dedicated probe helper for connectivity. Use it for readiness checks instead of sending a message and inferring health from whether it failed, because a send can fail for reasons that have nothing to do with connectivity.