Do I need API keys to use writer-automation?

No. Add the MCP endpoint; no API keys are required.

Why must I always search tools first?

Tool schemas change over time. Calling RUBE_SEARCH_TOOLS ensures you use current slugs and fields.

What should I include in memory during execution?

Include a memory object in RUBE_MULTI_EXECUTE_TOOL even if empty; memory helps maintain context across steps.

writer-automation

Scanned

npx machina-cli add skill ComposioHQ/awesome-claude-skills/writer-automation --openclaw

Files (1)

SKILL.md

2.8 KB

Writer Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/writer

Prerequisites

Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
Active Writer connection via RUBE_MANAGE_CONNECTIONS with toolkit writer
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 writer
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: "Writer 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 Writer task"}]
session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["writer"]
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 Writer-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `writer`
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/writer-automation/SKILL.mdView on GitHub

Overview

Automate routine Writer operations by orchestrating Composio's Writer toolkit through Rube MCP. Always fetch current tool schemas before execution to avoid hard-coded slugs and schemas. This enables reliable, scalable automation of writing workflows in your projects.

How This Skill Works

Discover available Writer tools with RUBE_SEARCH_TOOLS to obtain tool slugs, input schemas, and recommended execution plans. Verify an ACTIVE connection for the writer toolkit using RUBE_MANAGE_CONNECTIONS. Execute the chosen tool via RUBE_MULTI_EXECUTE_TOOL, supplying the discovered slug, exact arguments, a memory payload, and the session_id to maintain context.

When to Use It

Automating repetitive Writer tasks (drafts, outlines, edits) by calling current tools discovered via RUBE_SEARCH_TOOLS.
Onboarding new workflows where tool schemas change frequently, ensuring you always pull latest schemas.
Integrating Writer automation into CI/CD or deployment pipelines for consistent content generation checks.
Executing bulk or multi-tool writer operations across multiple sessions while reusing session IDs.
Debugging or validating integration by refreshing tool schemas and confirming an ACTIVE connection before execution.

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server in your client configuration.
Step 2: Run RUBE_SEARCH_TOOLS with use_case set to Writer operations to discover tools and schemas.
Step 3: Call RUBE_MANAGE_CONNECTIONS for toolkits: ["writer"] and, if ACTIVE, execute a tool with RUBE_MULTI_EXECUTE_TOOL using the discovered slug and a session.

Best Practices

Always run RUBE_SEARCH_TOOLS first to get up-to-date tool schemas.
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools.
Use the exact field names and types from the search results.
Include memory in every RUBE_MULTI_EXECUTE_TOOL call, even if empty.
Reuse session IDs for related workflows and handle pagination tokens when present.

Example Use Cases

Draft a blog post by executing a TOOL_SLUG_FROM_SEARCH discovered via RUBE_SEARCH_TOOLS, with a memory blob containing draft context.
Generate an article outline using a discovered writer tool slug and store outline context in memory.
Process a batch of product descriptions by reusing a writer session and executing multiple tools in sequence.
Run a bulk generation workflow with RUBE_REMOTE_WORKBENCH and run_composio_tool() to process many items.
Inspect and compare full tool schemas with RUBE_GET_TOOL_SCHEMAS to confirm integration readiness.

Frequently Asked Questions

Add this skill to your agents