What prerequisites are required?

Rube MCP must be connected with RUBE_SEARCH_TOOLS available, an active Bitwarden connection via RUBE_MANAGE_CONNECTIONS using the bitwarden toolkit, and you should always call RUBE_SEARCH_TOOLS first.

Why should I call RUBE_SEARCH_TOOLS first?

Tool schemas change over time. Always fetching current tool slugs and input schemas prevents hardcoding and ensures compatibility.

What is the memory parameter and why include it?

Memory must be included in every RUBE_MULTI_EXECUTE_TOOL call (even if empty) to preserve state across the execution and support complex workflows.

bitwarden-automation

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

Files (1)

SKILL.md

2.9 KB

Bitwarden Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/bitwarden

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Bitwarden operations through Composio's Bitwarden toolkit via Rube MCP. This skill guides you to discover current tool schemas with RUBE_SEARCH_TOOLS, connect the Bitwarden toolkit, and execute workflows using RUBE_MULTI_EXECUTE_TOOL.

How This Skill Works

Tool discovery is performed with RUBE_SEARCH_TOOLS to fetch available Bitwarden tool slugs and schemas. Next, verify and activate the Bitwarden connection using RUBE_MANAGE_CONNECTIONS with toolkit bitwarden and confirm ACTIVE. Finally, run the tool with RUBE_MULTI_EXECUTE_TOOL, always including memory and a session_id; remember to reuse sessions and avoid hardcoding slugs by referencing the discovered tools.

When to Use It

When you need to perform a Bitwarden operation and want to start by discovering all available tools with RUBE_SEARCH_TOOLS
When you must ensure the Bitwarden connection is active before running any workflow (RUBE_MANAGE_CONNECTIONS)
When executing a tool, ensuring you pass the correct arguments as per the discovered schema via the tool's input
When tool schemas change and hardcoding slugs would break your automation; re-run RUBE_SEARCH_TOOLS first
When performing bulk or chained Bitwarden tasks across multiple steps, reusing session_ids to expedite workflows

Quick Start

Step 1: Get Rube MCP: add https://rube.app/mcp as an MCP server
Step 2: Verify RUBE_SEARCH_TOOLS responds and call RUBE_MANAGE_CONNECTIONS with bitwarden toolkit
Step 3: Run a discovered tool with RUBE_MULTI_EXECUTE_TOOL using memory and a session_id

Best Practices

Always search first to fetch current tool schemas with RUBE_SEARCH_TOOLS
Check that RUBE_MANAGE_CONNECTIONS shows ACTIVE status before executing tools
Include memory in every RUBE_MULTI_EXECUTE_TOOL call, even if empty ({})
Reuse session IDs within a workflow to speed up operations
Do not hardcode tool slugs or input field names; rely on live schemas from RUBE_SEARCH_TOOLS

Example Use Cases

Discover Bitwarden tool slugs and schemas with RUBE_SEARCH_TOOLS, then execute a chosen tool via RUBE_MULTI_EXECUTE_TOOL
Establish the Bitwarden connection with RUBE_MANAGE_CONNECTIONS and confirm ACTIVE before running workflows
Perform a vault operation by calling a discovered tool slug with the exact fields from the schema
Always call RUBE_SEARCH_TOOLS again if tool availability or inputs are updated, avoid hardcoding
Include memory in the RUBE_MULTI_EXECUTE_TOOL call and reuse a session_id across steps

Frequently Asked Questions

Add this skill to your agents