What is the Prisma automation skill used for?

It automates Prisma tasks through Rube MCP and uses RUBE_SEARCH_TOOLS to fetch current tool schemas and RUBE_MULTI_EXECUTE_TOOL to run discovered tools.

What happens if tool schemas change?

Always re-run RUBE_SEARCH_TOOLS to fetch current tool slugs and schemas before executing; avoid hardcoding tool definitions.

prisma-automation

Scanned

npx machina-cli add skill ComposioHQ/awesome-claude-skills/prisma-automation --openclaw

Files (1)

SKILL.md

2.8 KB

Prisma Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/prisma

Prerequisites

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

Step 2: Check Connection

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

Source

git clone https://github.com/ComposioHQ/awesome-claude-skills/blob/master/composio-skills/prisma-automation/SKILL.mdView on GitHub

Overview

Automate Prisma operations through Composio’s Prisma toolkit via Rube MCP. Always search for current tool schemas before workflow execution to adapt to changes. This skill enables safe, schema-aware Prisma tasks with validated tool definitions.

How This Skill Works

Connect to Rube MCP and ensure an active Prisma connection using RUBE_MANAGE_CONNECTIONS with the prisma toolkit. Before any workflow, fetch available tools and their schemas with RUBE_SEARCH_TOOLS, then execute a discovered tool via RUBE_MULTI_EXECUTE_TOOL with the correct arguments and a memory payload.

When to Use It

Need to perform a Prisma operation using a tool discovered by RUBE_SEARCH_TOOLS to ensure current schemas.
Setting up or verifying a Prisma connection via RUBE_MANAGE_CONNECTIONS before running any Prisma workflow.
Running a discovered Prisma tool with exact schema fields and memory parameters after tool discovery.
Handling multi-step Prisma tasks that require executing multiple tools in sequence and managing sessions.
Reacting to schema changes by re-fetching tool schemas before executing to avoid hardcoding slugs or arguments.

Quick Start

Step 1: Add the Rube MCP endpoint and run RUBE_SEARCH_TOOLS to fetch current Prisma tool schemas.
Step 2: Establish or verify a Prisma connection with RUBE_MANAGE_CONNECTIONS; ensure status is ACTIVE.
Step 3: Run RUBE_MULTI_EXECUTE_TOOL using a discovered tool_slug and the required arguments, including memory, within a session.

Best Practices

Always call RUBE_SEARCH_TOOLS before any workflow to obtain current tool slugs and schemas.
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE for the Prisma toolkit before executing tools.
Use exact field names and types from the search results; avoid hardcoding tool definitions.
Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty (memory: {})
Reuse session IDs within a workflow and handle pagination tokens when discovering tools

Example Use Cases

Create a new user via a CREATE_USER tool discovered with RUBE_SEARCH_TOOLS, after confirming the Prisma connection is ACTIVE, then run with required fields and memory.
Update product pricing using an UPDATE_PRICE tool found by search; verify ACTIVE connection and pass exact schema fields as arguments.
List active sessions using a FIND_SESSIONS tool from discovery results; handle pagination tokens if returned.
Bulk delete old draft records with BULK_DELETE_DRAFTS tool discovered via search; include memory and reuse a session ID.
Migrate data between environments by executing MIGRATE_DATA tool discovered after a fresh RUBE_SEARCH_TOOLS call; re-fetch schemas if changes occur.

Frequently Asked Questions

Add this skill to your agents