What is required to start using screenshotone-automation?

You need a connected Rube MCP, active Screenshotone connection via RUBE_MANAGE_CONNECTIONS, and to always call RUBE_SEARCH_TOOLS first to fetch current tool schemas.

How do I run a Screenshotone task safely?

Discover tools with RUBE_SEARCH_TOOLS, verify the connection is ACTIVE with RUBE_MANAGE_CONNECTIONS, then execute tools with RUBE_MULTI_EXECUTE_TOOL using the discovered tool_slug and proper arguments, including memory.

How should I handle tool schema changes?

Always search for updated schemas before running any tool. Do not hardcode slugs or arguments; rely on the exact field names and types returned by RUBE_SEARCH_TOOLS, and respect pagination if present.

screenshotone-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Screenshotone Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/screenshotone

Prerequisites

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

Step 2: Check Connection

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

View on GitHub

Overview

This skill automates Screenshotone operations through Composio's Rube MCP toolkit. It emphasizes discovering current tool schemas first, establishing an ACTIVE Screenshotone connection, and executing tools within a structured workflow to ensure up-to-date interfaces and reliable runs.

How This Skill Works

You first discover available tools and their input schemas using RUBE_SEARCH_TOOLS. Next, you verify and establish the Screenshotone connection with RUBE_MANAGE_CONNECTIONS, ensuring the status is ACTIVE. Finally, you execute one or more tools with RUBE_MULTI_EXECUTE_TOOL, passing the appropriate tool_slug, arguments, memory, and session_id for a cohesive workflow.

When to Use It

You need to perform a Screenshotone task end-to-end from discovery to execution.
You must verify and maintain an ACTIVE Screenshotone connection before running workflows.
You want to fetch current tool schemas before scripting any automation.
You plan to run multiple Screenshotone tools in a single workflow or session.
You need to handle dynamic tool schemas and avoid hardcoding slugs or arguments.

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server in your client configuration. No API keys needed—just add the endpoint.
Step 2: Verify RUBE_SEARCH_TOOLS responds to confirm tool schemas are available.
Step 3: Call RUBE_MANAGE_CONNECTIONS with toolkit screenshotone and ensure the status is ACTIVE before running workflows.

Best Practices

Always call RUBE_SEARCH_TOOLS first to fetch current schemas before selecting tools.
Check the connection status via RUBE_MANAGE_CONNECTIONS and ensure it is ACTIVE.
Use exact field names and types from the search results; avoid guessing schema details.
Always 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

Discover a Screenshotone tool slug and execute it with a specific URL and viewport using RUBE_MULTI_EXECUTE_TOOL.
Batch screenshots for multiple URLs in a single session by looping discovered tools and inputs.
Establish a Screenshotone connection, verify ACTIVE, then run a sequence of tools to compare renders.
Use RUBE_REMOTE_WORKBENCH to run a composio tool workflow that includes multiple Screenshotone tasks.
Perform pagination-aware tool discovery to fetch all available tools, then execute selected ones.

Frequently Asked Questions

Add this skill to your agents