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

SKILL

parma-automation

Name: parma-automation
Author: Composio

Automate Parma tasks via Rube MCP after checking current tool schemas first.

Stars

★ 67,763

Source

GitHub

Updated

2026-07-15

// securityCaution

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

Summary

This skill is primarily a prompt-style wrapper and does not itself require local secrets or direct code execution. However, it is designed around external Rube MCP/Composio services and a subsequent Parma connection, so operations and related data are likely handled through a remote toolchain; overall this is low-to-moderate risk with caution warranted.

CredentialsCaution

The material states the skill itself needs 'no API keys', but it requires establishing a `parma` connection via `RUBE_MANAGE_CONNECTIONS` and following an auth link. This means credentials are mainly handled in the external Rube/Parma connection flow. There is no clear request for local sensitive environment variables, but third-party remote account authorization and session handling still introduce credential exposure and misuse considerations.

Network egressCaution

Although the top-level metadata says there are no remote endpoints, the README explicitly instructs users to add `https://rube.app/mcp` as an MCP server and references the Composio toolchain. Therefore, queries, parameters, session data, and business data may be sent to Rube/Composio and onward through the Parma integration path. The endpoint and purpose are disclosed in the material, so this is declared remote connectivity rather than a hidden egress red flag.

Code executionLow risk

Based on the provided material, this is a prompt-only skill document that mainly instructs use of existing MCP tools such as `RUBE_SEARCH_TOOLS` and `RUBE_MULTI_EXECUTE_TOOL`. It does not describe directly spawning local processes, running shell commands, installing dependencies, or requesting system-level execution privileges.

Data accessCaution

The skill itself does not claim direct access to local files or broad host resources, but it performs Parma operations through remote MCP tools and supports session reuse, memory parameters, and bulk execution. As a result, user inputs, task arguments, and related business data may be processed by external services. There is no clear sign of excessive local authorization beyond the stated purpose.

Supply chainLow risk

The source is a GitHub open-source repository with strong community adoption (64.7k stars), both of which are meaningful risk-reducing signals. The material itself is a skill description text, so it is relatively auditable. Remaining caveats are the unspecified license, unknown maintenance status, and the fact that runtime security also depends on the external Rube MCP/Composio services.

Recommendations

Enable it only after you trust the Rube MCP, Composio, and Parma integration chain, and review their privacy and data-handling terms.
Use least-privilege authorization when connecting a Parma account, avoiding unnecessary data scopes or admin capabilities.
Inspect the schemas returned by `RUBE_SEARCH_TOOLS` before execution to ensure no sensitive or out-of-scope parameters are being sent.
Validate in a test or low-sensitivity environment first, and avoid handling highly sensitive business data until remote data flows are assessed.

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

// download

Download SKILL.mdInstall manifest ↗

// docs

Parma Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/parma

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["parma"]
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 Parma-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `parma`
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

Automate Retailed workflows via Rube MCP after checking current tool schemas.

ComposioGet→

$ loading_