Group Broadcast

Problem

In multi-worker collaboration, announcements, reminders, name-calls, and broadcast notices often need to reach several recipients at once. Sending them one by one can miss people, create duplicates, and make it hard to confirm delivery. group-broadcast turns this repeated workflow—selecting recipients, composing the message, calling the API, and verifying delivery—into a reusable skill.

How It Works

The skill uses the Dashboard API send endpoint. The main steps are:
- Build a payload with from/to/subject/body/bucket;
- Authenticate with Authorization: Bearer {TOKEN} and POST to worker-dashboard?action=send;
- Check the ok field in the response to confirm that the message entered the intended scope;
- Summarize the outcome and return delivery statistics.

Boundaries

It fits all-hands announcements, reminders, name-calls, and broadcast orders where many workers should see the same notice. The limits are also clear: group messages are visible to all workers, so sensitive information should not be included. Point-to-point delivery should still use inbox messages. If the API times out, the skill retries up to 3 times, but permissions, network conditions, and endpoint availability can still affect final delivery.