Skip to main content
NEW · APP STORE Now on iOS · macOS · iPad Android & Windows soon GET IT
Prompts Bitwarden Automation via Rube MCP

agent tool_use skill risk: high

Bitwarden Automation via Rube MCP

Instructs the model to automate Bitwarden operations through Composio's Bitwarden toolkit via Rube MCP by first calling RUBE_SEARCH_TOOLS, verifying ACTIVE connection status with R…

  • Policy sensitive
  • Human review
  • External action: high

SKILL 1 file

SKILL.md
---
name: bitwarden-automation
description: "Automate Bitwarden tasks via Rube MCP (Composio). Always search tools first for current schemas."
---
# Bitwarden Automation via Rube MCP

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

**Toolkit docs**: [composio.dev/toolkits/bitwarden](https://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.

1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `bitwarden`
3. If connection is not ACTIVE, follow the returned auth link to complete setup
4. 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](https://composio.dev)*

REQUIRED CONTEXT

  • RUBE_SEARCH_TOOLS availability
  • active Bitwarden connection via RUBE_MANAGE_CONNECTIONS

TOOLS REQUIRED

  • RUBE_SEARCH_TOOLS
  • RUBE_MANAGE_CONNECTIONS
  • RUBE_MULTI_EXECUTE_TOOL
  • RUBE_GET_TOOL_SCHEMAS
  • RUBE_REMOTE_WORKBENCH

ROLES & RULES

  1. Always search tools first for current schemas
  2. Always call RUBE_SEARCH_TOOLS first to get current tool schemas
  3. Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds
  4. Call RUBE_MANAGE_CONNECTIONS with toolkit bitwarden
  5. Confirm connection status shows ACTIVE before running any workflows
  6. Always discover available tools before executing workflows
  7. Never hardcode tool slugs or arguments without calling RUBE_SEARCH_TOOLS
  8. Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status before executing tools
  9. Use exact field names and types from the search results
  10. Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty
  11. Reuse session IDs within a workflow
  12. Generate new session IDs for new workflows
  13. Check responses for pagination tokens and continue fetching until complete

EXPECTED OUTPUT

Format
markdown
Constraints
  • always search tools first
  • verify active connection before execution
  • reuse session ids

SUCCESS CRITERIA

  • Always search tools first
  • Verify active Bitwarden connection before execution
  • Use schema-compliant arguments from search results
  • Reuse session IDs within workflows

FAILURE MODES

  • Hardcoding tool slugs or arguments without searching first
  • Executing tools without confirming ACTIVE connection status
  • Omitting the memory parameter in execute calls
  • Failing to handle pagination in responses

EXAMPLES

Includes multiple example RUBE_* tool calls showing discovery, connection check, and execution patterns with specific argument structures.

CAVEATS

Dependencies
  • Rube MCP connection (RUBE_SEARCH_TOOLS available)
  • Active Bitwarden connection via RUBE_MANAGE_CONNECTIONS
Missing context
  • Target client or environment (e.g., Claude Desktop, Cursor) for MCP configuration
  • Example concrete Bitwarden tasks with expected outputs
Ambiguities
  • The exact syntax/format for calling the RUBE_* functions is shown in a pseudo-code style without specifying the actual invocation method (e.g., JSON-RPC, function calling API).

QUALITY

OVERALL
0.79
CLARITY
0.82
SPECIFICITY
0.78
REUSABILITY
0.75
COMPLETENESS
0.80

IMPROVEMENT SUGGESTIONS

  • Add a single concrete end-to-end example (e.g., 'list all items') with full function call syntax and sample response.

USAGE

Copy the prompt above and paste it into your AI of choice — Claude, ChatGPT, Gemini, or anywhere else you're working. Replace any placeholder sections with your own context, then ask for the output.

MORE FOR AGENT