← ClaudeAtlas

chat-delivery-adapterslisted

The delivery-adapter contract every advanced-workflow skill uses to post its finished report somewhere a human will see it — Slack, an IT Glue document, or (blocked) Microsoft Teams.
WYRE-AI/msp-claude-plugins · ★ 55 · AI & Automation · score 84
Install: claude install-skill WYRE-AI/msp-claude-plugins
## The contract Every workflow's body produces a **report payload**; a delivery adapter takes that payload and writes it somewhere a human will see it. Detect which delivery target is connected the same way you detect a data-role vendor: if more than one is connected, ask the human which to use; if none is connected, tell the human what's needed — don't guess, don't fail silently. ## Shipped adapters ### Slack summary - **Connector**: Slack (first-party claude.ai connector, not Conduit-routed). - **permitted_tools**: `slack_send_message`. - **Write snippet**: post a one-paragraph summary to the destination channel. - **Limits**: plain text, no rich layout — best for a short result. ### Slack canvas - **Connector**: Slack. - **permitted_tools**: `slack_create_canvas`, `slack_send_message`. - **Write snippet**: create a canvas titled `<report name> — <date>` with the full report; post a summary message linking it. - **Limits**: one canvas per run — each run leaves its own dated artefact rather than updating a single document in place. ### IT Glue document - **Connector**: Conduit (`itglue` vendor connection). - **permitted_tools**: `itglue__search_documents`, `itglue__create_document`, `itglue__update_document_section`, `itglue__publish_document`. - **Write snippet**: search for an existing document named `<report name>` in the target IT Glue org; if found, update its section, else create it; then call `itglue__publish_document` — section edits are invisible to a