What is spotlightr-automation?

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

What prerequisites do I need?

Rube MCP connected, RUBE_SEARCH_TOOLS available, and an active Spotlightr connection authenticated for the spotlightr toolkit.

Why must I always search for tools first?

Tool schemas change frequently. Fetch current tool slugs and arguments with RUBE_SEARCH_TOOLS instead of hardcoding.

spotlightr-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Spotlightr Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/spotlightr

Prerequisites

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

Step 2: Check Connection

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

Overview

Automates Spotlightr operations through Composio's Rube MCP toolkit. It emphasizes discovering current tool schemas before execution and validating the Spotlightr connection to ensure reliable automation.

How This Skill Works

Rube MCP fetches current Spotlightr tool schemas using RUBE_SEARCH_TOOLS, then verifies an ACTIVE Spotlightr connection with RUBE_MANAGE_CONNECTIONS. It finally runs discovered tools with RUBE_MULTI_EXECUTE_TOOL using schema-compliant arguments and a memory payload, ensuring you reuse sessions when appropriate.

When to Use It

Automating an end-to-end Spotlightr workflow from discovery to execution
When tool schemas change, requiring fresh tool slugs and argument names
To ensure the Spotlightr connection is ACTIVE before running workflows
Executing multiple tools or doing bulk ops with RUBE_MULTI_EXECUTE_TOOL or RUBE_REMOTE_WORKBENCH
Handling pagination and discovering complete tool options from RUBE_SEARCH_TOOLS

Quick Start

Step 1: Get Rube MCP endpoint and add https://rube.app/mcp as an MCP server
Step 2: Run RUBE_SEARCH_TOOLS with use_case for Spotlightr operations and start a session
Step 3: Manage the connection with RUBE_MANAGE_CONNECTIONS (toolkit: spotlightr) and then run RUBE_MULTI_EXECUTE_TOOL with a discovered tool slug

Best Practices

Always call RUBE_SEARCH_TOOLS first to fetch current tool schemas
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before any execution
Use exact field names and types from the search results, not hardcoded values
Include memory in every RUBE_MULTI_EXECUTE_TOOL call, even when empty
Reuse session IDs within a workflow and handle pagination tokens when discovering tools

Example Use Cases

Discover tools for Spotlightr operations and pick a tool_slug from the results
Establish a spotlightr connection and confirm ACTIVE, then execute a tool with proper arguments
Execute a sequence of tools in one session using RUBE_MULTI_EXECUTE_TOOL
Use RUBE_REMOTE_WORKBENCH to run a prepared batch of Spotlightr tasks
Fetch full tool schemas with RUBE_GET_TOOL_SCHEMAS to plan changes

Frequently Asked Questions

Add this skill to your agents