send-group-message

Send assistant messages to a group via customer_service API with IMEI authorization.

22|3|Updated Apr 22, 2026
One-click install
npx skills add https://github.com/MadeAgents/TopoClaw --skill send-group-message
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: send-group-message
Source: https://github.com/MadeAgents/TopoClaw/tree/main/TopoClaw/topoclaw/skills/send-group-message
Command: npx skills add https://github.com/MadeAgents/TopoClaw --skill send-group-message

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires requests.

What problem does it solve?

This Skill solves the problem of quickly sending a message to a specific group on behalf of the user without manually operating the group chat interface.

Core Features & Use Cases

  • Targeted group delivery: Sends an assistant-branded message to a specific group using group_id.
  • Environment-driven inputs: Supports auto-filling TOPO_GROUP_ID, TOPO_GROUP_MESSAGE, and TOPO_GROUP_SENDER to reduce friction.
  • Configurable customer service endpoint: Uses TOPO_ACTIVE_CUSTOMER_SERVICE_URL / CUSTOMER_SERVICE_URL / VITE_MOBILE_AGENT_CUSTOMER_SERVICE_URL with fail-fast behavior when missing.
  • Structured response output: Returns success status, IMEI, group details, a content preview, sender identity, and the raw server response.

Quick Start

Ask TopoClaw to send your requested message text to the group identified by group_id, and make sure the skill has access to the current caller IMEI and a valid customer service URL.

Frequently Asked Questions about send-group-message

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I send an automated assistant message to a specific group via API?

To send an automated assistant message to a specific group via API, you provide the group_id, message content, and caller IMEI to a customer_service API endpoint. The Skill formats this into an API request and outputs a structured JSON result with success status and server response.

What environment variables need to be configured for group messaging automation?

Group messaging automation requires configuring a customer service base URL, such as TOPO_ACTIVE_CUSTOMER_SERVICE_URL, CUSTOMER_SERVICE_URL, or VITE_MOBILE_AGENT_CUSTOMER_SERVICE_URL. It also supports auto-filling TOPO_GROUP_ID, TOPO_GROUP_MESSAGE, and TOPO_GROUP_SENDER to reduce input friction.

Can I use group messaging requests for TopoClaw mobile and desktop workflows?

Yes, you can use group messaging requests for TopoClaw mobile and desktop workflows. The API request requires imei-based authorization to validate the caller and successfully post the assistant-mediated message to the target group.

What data is included in the structured JSON response after posting to a group?

The structured JSON response after posting to a group includes the success status, IMEI, group details, content preview, sender identity, and the raw server response. This provides complete visibility into the API request outcome.

Why does my group messaging API request fail during automation?

Your group messaging API request fails during automation if the customer service base URL is missing from the environment configuration. The Skill uses fail-fast behavior, meaning it will immediately halt if TOPO_ACTIVE_CUSTOMER_SERVICE_URL or equivalent variables are not set.

Do I need a specific sender identity to post announcements to a group chat?

You do not need a manually configured sender identity to post announcements to a group chat. The Skill supports auto-filling the TOPO_GROUP_SENDER variable and outputs the sender identity in the JSON response, branding the message as an assistant-mediated announcement.