chatwork-automation
Use Cautionnpx machina-cli add skill ComposioHQ/awesome-claude-skills/chatwork-automation --openclawChatwork Automation via Rube MCP
Automate Chatwork operations through Composio's Chatwork toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/chatwork
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Chatwork connection via
RUBE_MANAGE_CONNECTIONSwith toolkitchatwork - Always call
RUBE_SEARCH_TOOLSfirst to get current tool schemas
Setup
Get Rube MCP: Add https://rube.app/mcp as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
- Verify Rube MCP is available by confirming
RUBE_SEARCH_TOOLSresponds - Call
RUBE_MANAGE_CONNECTIONSwith toolkitchatwork - If connection is not ACTIVE, follow the returned auth link to complete setup
- Confirm connection status shows ACTIVE before running any workflows
Tool Discovery
Always discover available tools before executing workflows:
RUBE_SEARCH_TOOLS
queries: [{use_case: "Chatwork operations", known_fields: ""}]
session: {generate_id: true}
This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls.
Core Workflow Pattern
Step 1: Discover Available Tools
RUBE_SEARCH_TOOLS
queries: [{use_case: "your specific Chatwork task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["chatwork"]
session_id: "your_session_id"
Step 3: Execute Tools
RUBE_MULTI_EXECUTE_TOOL
tools: [{
tool_slug: "TOOL_SLUG_FROM_SEARCH",
arguments: {/* schema-compliant args from search results */}
}]
memory: {}
session_id: "your_session_id"
Known Pitfalls
- Always search first: Tool schemas change. Never hardcode tool slugs or arguments without calling
RUBE_SEARCH_TOOLS - Check connection: Verify
RUBE_MANAGE_CONNECTIONSshows ACTIVE status before executing tools - Schema compliance: Use exact field names and types from the search results
- Memory parameter: Always include
memoryinRUBE_MULTI_EXECUTE_TOOLcalls, even if empty ({}) - Session reuse: Reuse session IDs within a workflow. Generate new ones for new workflows
- Pagination: Check responses for pagination tokens and continue fetching until complete
Quick Reference
| Operation | Approach |
|---|---|
| Find tools | RUBE_SEARCH_TOOLS with Chatwork-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit chatwork |
| Execute | RUBE_MULTI_EXECUTE_TOOL with discovered tool slugs |
| Bulk ops | RUBE_REMOTE_WORKBENCH with run_composio_tool() |
| Full schema | RUBE_GET_TOOL_SCHEMAS for tools with schemaRef |
Powered by Composio
Source
git clone https://github.com/ComposioHQ/awesome-claude-skills/blob/master/composio-skills/chatwork-automation/SKILL.mdView on GitHub Overview
Automate Chatwork operations through Composio's Chatwork toolkit via Rube MCP. This skill standardizes discovering current tool schemas, establishing a Chatwork connection, and executing toolkit actions using RUBE_SEARCH_TOOLS, RUBE_MANAGE_CONNECTIONS, and RUBE_MULTI_EXECUTE_TOOL.
How This Skill Works
First, fetch current tool slugs and input schemas with RUBE_SEARCH_TOOLS. Then ensure an ACTIVE connection for the chatwork toolkit using RUBE_MANAGE_CONNECTIONS. Finally, execute the discovered tools with RUBE_MULTI_EXECUTE_TOOL, providing exact field names, a memory payload, and the session_id from the workflow.
When to Use It
- You need to automate recurring Chatwork tasks (e.g., messages or task creation) and want up-to-date tool schemas.
- Integrating Chatwork workflows into a larger automation and you must verify tool availability before execution.
- Setting up a new Chatwork operation and you should discover available tools before coding.
- Debugging a Chatwork workflow and you need to verify tool schemas, connections, and session handling.
- Performing bulk Chatwork actions that require multiple tools via RUBE_MULTI_EXECUTE_TOOL with proper memory handling.
Quick Start
- Step 1: Get Rube MCP: Add https://rube.app/mcp as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
- Step 2: Verify availability: Run RUBE_SEARCH_TOOLS and confirm it returns Chatwork tool slugs and schemas.
- Step 3: Connect and run: Call RUBE_MANAGE_CONNECTIONS with toolkits: ["chatwork"] and ensure status ACTIVE before executing workflows.
Best Practices
- Always call RUBE_SEARCH_TOOLS before executing workflows to get current tool schemas.
- Verify RUBE_MANAGE_CONNECTIONS reports ACTIVE status prior to tool execution.
- Use exact field names and types from the tool schemas; avoid hardcoded slugs.
- Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty.
- Reuse session IDs within a workflow and watch for pagination tokens during discovery.
Example Use Cases
- Automate daily status updates to a Chatwork room.
- Create and assign tasks in Chatwork from a project trigger.
- Sync Chatwork task statuses with an external workflow.
- Send bulk Chatwork messages to teammates on events.
- Run a chained sequence of tools discovered via RUBE_SEARCH_TOOLS for a single workflow.
