cincopa-automation
Scannednpx machina-cli add skill ComposioHQ/awesome-claude-skills/cincopa-automation --openclawCincopa Automation via Rube MCP
Automate Cincopa operations through Composio's Cincopa toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/cincopa
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Cincopa connection via
RUBE_MANAGE_CONNECTIONSwith toolkitcincopa - 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 toolkitcincopa - 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: "Cincopa 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 Cincopa task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["cincopa"]
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 Cincopa-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit cincopa |
| 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/cincopa-automation/SKILL.mdView on GitHub Overview
Automate Cincopa operations through Composio's Cincopa toolkit using Rube MCP. The approach emphasizes discovering the latest tool schemas before execution to adapt to changes and ensure robust automation. It also requires validating an ACTIVE connection prior to running any workflows.
How This Skill Works
Start by running RUBE_SEARCH_TOOLS to fetch available Cincopa tool slugs and their input schemas. Then verify the Cincopa connection with RUBE_MANAGE_CONNECTIONS and execute a chosen tool using RUBE_MULTI_EXECUTE_TOOL with the discovered slug and schema-aligned arguments. Always include memory in the multi-execute call and rely on current schemas to map fields correctly.
When to Use It
- Starting a new Cincopa workflow and you need the latest tool schemas.
- Verifying that RUBE_MANAGE_CONNECTIONS shows ACTIVE before execution.
- Discovering available Cincopa tools for a specific operation.
- Executing a discovered tool with the exact slug and schema-compliant arguments.
- Coordinating bulk or chained Cincopa tasks within a single session using memory and session reuse.
Quick Start
- Step 1: Ensure Rube MCP is configured and RUBE_SEARCH_TOOLS responds.
- Step 2: Use RUBE_SEARCH_TOOLS to discover tools for Cincopa and pick a slug.
- Step 3: Verify ACTIVE connection with RUBE_MANAGE_CONNECTIONS and execute the tool with RUBE_MULTI_EXECUTE_TOOL, including memory and the correct arguments.
Best Practices
- Always run RUBE_SEARCH_TOOLS first to fetch current schemas.
- Check that RUBE_MANAGE_CONNECTIONS reports ACTIVE before running tools.
- Do not hardcode tool slugs or arguments; map to the search results.
- Include memory: {} in RUBE_MULTI_EXECUTE_TOOL calls.
- Reuse session IDs in a workflow and handle pagination tokens from search results.
Example Use Cases
- Upload a new video to Cincopa when a CMS event occurs, using the discovered upload tool slug and providing required fields.
- Batch-update metadata for multiple assets in Cincopa with the appropriate tool slug and schema.
- Fetch analytics for a published asset using the analytics tool slug.
- Generate thumbnails for a list of assets via the thumbnail tool slug.
- Clean up unused or orphaned assets with the cleanup tool slug discovered by the search.
