What is Rube MCP and how does this skill use it?

Rube MCP is a control plane that manages tool discovery, connections, and execution. This skill uses RUBE_SEARCH_TOOLS, RUBE_MANAGE_CONNECTIONS, and RUBE_MULTI_EXECUTE_TOOL to automate Screenshot Fyi tasks.

Do I need API keys to use MCP?

No API keys are required — you simply add the MCP endpoint (e.g., https://rube.app/mcp) to your client configuration.

What happens if tool schemas change?

Always fetch current schemas with RUBE_SEARCH_TOOLS before running a workflow to avoid hardcoding tool slugs or arguments.

screenshot-fyi-automation

Scanned

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

Files (1)

SKILL.md

3.0 KB

Screenshot Fyi Automation via Rube MCP

Automate Screenshot Fyi operations through Composio's Screenshot Fyi toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/screenshot_fyi

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["screenshot_fyi"]
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 Screenshot Fyi-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `screenshot_fyi`
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/screenshot-fyi-automation/SKILL.md

View on GitHub

Overview

This skill automates Screenshot Fyi operations through Composio's Screenshot Fyi toolkit using Rube MCP. It emphasizes discovering current tool schemas, managing the Screenshot Fyi connection, and executing tools safely in a repeatable workflow.

How This Skill Works

Technically, it uses RUBE_SEARCH_TOOLS to fetch up-to-date tool schemas, then RUBE_MANAGE_CONNECTIONS to connect the screenshot_fyi toolkit, and finally RUBE_MULTI_EXECUTE_TOOL to run the chosen tool with a memory payload. The approach prevents hardcoding tool slugs and ensures sessions are reused where appropriate.

When to Use It

Discover available Screenshot Fyi tools for a task using RUBE_SEARCH_TOOLS before executing any workflow.
Establish or verify an ACTIVE connection to the screenshot_fyi toolkit with RUBE_MANAGE_CONNECTIONS before running tools.
Execute a discovered tool with exact schema fields using RUBE_MULTI_EXECUTE_TOOL and a memory payload.
Reuse session IDs within a workflow and generate new ones for separate workflows to maintain context.
Re-fetch tool schemas before large runs to avoid using outdated slugs or arguments.

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server in your client and verify RUBE_SEARCH_TOOLS responds.
Step 2: Run RUBE_SEARCH_TOOLS to discover available Screenshot Fyi tools and pick a tool slug from the results.
Step 3: Run RUBE_MANAGE_CONNECTIONS for toolkit 'screenshot_fyi', then use RUBE_MULTI_EXECUTE_TOOL with the discovered slug and a memory payload.

Best Practices

Always call RUBE_SEARCH_TOOLS first to get current tool schemas.
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools.
Use exact field names and types from the search results.
Include memory in RUBE_MULTI_EXECUTE_TOOL calls (even if empty).
Reuse session IDs within a workflow and generate new ones for new workflows.

Example Use Cases

Schedule a daily Screenshot Fyi activity summary by discovering tools, connecting once, and executing the daily_report tool with a persistent session.
Run an on-demand check_screenshots task for a project to validate recent captures using a freshly discovered tool schema.
Process screenshots in bulk across five projects in a single session, reusing the session ID for continuity.
Reconnect and re-authenticate the screenshot_fyi toolkit after a credential rotation, then re-run a previously failing task.
Fetch updated tool schemas before a complex multi-step workflow to ensure compatibility and avoid stale slugs.

Frequently Asked Questions

Add this skill to your agents