message-chunker
智能消息分段工具。自动将长消息拆分成多条发送,避免飞书API消息长度限制。当需要发送长消息(如汇报、方案、日志)时自动激活。
Install via CLI (Recommended)
clawhub install openclaw/skills/skills/as9530272755/message-chunkerWhat This Skill Does
The message-chunker is a critical infrastructure utility for the OpenClaw AI ecosystem designed to solve the persistent issue of message length restrictions on communication platforms like Feishu, Telegram, and Discord. When an AI generates long-form content—such as detailed project reports, comprehensive strategy proposals, or raw technical logs—it often hits character limits, resulting in incomplete transmissions or API errors. This skill intelligently intercept the output stream to partition content into valid, manageable chunks while preserving the logical structure of the text. By respecting internal document elements like headers, tables, and paragraph boundaries, it ensures that your communications remain professional, readable, and perfectly formatted across all supported messaging platforms.
Installation
To integrate this utility into your OpenClaw environment, execute the following command in your terminal or assistant console:
clawhub install openclaw/skills/skills/as9530272755/message-chunker
Once installed, you can configure the behavior (such as maxChunkSize or automatic continuation markers) by modifying the parameters within your TOOLS.md configuration file.
Use Cases
- Project Reporting: Automatically break down lengthy end-of-week status reports into structured, easy-to-read segments.
- Technical Documentation: Share extensive code snippets or long debugging logs without being cut off by character caps.
- Complex Planning: Deliver detailed business proposals that contain multiple chapters or large data tables without breaking the table formatting or interrupting reading flow.
- Collaborative Syncing: Ensure that deep-dive insights or research summaries are transmitted fully, even when they exceed the typical 4000-character limit.
Example Prompts
- "Draft a comprehensive project proposal for the Q3 migration, include a detailed timeline table, and ensure it is sent in full chunks."
- "Extract all error logs from the server response (approx 12,000 characters) and summarize the findings, splitting the response as needed."
- "Write a multi-part tutorial on setting up our development environment, utilizing the automatic chunker to keep the guide well-structured."
Tips & Limitations
- Config Optimization: Always set your
maxChunkSizeaccording to your primary platform's constraints (e.g., 1900 characters for Discord to ensure safety). - Manual Control: Use the
{{CHUNK}}marker to force a break exactly where you want a new message to begin. - Avoid Over-Splitting: The tool is smart, but try not to force breaks in the middle of lists or tables unless necessary, as it may affect the readability of the content for the recipient.
- Integrity: If you are sending tabular data, ensure the table remains within a single chunk, as the skill aims to preserve table integrity whenever possible to avoid parsing errors in the output.
Metadata
Not sure this is the right skill?
Describe what you want to build — we'll match you to the best skill from 16,000+ options.
Find the right skillPaste this into your clawhub.json to enable this plugin.
{
"plugins": {
"official-as9530272755-message-chunker": {
"enabled": true,
"auto_update": true
}
}
}