How do I ensure I’m using current tool schemas?

Always call RUBE_SEARCH_TOOLS before executing; it returns tool slugs, input schemas, and execution plans.

What if the Perplexityai connection isn’t ACTIVE?

Use RUBE_MANAGE_CONNECTIONS with the perplexityai toolkit to authenticate and verify ACTIVE status before running workflows.

Do I have to include memory for every tool execution?

Yes. Always include a memory object in RUBE_MULTI_EXECUTE_TOOL calls, even if empty, to preserve context.

perplexityai-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Perplexityai Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/perplexityai

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["perplexityai"]
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 Perplexityai-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `perplexityai`
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/perplexityai-automation/SKILL.md

View on GitHub

Overview

Automate Perplexityai operations using Composio's toolkit through Rube MCP. This approach emphasizes discovering current tool schemas first and validating the Perplexityai connection before workflow execution.

How This Skill Works

Connect Rube MCP, verify availability with RUBE_SEARCH_TOOLS, and link the perplexityai toolkit using RUBE_MANAGE_CONNECTIONS. Discover tools, then execute them via RUBE_MULTI_EXECUTE_TOOL, ensuring memory is included and sessions are reused when appropriate.

When to Use It

You need to run a recurring Perplexityai operation and want an automated workflow.
You must discover current Perplexityai tool schemas before execution to avoid hardcoding slugs.
You need to verify or re-establish the Perplexityai toolkit connection prior to running tools.
You intend to run multiple Perplexityai tools in sequence within a single session using memory context.
Tool schemas change or pagination is involved, requiring re-fetching available tools and schemas.

Quick Start

Step 1: Add Rube MCP endpoint https://rube.app/mcp to your client configuration.
Step 2: Run RUBE_SEARCH_TOOLS to verify tool schemas and availability for perplexityai.
Step 3: Run RUBE_MANAGE_CONNECTIONS with toolkit perplexityai and, if ACTIVE, execute tools via RUBE_MULTI_EXECUTE_TOOL with memory.

Best Practices

Always call RUBE_SEARCH_TOOLS first to fetch current tool slugs and input schemas.
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing any tools.
Use exact field names and types from the discovered tool schemas; avoid hardcoding.
Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({}).
Reuse session IDs within a workflow; generate new IDs for separate workflows.

Example Use Cases

Schedule a daily Perplexityai report by discovering tools, validating the connection, and chaining a batch of tools via RUBE_MULTI_EXECUTE_TOOL.
Create a data enrichment pipeline that discovers tools, then executes multiple perplexityai operations in sequence with a single session.
Revalidate and reconnect the perplexityai toolkit after schema updates using RUBE_MANAGE_CONNECTIONS before running tasks.
Execute bulk perplexityai tasks with RUBE_REMOTE_WORKBENCH and run_composio_tool for scalable workflows.
Fetch all available Perplexityai tools with RUBE_SEARCH_TOOLS, log schemas, and adapt pipelines accordingly.

Frequently Asked Questions

Add this skill to your agents