$ ~/registry/skill/composiohq-composio-skills-spondyr-automation

SKILL

spondyr-automation

Name: spondyr-automation
Author: Composio

Automate Spondyr tasks via Rube MCP after checking current tool schemas.

Stars

★ 67,763

Source

GitHub

Updated

2026-07-15

// securityCaution

Prompt only, no code
Open source
Community-trusted· 64.9k

Summary

This skill is primarily prompt/documentation content, and the source is open with strong community adoption, so the overall risk is low. Its real operational capability depends on external Rube MCP and a Spondyr connection, so the main concerns are the external toolchain and remote data flow rather than the skill text itself.

CredentialsCaution

The material states that the skill itself requires no local API keys or environment variables, but actual use requires establishing an external Spondyr connection via RUBE_MANAGE_CONNECTIONS and completing authorization, meaning credentials exist in the external connection system; no direct credential harvesting or exposure red flags are shown in the skill text.

Network egressCaution

The skill itself is prompt-only and does not directly implement network communication; however, the README explicitly instructs adding the remote MCP endpoint https://rube.app/mcp and using Composio/Rube to execute Spondyr operations, so task data and arguments are likely routed through that remote service. This is normal declared connectivity, but the material does not fully describe data handling boundaries.

Code executionLow risk

No local scripts, install commands, or direct code-execution logic are shown; the skill mainly provides usage flow and tool-calling guidance, and does not itself start local processes or execute arbitrary code on the host.

Data accessLow risk

Based on the provided material, the skill itself does not claim to read or write local files, system directories, or host data stores; its access scope is mainly to guide use of an external MCP for Spondyr resources, with no apparent request for local data permissions beyond its stated purpose.

Supply chainLow risk

The source is an open GitHub repository with very strong community adoption (about 64.9k stars), which materially lowers supply-chain risk. The license and maintenance status are not explicit, and the skill depends on external Rube/Composio services, so those should be verified separately, but there are no concrete red flags here that would justify a high-risk rating.

Recommendations

Before connecting to https://rube.app/mcp, verify Rube/Composio privacy terms, data retention practices, and the scope of Spondyr authorization.
Activate the Spondyr connection only when needed, prefer least-privilege authorization, and regularly revoke unused connections.
Review the tool schemas returned by RUBE_SEARCH_TOOLS before execution to avoid sending unnecessary sensitive business data to external services.
Treat this skill as a documentation-layer asset; to assess real runtime risk, separately audit the underlying Rube MCP and Composio tool implementation.

Audited by: gpt-5.4 · 2026-06-17

// install

Copy the install command and let the AI configure it · recommended for beginners

Please install the "spondyr-automation" skill from askskill:
1. Download https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/composio-skills/spondyr-automation/SKILL.md
2. Save it as ~/.claude/skills/spondyr-automation/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// docs

Spondyr Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/spondyr

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["spondyr"]
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 Spondyr-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `spondyr`
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

Automate Composio tasks via Rube MCP with tool schema lookup first.

ComposioGet→

$ loading_