lastpass-automation

Overview of lastpass-automation skill

What lastpass-automation does

lastpass-automation is a Claude skill for running LastPass-related workflows through Composio’s Rube MCP server. Instead of hard-coding a single LastPass API shape, the skill instructs the agent to discover the current available Rube tools first, confirm the LastPass connection, then execute the selected operation with the live schema returned by MCP.

Best fit for Access Control workflows

This lastpass-automation skill is most useful for teams that want an AI agent to help with Access Control operations such as finding vault items, checking available LastPass actions, preparing credential-management workflows, or coordinating repeatable administrative steps. It is not a standalone password manager client; it depends on Rube MCP and an active LastPass toolkit connection.

Key adoption requirement

The main differentiator is also the main requirement: tool discovery comes first. The upstream skill explicitly expects RUBE_SEARCH_TOOLS to be available and used before execution because Composio tool schemas can change. If your agent cannot call MCP tools, or your environment blocks Rube, this skill will not deliver much beyond ordinary prompt guidance.

What to inspect before installing

The repository path is composio-skills/lastpass-automation, and the practical source is SKILL.md. There are no companion scripts, rule packs, or reference folders in the current file tree, so install decisions should be based on whether your client supports Rube MCP and whether your LastPass connection can be authorized through RUBE_MANAGE_CONNECTIONS.

How to Use lastpass-automation skill

lastpass-automation install context

Install the skill from the Composio skills repository in the way your Claude/skills client supports. A common directory command is:

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

Then add Rube MCP as a server using:

https://rube.app/mcp

After installation, verify that the agent can call RUBE_SEARCH_TOOLS. Next, use RUBE_MANAGE_CONNECTIONS with toolkit lastpass and complete the returned authorization flow if the connection is not ACTIVE.

Inputs the skill needs

For reliable lastpass-automation usage, give the agent three things: the exact LastPass task, the intended scope, and any safety constraints. Weak input is: “Check LastPass.” Strong input is: “Use lastpass-automation for Access Control. Discover current LastPass tools, confirm the LastPass connection is active, then find whether there are tools for listing shared-folder membership. Do not change vault data; report the available tool names, required fields, and a safe execution plan first.”

This matters because the skill is built around dynamic tool discovery. Clear scope helps RUBE_SEARCH_TOOLS return relevant tool slugs and prevents the agent from jumping from read-only investigation into mutation.

Practical workflow to follow

A good lastpass-automation guide workflow is:

1. Read SKILL.md first; it contains the actual operating pattern.
2. Ask the agent to call RUBE_SEARCH_TOOLS for your specific use case, not a generic “LastPass operations” query.
3. Confirm LastPass connection status with RUBE_MANAGE_CONNECTIONS.
4. Review the returned tool schema, required fields, execution plan, and pitfalls.
5. Run read-only actions before write actions where possible.
6. For any change to credentials, sharing, folders, or access, require the agent to summarize the intended operation before execution.

Prompt pattern that works well

Use prompts that force discovery and confirmation:

“Use the lastpass-automation skill. First call RUBE_SEARCH_TOOLS for: ‘LastPass shared folder access review’. Then check the LastPass toolkit connection with RUBE_MANAGE_CONNECTIONS. If active, show me the current tool options, required parameters, and the safest read-only plan. Do not create, update, delete, or share anything unless I approve a second step.”

This style improves output quality because it aligns with the skill’s core workflow and gives the agent a stopping point before sensitive actions.

lastpass-automation skill FAQ

Is lastpass-automation only for admins?

Mostly, yes. It is best suited to users who are allowed to manage or audit LastPass data through Composio. Non-admin users can still use it for permitted account workflows, but many Access Control tasks may fail or return limited data if the connected LastPass account lacks privileges.

How is it better than a normal prompt?

A normal prompt can describe LastPass procedures, but it cannot discover live Composio tool schemas or call the Rube MCP tools. The lastpass-automation skill adds a concrete execution pattern: search tools first, check connection state, use returned schemas, then execute. That reduces guesswork when tool names or parameters change.

When should I not use it?

Do not use it if your environment cannot enable MCP, if LastPass authorization cannot be completed, or if your organization forbids AI-mediated access to password-vault operations. Also avoid using it for irreversible changes until you have tested read-only discovery and confirmed the exact tool schema returned in your session.

Is this beginner friendly?

It is beginner friendly for MCP users, but not for someone expecting a one-click LastPass integration. The skill assumes you understand that the agent will call external tools and that authorization, permissions, and approval gates matter. Beginners should start with read-only discovery prompts before attempting changes.

How to Improve lastpass-automation skill

Improve lastpass-automation prompts

Better prompts should name the operation, risk level, and approval boundary. Instead of “update LastPass access,” say: “Discover tools for updating LastPass shared-folder access. Report required fields and risks. Stop before making changes.” This gives the skill enough context to find relevant tools while preserving human control over sensitive Access Control actions.

Reduce common failure modes

The most common failures are skipping RUBE_SEARCH_TOOLS, assuming a stale schema, trying to run actions before the LastPass connection is ACTIVE, and giving vague targets such as “clean up vault.” Fix these by requiring the agent to display the discovered tool slug, input schema, and planned parameters before execution.

Iterate after the first output

After the first discovery result, refine with the actual tool names and fields returned by Rube. For example: “Using the discovered tool schema, prepare the request body for a read-only access review of shared folders. Leave unknown IDs blank and ask me for them.” This prevents fabricated parameters and turns the first output into a safer second-step plan.

What maintainers could add next

The skill would be stronger with example prompts for common LastPass tasks, explicit read-only versus write workflow templates, and cautions for credential, sharing, and deletion operations. A short troubleshooting section for inactive connections, missing Rube tools, and authorization failures would also make lastpass-automation install decisions easier for security-conscious teams.