RUBE MCP is the Composio management plane that lets you search for Neuronwriter tool schemas, manage connections, and run tools.

Why always search first?

Tool schemas change; fetching them ensures you have valid tool slugs and argument names.

Memory carries session state for multi-tool workflows; pass memory even if empty to ensure end-to-end execution.

neuronwriter-automation

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

Files (1)

SKILL.md

2.9 KB

Neuronwriter Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/neuronwriter

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["neuronwriter"]
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 Neuronwriter-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `neuronwriter`
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/neuronwriter-automation/SKILL.md

View on GitHub

Overview

Automate Neuronwriter operations using Composio's Neuronwriter toolkit via Rube MCP. Always fetch current tool schemas before execution to avoid broken pipelines. This skill streamlines setup, discovery, and execution of Neuronwriter workflows.

How This Skill Works

Connect Rube MCP and verify the Neuronwriter connection via RUBE_MANAGE_CONNECTIONS. Use RUBE_SEARCH_TOOLS to fetch current tool schemas, then discover available tools and select a workflow. Finally execute the tool with RUBE_MULTI_EXECUTE_TOOL, including a memory payload and the active session_id.

When to Use It

When starting a Neuronwriter automation, to fetch up-to-date tool schemas before selecting tools.
When you need to establish or verify a Neuronwriter connection via Rube MCP.
When you want to discover available Neuronwriter tools for a specific use case.
When you have identified a tool and are ready to run it in a session.
When you need to handle tool schema changes, pagination tokens, or ensure memory is included.

Quick Start

Step 1: Configure Rube MCP by adding https://rube.app/mcp as an MCP server and verify RUBE_SEARCH_TOOLS.
Step 2: Manage connection with RUBE_MANAGE_CONNECTIONS for the neuronwriter toolkit and ensure status ACTIVE.
Step 3: Discover tools with RUBE_SEARCH_TOOLS, pick a tool slug, and execute it with RUBE_MULTI_EXECUTE_TOOL including memory and the session_id.

Best Practices

Always call RUBE_SEARCH_TOOLS first to get current schemas.
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before execution.
Use exact field names and types from the search results.
Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty.
Reuse session IDs within a workflow; generate new ones for new workflows.

Example Use Cases

Automate creating a Neuronwriter draft by discovering tools and executing the appropriate tool slug.
Bulk update multiple pages by discovering tools and looping RUBE_MULTI_EXECUTE_TOOL calls in a single session.
Reconnect after a Neuronwriter connection drop using RUBE_MANAGE_CONNECTIONS and RUBE_SEARCH_TOOLS.
Update Neuronwriter SEO details by using a discovered tool that accepts title, meta, and content fields.
Fetch all available Neuronwriter tools handling pagination tokens from RUBE_SEARCH_TOOLS.

Frequently Asked Questions

Add this skill to your agents