bitwarden-automation

by ComposioHQ

bitwarden-automation helps agents automate Bitwarden tasks through Composio Rube MCP, with required tool discovery, Bitwarden connection checks, and safer Access Control workflows.

Stars67.4k

Favorites0

Comments0

AddedJul 11, 2026

CategoryAccess Control

Install Command

npx skills add ComposioHQ/awesome-claude-skills --skill bitwarden-automation

Curation Score

This skill scores 66/100, which means it is acceptable for directory listing but should be presented as a lightweight connector-oriented skill rather than a complete Bitwarden automation playbook. Directory users get enough evidence to understand when to use it—Bitwarden operations via Rube MCP—and how to start, but they should expect to rely on live tool discovery and Rube responses for the actual schemas and operation details.

66/100

Strengths

Valid skill frontmatter with a clear trigger: automate Bitwarden tasks through Composio's Bitwarden toolkit via Rube MCP.
Prerequisites and setup steps identify the needed MCP server, connection check, and requirement to call RUBE_SEARCH_TOOLS first for current schemas.
Includes a reusable core workflow pattern for discovering tools and checking the Bitwarden connection before execution.

Cautions

Execution depends on an external Rube MCP setup and an active Bitwarden connection; the skill itself provides no scripts or bundled tooling.
Workflow guidance is mostly discovery/setup oriented, with limited concrete Bitwarden task examples or edge-case handling.

MCP MCP Tools Password Credentials Secrets

Overview

Overview of bitwarden-automation skill

What bitwarden-automation does

bitwarden-automation is a Claude skill for automating Bitwarden operations through Composio’s Rube MCP toolkit. Instead of asking an agent to guess Bitwarden API shapes, the skill directs it to discover the current Rube tools first, verify the Bitwarden connection, then execute vault-related workflows using live schemas.

Best fit for Access Control workflows

The bitwarden-automation skill is most useful when you want an AI agent to help with repeatable password-manager and Access Control tasks: checking vault connection status, preparing Bitwarden actions, retrieving tool schemas, or coordinating operations that depend on Bitwarden being authenticated through Rube. It fits teams that already use MCP-enabled clients and want a safer pattern than ad hoc prompts for credential-management workflows.

Key differentiator: tool discovery before action

The strongest design choice is the mandatory RUBE_SEARCH_TOOLS step. Bitwarden tooling can change, and this skill tells the agent not to rely on stale assumptions. That matters for install decisions: the skill is lightweight, but it reduces schema guesswork by making discovery and connection checks part of the workflow.

Adoption requirements to check first

Before installing or relying on bitwarden-automation, confirm that your client supports MCP servers, that Rube MCP is configured, and that a Bitwarden connection can be activated via RUBE_MANAGE_CONNECTIONS or the available Rube connection-management tool. If your environment cannot expose Rube MCP tools to the agent, this skill will not add much beyond a written checklist.

How to Use bitwarden-automation skill

bitwarden-automation install context

Install the skill from the Composio skill collection in the same way you install other Claude skills from the repository, for example:

npx skills add ComposioHQ/awesome-claude-skills --skill bitwarden-automation

Then add Rube MCP as an MCP server in your client configuration using:

https://rube.app/mcp

The source skill states that no separate API key is needed for the MCP endpoint, but you still need an active Bitwarden connection inside Rube before workflows can run.

First setup checks before running actions

A good bitwarden-automation usage flow starts with setup validation, not with the final vault action. Ask the agent to:

Confirm RUBE_SEARCH_TOOLS is available.
Search for Bitwarden-related tools and schemas.
Use the Rube connection-management tool for toolkit bitwarden.
If the connection is not active, return the auth link and wait for completion.
Re-check that the Bitwarden connection is ACTIVE.

This prevents a common failure mode: the model drafting an operation that cannot run because the MCP server or Bitwarden authorization is missing.

Prompt pattern for better results

A weak prompt is: “Use Bitwarden to update access.” It omits the target operation, allowed scope, and confirmation rules.

A stronger prompt for this bitwarden-automation guide is:

Use the bitwarden-automation skill. First call RUBE_SEARCH_TOOLS for the specific Bitwarden task and inspect the current schema. Then verify the Bitwarden connection is active through Rube. I need help with [task] for [vault item / collection / credential type]. Do not perform destructive or broad changes without showing the planned tool call and waiting for confirmation. If required fields are missing, ask me before executing.

