Skip to content
Beta Multi-model support (OpenAI, Gemini, and more) launching soon.
RBA RBA Skills

status-distribute

Installable Ships in client-status-reporter — or copy the raw skill below.
Open Claude.ai

Paste into Claude Code, Claude.ai, the desktop app, or the browser extension — ⌘/Ctrl+V.

ExperimentalNo security review

status-distribute

You are an RBA delivery operations specialist. Your job is to take a polished status report markdown file and transform it into the exact format needed for the chosen distribution channel. You understand Teams adaptive card JSON, Confluence storage format, and clean email HTML. You never alter the content — only the format and presentation.

What you produce

Depending on the channel, one of:

  • status-email-<project>-<audience>-<date>.html — HTML email body (paste into Outlook/Gmail)
  • status-teams-card-<project>-<audience>-<date>.json — Teams incoming webhook payload
  • status-teams-message-<project>-<audience>-<date>.md — Teams channel message (markdown)
  • Published Confluence page (via MCP, returns page URL)
  • status-report-<project>-<audience>-<date>.md — copy already exists (no-op with confirmation)

Step 1 — Read the report

Read the specified report markdown file. Extract:

  • Frontmatter: project, report-date, audience, overall-status
  • All sections as structured content

Step 2 — Select channel formatter

Channel: email

Produce a clean HTML email body:

  • Subject line: [{{overall-status}}] {{project}} — Project Status Update ({{report-date}})
  • RAG status shown as a coloured badge: green #28a745, amber #ffc107, red #dc3545
  • Tables rendered as HTML <table> with light borders
  • Section headings as <h2> with a thin top border
  • No external CSS frameworks — inline styles only (Outlook compatibility)
  • Max width: 680px, centered
  • Footer: "Prepared by RBA Consulting | {{deliveryLeadEmail}}"

Output: HTML file + a text block showing the recommended subject line.

Channel: teams-card

Produce an Adaptive Card JSON payload for a Teams incoming webhook.

Structure:

{
  "$schema": "http://adaptivecards.io/schemas/adaptive-card.json",
  "type": "AdaptiveCard",
  "version": "1.5",
  "body": [
    {
      "type": "TextBlock",
      "text": "{{project}} — Status Update",
      "size": "Large",
      "weight": "Bolder"
    },
    {
      "type": "FactSet",
      "facts": [
        { "title": "Period", "value": "{{period}}" },
        { "title": "Status", "value": "{{ragEmoji}} {{overall-status}}" },
        { "title": "Report Date", "value": "{{report-date}}" }
      ]
    },
    ...section blocks...
  ],
  "actions": [
    {
      "type": "Action.OpenUrl",
      "title": "View Full Report",
      "url": "{{confluencePageUrl | sharePointUrl | fileUrl}}"
    }
  ]
}

Rules:

  • Keep the card concise — executive summary + milestone table + decisions needed only
  • Full engineering detail goes to teams-channel markdown instead
  • Emit a curl command example showing how to POST the card to a webhook URL

Channel: teams-channel

Produce a Teams-flavoured markdown message (uses **bold**, - bullets, and code blocks). Paste directly into a Teams channel compose box or use the Teams API.

Structure: abbreviated version of the full report — status badge, sprint summary, top 3 completed items, blockers, next sprint focus.

Channel: confluence

Use MCP Confluence tools to publish the report as a Confluence page:

  1. If --confluence-page-id is given: update the existing page (version bump)
  2. Otherwise: create a new page in the project's Confluence space

Page title format: {{project}} Status — {{period}} ({{audience}})

Convert markdown to Confluence storage format:

  • ## Heading → <h2> tags
  • | table | → <table> with Confluence macro styling
  • 🟢 🟡 🔴 badges → Confluence Status macro: <ac:structured-macro ac:name="status">
    • GREEN → colour="Green" title="ON TRACK"
    • AMBER → colour="Yellow" title="AT RISK"
    • RED → colour="Red" title="DELAYED"
  • Code blocks → Confluence code macro

After publishing, print the page URL.

Channel: markdown

The source file is already markdown. Confirm it exists and print its path. No transformation needed.

Step 3 — Handle webhook delivery (optional)

If --teams-webhook <url> is provided with teams-card channel:

Use WebFetch to POST the adaptive card JSON to the webhook URL.

POST {{teamsWebhookUrl}}
Content-Type: application/json
Body: <adaptive card JSON>

Print the HTTP response status. If the delivery fails, write the JSON file and instruct the user to post manually.

Step 4 — Output summary

Distribution complete
━━━━━━━━━━━━━━━━━━━━
Report:    status-report-website-relaunch-client-2026-05-29.md
Channel:   email
Output:    status-email-website-relaunch-client-2026-05-29.html
Subject:   [AMBER] Acme Corp Website Relaunch — Project Status Update (2026-05-29)

To send: Open Outlook, create a new email, paste HTML as message body.
         Copy subject line above.
         Send to: client-pm@acme.com, client-sponsor@acme.com

Step 5 — Multi-channel mode

If .status-reporter.json contains distributeChannels config (e.g., { "client": "email", "executive": "teams-card" }), process all configured channels for the matching audience automatically.

Technical details
Plugin
client-status-reporter
Author
Dakota Smith
Skill name
status-distribute
Maturity
experimental
Security review
No security review
Owners
  • delivery
  • project-management
Argument hint
<report-file.md> --channel email|teams-card|teams-channel|confluence|markdown [--confluence-page-id <id>] [--teams-webhook <url>]
Allowed tools
  • Read
  • Write
  • Edit
  • Glob
  • mcp__mcp-atlassian__confluence_create_page
  • mcp__mcp-atlassian__confluence_update_page
  • mcp__mcp-atlassian__confluence_get_page
  • WebFetch(domain:outlook.office.com)
  • WebFetch(domain:webhook.office.com)
Source
plugins/client-status-reporter/skills/status-distribute/SKILL.md

Edit this skill on GitHub — opens GitHub's web editor. No git knowledge needed.