$ ~/registry/skill/composiohq-composio-skills-chatwork-automation

SKILL

chatwork-automation

Name: chatwork-automation
Author: Composio

Automate Chatwork messages, tasks, and team workflows through Rube MCP.

Stars

★ 67,763

Source

GitHub

Updated

2026-07-15

// securityCaution

Prompt only, no code
Open source
Community-trusted· 64.7k

Summary

Overall this is a prompt-only skill with open-source provenance and relatively strong community adoption, so baseline risk is low. The main caution is that it relies on Rube MCP/Composio for external tool calls, which introduces connection authorization and data egress during actual use.

CredentialsLow risk

No additional API keys or tokens are required in the materials; it only mentions standard Chatwork connection authorization via RUBE_MANAGE_CONNECTIONS, with no credential-abuse red flags.

Network egressCaution

The skill explicitly communicates with Chatwork/Composio tools through Rube MCP and requires tool discovery before execution; this means task data is sent to declared external services, which is ordinary egress rather than suspicious endpoints.

Code executionCaution

The material is prompt-only with no evidence of spawning local processes or arbitrary code execution; however, it can trigger MCP tool execution workflows, which is normal for tool-based automation.

Data accessCaution

The capability is focused on Chatwork operations and may read/write Chatwork conversations and related business data; there is no description of excessive access to local files or system-wide resources beyond this scope.

Supply chainCaution

The source is a GitHub open-source repository with high community stars, which lowers supply-chain uncertainty; however, the license is undeclared, maintenance status is unknown, and execution depends on the Rube/Composio ecosystem, so caution is still warranted.

Recommendations

Enable it only when Chatwork automation is needed, and minimize the connection scope.
Verify the authorization page and tool list returned by Rube/Composio to avoid granting unnecessary permissions.
Review the tool schema and target endpoints before execution to reduce misuse or prompt-injection risk.

Audited by: gpt-5.4 · 2026-06-17

// install

Copy the install command and let the AI configure it · recommended for beginners

Please install the "chatwork-automation" skill from askskill:
1. Download https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/composio-skills/chatwork-automation/SKILL.md
2. Save it as ~/.claude/skills/chatwork-automation/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// docs

Chatwork 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_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.

Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds
Call RUBE_MANAGE_CONNECTIONS with toolkit chatwork
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_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

Automate Missive email and collaboration tasks through Rube MCP workflows.

ComposioGet→

$ loading_