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

SKILL

quaderno-automation

Name: quaderno-automation
Author: Composio

Automate Quaderno tax and billing workflows through Rube MCP integrations.

Stars

★ 67,763

Source

GitHub

Updated

2026-07-15

// securityCaution

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

Summary

This skill is an open-source, prompt-only wrapper that does not directly require local secrets and does not describe local code execution or file access, so its baseline risk is low. However, it is designed to route actions through remote Rube MCP/Composio and a Quaderno connection, so users should remain cautious about network egress, third-party connections, and supply-chain boundaries.

CredentialsCaution

The material says no API key is needed to add Rube MCP, but it also requires creating an ACTIVE `quaderno` connection via `RUBE_MANAGE_CONNECTIONS` and following an auth link. This implies real service credentials or OAuth-style authorization are involved in a third-party connection flow. The skill does not directly request secrets itself, but there is a normal credential-delegation risk when authorizing Quaderno access to an external platform.

Network egressCaution

The README explicitly requires adding the remote MCP endpoint `https://rube.app/mcp` and using Composio/Rube to search tools, manage connections, and execute Quaderno operations. Task arguments, session IDs, and potentially business data will be sent to that remote service. The endpoint is declared and functionally relevant, so this is normal tool egress rather than a red flag, but users should assume operational data leaves the local client.

Code executionLow risk

The system marks this skill as `prompt-only`, and the material does not describe starting local processes, running scripts, installing binaries, or invoking a system shell. It mainly instructs how to call remote MCP tools. Based on the provided facts, no local code-execution capability is evident.

Data accessCaution

The material does not claim direct local file read/write access, but it is intended to automate Quaderno operations and can invoke remote tools via `RUBE_MULTI_EXECUTE_TOOL` and `RUBE_REMOTE_WORKBENCH`, which typically means access to data the user authorizes in Quaderno. There is no sign of excessive local data permissions, but the third-party platform may handle authorized business data.

Supply chainLow risk

The source is an open GitHub repository, the system marks it as `open-source`, and community adoption is high (about 64.9k stars), all of which materially lower risk. The provided material appears to be descriptive skill content rather than an executable payload; although the license is unspecified and maintenance status is unknown, that alone is not enough to raise it to high risk.

Recommendations

Before authorizing the Quaderno connection, verify Rube/Composio's data-handling model and grant only the minimum permissions required.
Avoid sending unnecessary sensitive finance or customer data in tool arguments, and test workflows with a non-production account first.
Treat this skill as an entry point to remote service orchestration and confirm your organization allows data to transit through `rube.app`/Composio.
For stronger assurance, review the linked open-source repository and log external connection and tool-execution activity.

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 "quaderno-automation" skill from askskill:
1. Download https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/composio-skills/quaderno-automation/SKILL.md
2. Save it as ~/.claude/skills/quaderno-automation/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// docs

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

$ loading_