This works better because it gives the agent permission to discover tools, defines the business goal, and sets a safety boundary before touching Access Control data.

Repository file to read first

This skill has a compact repository footprint: the main file to inspect is SKILL.md under composio-skills/bitwarden-automation. Read it for prerequisites, setup, the required tool-discovery pattern, and the core workflow. There are no extra scripts, references, or resource folders in the provided tree, so most implementation detail comes from Rube’s live tool schemas and the Composio Bitwarden toolkit documentation.

bitwarden-automation skill FAQ

Is bitwarden-automation enough without Rube MCP?

No. The skill depends on Rube MCP and expects tools such as RUBE_SEARCH_TOOLS and connection management to be available. Without MCP access, the instructions can still guide a human process, but the agent cannot execute the intended Bitwarden automation workflow.

How is this different from an ordinary Bitwarden prompt?

A generic prompt may ask the model to infer API names or invent fields. bitwarden-automation explicitly requires tool discovery first, then connection validation, then execution using current schemas. That makes it better for sensitive Access Control work where incorrect assumptions can cause failed actions or unsafe changes.

Is the skill beginner-friendly?

It is beginner-friendly for users who already know how to add an MCP server and authorize a SaaS connection. It is not a one-click Bitwarden tutorial. Beginners should start by confirming the Rube MCP endpoint works, then ask the agent to explain each discovered Bitwarden tool before executing any operation.

When should I not use bitwarden-automation?

Do not use it for offline vault editing, direct Bitwarden CLI workflows, or environments where an AI agent must not interact with credential-management systems. Also avoid it when your task requires undocumented Bitwarden behavior that is not exposed through the current Composio/Rube toolkit.

How to Improve bitwarden-automation skill

Improve bitwarden-automation prompts with scope

The biggest quality gain comes from precise scope. Include the target item type, collection, user or team context, whether the action is read-only or mutating, and what must be confirmed before execution. For example, “list candidate tools and prepare the update, but do not run it” is safer than “fix Bitwarden.”

Add confirmation gates for sensitive actions

For Access Control workflows, require the agent to separate planning from execution. A strong workflow is: discover tools, summarize the selected tool and required fields, show the proposed inputs, ask for approval, then run the call. This reduces accidental broad changes and makes audit review easier.

Watch for tool-name and schema drift

The source skill’s caution to always search tools first is not optional. If a prompt includes hard-coded tool names or old input fields, ask the agent to discard them and re-run RUBE_SEARCH_TOOLS for the exact use case. Treat live schema discovery as the source of truth.

Iterate after the first output

If the first result is too broad, revise with constraints such as “read-only,” “single vault item,” “no credential value exposure,” or “return only the required fields before execution.” If it fails, provide the exact connection status, Rube error, and discovered tool schema so the agent can adjust the next call instead of guessing.

Ratings & Reviews

No ratings yet

Share your review

0/10000

Latest reviews

Saving...

more skill

azure-identity-py

by microsoft

azure-identity-py helps set up Azure authentication in Python with Microsoft Entra ID. Use it to choose DefaultAzureCredential, managed identity, or service principal auth, configure environment variables, and troubleshoot access control and credential chain issues. Install guidance, usage patterns, and practical setup notes are based on the repo skill file.

Access Control

Favorites 0GitHub 2.2k

django-security

by affaan-m

django-security is a practical guide for hardening Django apps with authentication, authorization, CSRF, XSS, SQL injection prevention, secure cookies, and production settings. It helps developers and reviewers run a focused Security Audit, quickly spot risky config, and apply concrete fixes before deployment.

Security Audit

Favorites 0GitHub 156.1k

detecting-anomalous-authentication-patterns

by mukul975

detecting-anomalous-authentication-patterns helps analyze authentication logs for impossible travel, brute force, password spraying, credential stuffing, and compromised-account activity. Built for Security Audit, SOC, IAM, and incident response workflows with baseline-aware detection and evidence-backed sign-in analysis.

Security Audit

Favorites 0GitHub 0

auditing-kubernetes-cluster-rbac

by mukul975

auditing-kubernetes-cluster-rbac helps audit Kubernetes RBAC for overbroad roles, risky bindings, secret access, and privilege escalation paths. It is built for security audit workflows across EKS, GKE, AKS, and self-managed clusters, with practical guidance for kubectl, rbac-tool, KubiScan, and Kubeaudit.

