streamtime-automation
Scannednpx machina-cli add skill ComposioHQ/awesome-claude-skills/streamtime-automation --openclawStreamtime Automation via Rube MCP
Automate Streamtime operations through Composio's Streamtime toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/streamtime
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Streamtime connection via
RUBE_MANAGE_CONNECTIONSwith toolkitstreamtime - 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 toolkitstreamtime - 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: "Streamtime 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 Streamtime task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["streamtime"]
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 Streamtime-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit streamtime |
| 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/streamtime-automation/SKILL.mdView on GitHub Overview
Automate Streamtime tasks using Composio's Streamtime toolkit through Rube MCP. The approach emphasizes discovering current tool schemas with RUBE_SEARCH_TOOLS, validating an ACTIVE Streamtime connection, and executing tools with memory-aware inputs. Always fetch tool schemas first to stay aligned with API changes.
How This Skill Works
The workflow starts by discovering available Streamtime tools with RUBE_SEARCH_TOOLS. Next, you verify the connection to Streamtime using RUBE_MANAGE_CONNECTIONS and ensure the status is ACTIVE. Finally, you execute a chosen tool via RUBE_MULTI_EXECUTE_TOOL, supplying the discovered tool_slug, schema-compliant arguments, and a memory object.
When to Use It
- Automate routine Streamtime tasks by discovering current tool slugs with RUBE_SEARCH_TOOLS.
- When tool schemas change, fetch the latest schemas before executing any workflow.
- Batch multiple Streamtime actions in a single session using RUBE_MULTI_EXECUTE_TOOL.
- Validate the Streamtime connection is ACTIVE prior to running workflows.
- Build end-to-end Streamtime workflows that reuse session IDs for related tasks.
Quick Start
- Step 1: Add https://rube.app/mcp as an MCP server and verify RUBE_SEARCH_TOOLS responds.
- Step 2: Connect to Streamtime with RUBE_MANAGE_CONNECTIONS and ensure the status is ACTIVE.
- Step 3: Discover a tool with RUBE_SEARCH_TOOLS and execute it with RUBE_MULTI_EXECUTE_TOOL using the required memory.
Best Practices
- Always call RUBE_SEARCH_TOOLS first; don't hardcode slugs or fields.
- Verify the connection status with RUBE_MANAGE_CONNECTIONS is ACTIVE before executing tools.
- Use exact field names and types from the search results to ensure schema compliance.
- Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({}).
- Reuse session IDs within a workflow and generate new ones for new workflows.
Example Use Cases
- Create a new Streamtime project by using a discovered tool slug and the required input fields.
- Bulk update multiple time entries for a sprint by executing several tools in a single session.
- Fetch the latest tool schemas, then run a Create Project tool with schema-compliant input.
- Connect to Streamtime, verify ACTIVE, then execute a time-entry logging tool within the same flow.
- Run a multi-step workflow that discovers tools, checks the connection, and executes a tool in one session.
