shortpixel-automation
npx machina-cli add skill ComposioHQ/awesome-claude-skills/shortpixel-automation --openclawShortpixel Automation via Rube MCP
Automate Shortpixel operations through Composio's Shortpixel toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/shortpixel
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Shortpixel connection via
RUBE_MANAGE_CONNECTIONSwith toolkitshortpixel - Always call
RUBE_SEARCH_TOOLSfirst 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_TOOLSresponds - Call
RUBE_MANAGE_CONNECTIONSwith toolkitshortpixel - 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: "Shortpixel 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 Shortpixel task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["shortpixel"]
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_CONNECTIONSshows ACTIVE status before executing tools - Schema compliance: Use exact field names and types from the search results
- Memory parameter: Always include
memoryinRUBE_MULTI_EXECUTE_TOOLcalls, 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 Shortpixel-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit shortpixel |
| 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/shortpixel-automation/SKILL.mdView on GitHub Overview
Automate Shortpixel operations through Composio's Shortpixel toolkit via Rube MCP. It emphasizes discovering current tool schemas with RUBE_SEARCH_TOOLS before every run and validating an ACTIVE Shortpixel connection. Use this to streamline batch image optimization and related tasks.
How This Skill Works
Workflow begins by discovering available Shortpixel tools with RUBE_SEARCH_TOOLS, then checks/establishes an ACTIVE connection via RUBE_MANAGE_CONNECTIONS, and finally executes the chosen tool with RUBE_MULTI_EXECUTE_TOOL using the correct memory payload and session_id.
When to Use It
- When you need to automate a batch of Shortpixel tasks without manual clicks
- When tool schemas update and you must fetch current slugs and args first
- When you want to verify connection status before running workflows
- When executing multiple tools in a single session to optimize a project
- When performing bulk or paginated tool discovery to enumerate all available operations
Quick Start
- Step 1: Verify Rube MCP connectivity by running RUBE_SEARCH_TOOLS and confirm tool schemas are returned
- Step 2: Call RUBE_MANAGE_CONNECTIONS with toolkit 'shortpixel' and ensure the status is ACTIVE
- Step 3: Discover tools with RUBE_SEARCH_TOOLS, then execute a chosen tool using RUBE_MULTI_EXECUTE_TOOL with a memory payload and a session_id
Best Practices
- Always call RUBE_SEARCH_TOOLS first to fetch current tool schemas
- Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools
- Use exact field names and types from search results; avoid hardcoding slugs
- Include memory: {} in RUBE_MULTI_EXECUTE_TOOL calls
- Reuse session IDs within a workflow and generate new ones for new runs
Example Use Cases
- Batch optimize images by discovering TOOL_SLUG_FROM_SEARCH for 'image optimization' and running it with arguments like {image_ids:[...], quality:70} in a single session
- Convert assets in a folder to WebP by discovering TOOL_SLUG_FROM_SEARCH with webp conversion use_case and executing with {folder_id:'FOLDER123', target:'webp', quality:80}
- Resize and compress a batch by executing TOOL_SLUG_FROM_SEARCH with {width:1024, height:768, mode:'compress'}
- Retry a failed optimization by re-running the same TOOL_SLUG_FROM_SEARCH within the same session after a failure
- Bulk operations via RUBE_REMOTE_WORKBENCH: run_composio_tool() to execute several Shortpixel tasks collected from discovery