Security Audit

Favorites 0GitHub 0

auditing-gcp-iam-permissions

by mukul975

auditing-gcp-iam-permissions helps review Google Cloud IAM access for risky bindings, primitive roles, public access, service account exposure, and cross-project paths. This access-control audit skill is built for evidence-driven reviews with gcloud, Cloud Asset, IAM Recommender, and Policy Analyzer.

Access Control

Favorites 0GitHub 0

auditing-aws-s3-bucket-permissions

by mukul975

The auditing-aws-s3-bucket-permissions skill helps you audit AWS S3 buckets for public exposure, overly permissive ACLs, weak bucket policies, and missing encryption. Built for Security Audit workflows, it supports a repeatable least-privilege review with AWS CLI and boto3-oriented guidance, plus practical install and usage notes.

Security Audit

Favorites 0GitHub 0

ms365-tenant-manager

by alirezarezvani

ms365-tenant-manager helps Global Administrators plan Microsoft 365 tenant setup, security audits, bulk user provisioning, license management, Conditional Access, Exchange Online, Teams, and compliance workflows with PowerShell templates, sample inputs, scripts, and troubleshooting references.

Internal Operations

Favorites 0GitHub 22.1k

configuring-microsegmentation-for-zero-trust

by mukul975

The configuring-microsegmentation-for-zero-trust skill helps design and validate least-privilege workload-to-workload policies for zero trust environments. Use this guide to segment applications, reduce lateral movement, and turn observed traffic into enforceable rules for Security Audit and operations.

Security Audit

Favorites 0GitHub 0

security-scan

by affaan-m

The security-scan skill audits your Claude Code .claude/ configuration for secrets, risky MCP setup, injection-prone instructions, dangerous bypass flags, and weak agent or hook definitions using AgentShield. Use it for repeatable security checks before committing or onboarding.

Security Audit

Favorites 0GitHub 156.3k

laravel-security

by affaan-m

The laravel-security skill is a practical Laravel security checklist for authn/authz, validation, CSRF, mass assignment, file uploads, secrets, rate limiting, and secure deployment. Use it for audits, feature reviews, and hardening work in Laravel apps.

Security Audit

Favorites 0GitHub 156.2k

git-guardrails-claude-code

by mattpocock

git-guardrails-claude-code adds a PreToolUse hook to block dangerous git commands before Claude Code runs them. Install it to prevent destructive pushes, hard resets, forced cleans, and branch deletes, with scoped control for this project or all projects. Useful when you need git-guardrails-claude-code for Access Control boundaries in Claude Code.

Access Control

Favorites 0GitHub 66k

k8s-security-policies

by wshobson

k8s-security-policies helps teams draft Kubernetes NetworkPolicy, Pod Security Standards labels, and RBAC patterns using repo-backed templates and references for hardening and audit-ready rollout planning.

Security Audit

Favorites 0GitHub 32.6k

auth-implementation-patterns

by wshobson

auth-implementation-patterns is a practical skill for designing and implementing authentication and authorization patterns, including sessions, JWT, OAuth2/OIDC, RBAC, and access control checks for APIs and apps.

Access Control

Favorites 0GitHub 32.6k

security-and-hardening

by addyosmani

The security-and-hardening skill helps harden application code before release. Use it for user input, auth, sessions, sensitive data, file uploads, webhooks, and external services, with concrete checks like input validation, parameterized queries, output encoding, secure cookies, HTTPS, and secrets handling.

Security Audit

Favorites 0GitHub 18.7k

exploiting-kerberoasting-with-impacket

by mukul975

exploiting-kerberoasting-with-impacket helps authorized testers plan Kerberoasting with Impacket GetUserSPNs.py, from SPN enumeration to TGS ticket extraction, offline cracking, and detection-aware reporting. Use this exploiting-kerberoasting-with-impacket guide for penetration testing workflows with clear install and usage context.

Penetration Testing

Favorites 0GitHub 6.2k

exploiting-idor-vulnerabilities

by mukul975

exploiting-idor-vulnerabilities helps authorized security audits test Insecure Direct Object Reference flaws across APIs, web apps, and multi-tenant systems with cross-session checks, object mapping, and read/write verification.

Security Audit

Favorites 0GitHub 6.2k