What is svix-automation?

A workflow that automates Svix operations via the Rube MCP and Composio Svix toolkit.

Do I need API keys to use it?

No API keys are required. Add the MCP endpoint and authenticate via the connected Svix toolkit.

How do I ensure tool schemas are current?

Always run RUBE_SEARCH_TOOLS before executing any tool to fetch the latest tool slugs and input schemas.

svix-automation

Scanned

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

Files (1)

SKILL.md

2.8 KB

Svix Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/svix

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["svix"]
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 Svix-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `svix`
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/svix-automation/SKILL.mdView on GitHub

Overview

Automate Svix operations through Composio's Svix toolkit using Rube MCP. The workflow always starts by calling RUBE_SEARCH_TOOLS to fetch current tool schemas, and requires an active Svix connection established with RUBE_MANAGE_CONNECTIONS. This enables reliable, schema-aware Svix automation across environments.

How This Skill Works

The automation flow discovers available Svix tools with RUBE_SEARCH_TOOLS, then verifies the Svix connection via RUBE_MANAGE_CONNECTIONS and ensures it is ACTIVE. Finally, it executes a chosen tool using RUBE_MULTI_EXECUTE_TOOL, supplying the schema-compliant arguments, a memory payload, and a session_id to maintain context.

When to Use It

When you need to automate a Svix task and must use the latest tool schemas
When integrating Svix workflows with Rube MCP and need to verify an ACTIVE connection
When selecting a tool for a Svix operation, first discover available tools to see input schemas and plans
When executing multiple Svix actions in a single session using RUBE_MULTI_EXECUTE_TOOL and memory
When troubleshooting Svix automation and you need to re-scan tool schemas to adapt to changes

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server in your client configuration
Step 2: Verify RUBE_SEARCH_TOOLS responds to confirm tool schemas are available
Step 3: ConnectSvix with RUBE_MANAGE_CONNECTIONS and execute a discovered tool via RUBE_MULTI_EXECUTE_TOOL

Best Practices

Always call RUBE_SEARCH_TOOLS first before attempting any tool execution
Keep the Svix connection status as ACTIVE before running workflows
Use exact field names and types from the search results (do not hardcode)
Include a memory payload in RUBE_MULTI_EXECUTE_TOOL calls (even if empty)
Reuse session IDs within a workflow and fetch all pages when retrieving tool schemas

Example Use Cases

Discover Svix tools for creating a webhook, then execute it with the discovered tool slug and correct arguments
Update a webhook configuration by reusing an existing session and applying new schema fields
Perform bulk Svix operations by using RUBE_REMOTE_WORKBENCH to run multiple tools in one workflow
Fetch full tool schemas using RUBE_GET_TOOL_SCHEMAS to adapt to changes before running tools
Validate connectivity by running RUBE_MANAGE_CONNECTIONS and confirming ACTIVE status prior to execution

Frequently Asked Questions

Add this skill to your agents