PromptShop

Html To Image Automation

automates HTML to image conversions using Composio's Html To Image toolkit via Rube MCP. It's designed for users who need to programmatically generate images...

Install

npx promptshop add html-to-image-automation

Details

What This Skill Does

  • This skill automates HTML to image conversions using Composio's Html To Image toolkit via Rube MCP.
  • It's designed for users who need to programmatically generate images from HTML, streamlining workflows and enabling dynamic content creation.
  • The skill requires an active Html To Image connection via Rube MCP.

When to Use

Generate website previews Create social media cards Automate report generation Convert HTML emails to images Archive web content visually Create visual documentation

Key Features

Automates HTML to image conversion Uses Composio's Html To Image toolkit Integrates with Rube MCP for tool discovery Requires active Html To Image connection Provides tool schemas via RUBE_SEARCH_TOOLSSupports dynamic content creation

Manual Installation

Automate Html To Image operations through Composio's Html To Image toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/html_to_image

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS toolkits: ["html_to_image"] 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

OperationApproach
Find toolsRUBE_SEARCH_TOOLS with skill-specific use case
ConnectRUBE_MANAGE_CONNECTIONS with relevant toolkit
ExecuteRUBE_MULTI_EXECUTE_TOOL with discovered tool slugs
Bulk opsRUBE_REMOTE_WORKBENCH with run_composio_tool()
Full schemaRUBE_GET_TOOL_SCHEMAS for tools with schema Ref