What is the first thing to do before running any Quaderno workflows?

Always search for tools with RUBE_SEARCH_TOOLS to obtain current tool slugs and input schemas.

How do I verify the Quaderno connection is ready?

Use RUBE_MANAGE_CONNECTIONS with the toolkit quaderno and confirm the status is ACTIVE before executing tools.

Do I have to include a memory object in tool executions?

Yes. Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if it is empty ({}), to ensure state consistency.

quaderno-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Quaderno Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/quaderno

Prerequisites

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

Step 2: Check Connection

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

Overview

Automates Quaderno operations through Composio's Quaderno toolkit via Rube MCP. The workflow emphasizes discovering current tool schemas with RUBE_SEARCH_TOOLS before execution and ensuring an ACTIVE Quaderno connection. This avoids hardcoding tool slugs and keeps integrations up to date.

How This Skill Works

It uses a three-step pattern: discover tools with RUBE_SEARCH_TOOLS, confirm an ACTIVE quaderno connection via RUBE_MANAGE_CONNECTIONS, then execute tools with RUBE_MULTI_EXECUTE_TOOL using the provided schema arguments. Tool schemas are dynamic; you must pull the latest input definitions before calling execute.

When to Use It

When you need to automate a Quaderno operation (e.g., invoicing or compliance tasks) by first discovering the appropriate tool slug and input schema.
When tool schemas may change and you must fetch current slugs and arguments with RUBE_SEARCH_TOOLS before running anything.
When you must verify that the Quaderno connection is ACTIVE via RUBE_MANAGE_CONNECTIONS before executing workflows.
When you want to reuse a session_id across multiple Quaderno actions within a single workflow to optimize state management.
When performing bulk or batch Quaderno operations using RUBE_REMOTE_WORKBENCH or multiple tool executions in a single run.

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server in your client configuration.
Step 2: Run RUBE_SEARCH_TOOLS to fetch current Quaderno tool schemas and slugs.
Step 3: Run RUBE_MANAGE_CONNECTIONS to ensure quaderno is ACTIVE, then execute a tool with RUBE_MULTI_EXECUTE_TOOL using memory and the discovered slug.

Best Practices

Always call RUBE_SEARCH_TOOLS first to obtain current tool slugs and input schemas.
Verify the Quaderno connection status is ACTIVE with RUBE_MANAGE_CONNECTIONS before execution.
Use exact field names and types from the discovered schema; avoid hardcoding values.
Include memory in every RUBE_MULTI_EXECUTE_TOOL call, even if empty (memory: {}).
Reuse session IDs for related workflows and fetch new ones only for new workflows.

Example Use Cases

Discover a Quaderno tool slug from RUBE_SEARCH_TOOLS for creating an invoice and execute it with the required arguments returned by the search results.
Fetch a customer profile by using the tool slug provided by RUBE_SEARCH_TOOLS and pass customer_id as an argument.
Update Quaderno tax settings by running the discovered update_tax_settings tool with the new tax_rate value.
Execute a sequence of Quaderno actions in one session using RUBE_MULTI_EXECUTE_TOOL and the discovered tool slugs.
Perform a bulk set of Quaderno tasks via RUBE_REMOTE_WORKBENCH using run_composio_tool() on the discovered slugs, ensuring memory is provided.

Frequently Asked Questions

Add this skill to your agents