home / skills / composiohq / awesome-claude-skills / chatwork-automation

chatwork-automation skill

safe

/chatwork-automation

This skill automates Chatwork tasks via Rube MCP, prioritizing current tool schemas and verified connections for reliable workflows.

npx playbooks add skill composiohq/awesome-claude-skills --skill chatwork-automation

Review the files below or copy the command above to add this skill to your agents.

Files (1)

SKILL.md

2.9 KB

---
name: chatwork-automation
description: "Automate Chatwork tasks via Rube MCP (Composio). Always search tools first for current schemas."
requires:
  mcp: [rube]
---

# Chatwork Automation via Rube MCP

Automate Chatwork operations through Composio's Chatwork toolkit via Rube MCP.

**Toolkit docs**: [composio.dev/toolkits/chatwork](https://composio.dev/toolkits/chatwork)

## Prerequisites

- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Chatwork connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `chatwork`
- Always call `RUBE_SEARCH_TOOLS` first 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.

1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `chatwork`
3. If connection is not ACTIVE, follow the returned auth link to complete setup
4. 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_CONNECTIONS` shows ACTIVE status before executing tools
- **Schema compliance**: Use exact field names and types from the search results
- **Memory parameter**: Always include `memory` in `RUBE_MULTI_EXECUTE_TOOL` calls, 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](https://composio.dev)*

Overview

This skill automates Chatwork tasks through Composio’s Chatwork toolkit using Rube MCP. It provides a reproducible pattern for discovering tools, confirming connections, and running Composio tools programmatically. The workflow emphasizes schema discovery and session management to avoid runtime errors.

How this skill works

The skill first queries RUBE_SEARCH_TOOLS to retrieve current tool slugs, input schemas, and recommended execution plans. It then verifies the Chatwork connection via RUBE_MANAGE_CONNECTIONS and runs operations with RUBE_MULTI_EXECUTE_TOOL or RUBE_REMOTE_WORKBENCH, always supplying memory and a session_id. Tool schemas and pagination tokens are respected to ensure reliable execution.

When to use it

Automate message posting, channel management, or user queries in Chatwork
Run bulk Chatwork operations that require orchestration across multiple tools
Integrate Chatwork actions into larger Claude or Composio workflows
When tool schemas may have changed and you need a discovery-first approach
When you need repeatable automation with explicit session and memory management

Best practices

Always call RUBE_SEARCH_TOOLS first — never hardcode tool slugs or argument shapes
Confirm Chatwork connection status via RUBE_MANAGE_CONNECTIONS and complete any auth flows before executing tools
Include an explicit memory object in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({})
Reuse session_id within a workflow and generate new session_ids for new workflows
Check responses for pagination tokens and fetch additional pages until complete
Use RUBE_GET_TOOL_SCHEMAS for full schema details when schemaRef is present

Example use cases

Post announcements to multiple Chatwork rooms in a single run by discovering the send-message tool and executing it for each room
Automate onboarding: create channels, add users, and post welcome messages using a multi-step RUBE_MULTI_EXECUTE_TOOL plan
Sync Chatwork channel membership to an external directory by paging through members and updating roles
Run scheduled bulk maintenance tasks via RUBE_REMOTE_WORKBENCH calling run_composio_tool() across multiple tool slugs
Query message history with pagination to build searchable archives or trigger alerts

FAQ

Do I need API keys to use Rube MCP?

No API keys are required. Add https://rube.app/mcp as an MCP server in your client configuration to connect.

What if a tool schema changes mid-workflow?

Always re-run RUBE_SEARCH_TOOLS before executing critical steps. If a schema changed, update arguments to match the returned field names and types before calling RUBE_MULTI_EXECUTE_TOOL.