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

SKILL

paradym-automation

Name: paradym-automation
Author: Composio

Automate Paradym tasks via Rube MCP with schema lookup first.

Stars

★ 67,763

Source

GitHub

Updated

2026-07-15

// securityCaution

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

Summary

This skill appears to be prompt/documentation-only and does not itself declare secrets, endpoints, or local execution. However, it is explicitly designed to drive remote Rube MCP/Composio connections and operate Paradym through external tooling, so the overall posture is low-to-moderate risk with caution mainly due to external toolchain dependency.

CredentialsCaution

The material says 'No API keys needed,' but it also requires establishing an ACTIVE Paradym connection via `RUBE_MANAGE_CONNECTIONS` and completing an auth link, which implies third-party account authorization or session credentials may still be involved. There is no indication that the skill itself collects or stores secrets.

Network egressCaution

The README explicitly requires adding the remote MCP endpoint `https://rube.app/mcp` and using Composio/Rube to search tools, manage connections, and execute Paradym operations. This means task inputs, session IDs, tool arguments, and potentially business data may transit through external services. The endpoint is declared, and no additional unknown exfiltration target is evident from the material.

Code executionLow risk

Based on the provided material, this skill is prompt-only and mainly provides workflow guidance and MCP call patterns. It does not declare any local process spawning, script execution, or system-level execution privileges for itself.

Data accessCaution

The skill itself does not declare direct local file or host-data access, but its purpose is to 'Automate Paradym operations' through external tools. Therefore, the effective data access scope depends on the authorized Paradym/Composio/Rube connection and carries the usual risk of reading or modifying remote business data.

Supply chainLow risk

The source is a GitHub open-source repository with strong community adoption (~64.9k stars), which materially lowers supply-chain risk. The material looks like skill documentation rather than an executable binary. Still, the missing license declaration and unknown maintenance status warrant verifying actual commits and upstream Rube/Composio documentation.

Recommendations

Enable it only after confirming trust in `rube.app`, Composio, and the Paradym integration chain, and review their privacy/data-handling terms.
Use a least-privilege account when connecting Paradym, limiting accessible data scope and environments.
Inspect the actual schemas returned by `RUBE_SEARCH_TOOLS` before execution to avoid invoking tools with broader-than-expected capabilities.
Require human confirmation and audit logging for sensitive write actions, and periodically review external connection status and granted permissions.

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

// download

Download SKILL.mdInstall manifest ↗

// docs

Paradym Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/paradym

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["paradym"]
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 Paradym-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `paradym`
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 Prisma tasks via Rube MCP with schema-first tool discovery.

ComposioGet→

$ loading_