What is the core workflow of this skill?

It follows discover tools, verify connection, then execute tools using the discovered tool slugs.

Do I need API keys to use it?

No API keys are required. You add the MCP server and complete the Placekey connection via the toolkit.

What common pitfalls should I avoid?

Do not hardcode slugs or arguments. Always search tools first, ensure ACTIVE connections, include memory in calls, and handle pagination tokens.

placekey-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Placekey Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/placekey

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["placekey"]
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 Placekey-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `placekey`
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/placekey-automation/SKILL.mdView on GitHub

Overview

Automate Placekey operations using Composio's Placekey toolkit through Rube MCP. This guide helps you connect, discover up-to-date tool schemas, and execute Placekey workflows without hardcoding tool slugs.

How This Skill Works

First, discover available Placekey tools with RUBE_SEARCH_TOOLS to obtain current input schemas. Then establish and verify a Placekey connection using RUBE_MANAGE_CONNECTIONS and ensure it is ACTIVE. Finally, execute the discovered tool using RUBE_MULTI_EXECUTE_TOOL with the tool slug, proper arguments, a memory payload, and the current session_id.

When to Use It

Starting a Placekey automation and pulling the latest tool schemas.
Connecting to the Placekey toolkit and validating ACTIVE status before running workflows.
Running a Placekey operation with a discovered tool slug and schema.
Performing bulk Placekey tasks via remote bench or multi-tool execute.
Troubleshooting schema changes, pagination, or session handling during execution.

Quick Start

Step 1: Add the MCP server at https://rube.app/mcp in your client and verify access with RUBE_SEARCH_TOOLS.
Step 2: Connect to Placekey via RUBE_MANAGE_CONNECTIONS with the toolkit set to placekey and confirm ACTIVE.
Step 3: Discover tools with RUBE_SEARCH_TOOLS and execute a chosen tool with RUBE_MULTI_EXECUTE_TOOL, including memory and session_id.

Best Practices

Always call RUBE_SEARCH_TOOLS first to get current tool schemas.
Verify that RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools.
Use the exact field names and types from the search results; do not hardcode slugs or arguments.
Include a memory object in every RUBE_MULTI_EXECUTE_TOOL call, even if empty.
Reuse session IDs within a workflow and generate new IDs for new workflows; monitor pagination tokens.

Example Use Cases

Discover and run a Placekey operation after authenticating the Placekey toolkit via RUBE_MANAGE_CONNECTIONS.
Set up a new Placekey connection and confirm ACTIVE before starting an automation workflow.
Execute a specific Placekey tool using a discovered slug with the appropriate arguments.
Run multiple Placekey tasks in a single batch using RUBE_REMOTE_WORKBENCH to run composio tools.
Fetch the full tool schemas with RUBE_GET_TOOL_SCHEMAS and adapt workflows to updated schemas.

Frequently Asked Questions

Add this skill to your agents