What is the prerequisite for timelinesai-automation?

Rube MCP must be connected and RUBE_SEARCH_TOOLS must respond; you must manage connections to the timelinesai toolkit.

No API keys are required; just connect to the Rube MCP endpoint.

How do I handle tool schema changes?

Always search tools first to fetch current schemas and use exact field names from the results.

timelinesai-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Timelinesai Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/timelinesai

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["timelinesai"]
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 Timelinesai-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `timelinesai`
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/timelinesai-automation/SKILL.md

View on GitHub

Overview

Automate Timelinesai operations through Composio's Timelinesai toolkit via Rube MCP. Always search tools first to retrieve current schemas before running any workflows.

How This Skill Works

The workflow discovers available tools with RUBE_SEARCH_TOOLS, verifies and manages connections with RUBE_MANAGE_CONNECTIONS, then executes tools via RUBE_MULTI_EXECUTE_TOOL using the discovered tool slug and arguments. Always include memory in multi-execute calls and confirm the connection is ACTIVE before execution.

When to Use It

Setting up or updating Timelinesai workflows where tool schemas frequently change.
Verifying an ACTIVE Timelinesai connection before executing any workflows.
Discovering available Timelinesai tools and their input schemas prior to automation.
Executing a sequence of Timelinesai tools as part of a single session (reuse session IDs).
Batching tool executions or bulk operations via RUBE_REMOTE_WORKBENCH for Timelinesai tasks.

Quick Start

Step 1: Verify Rube MCP is connected and RUBE_SEARCH_TOOLS responds with tool schemas.
Step 2: Call RUBE_MANAGE_CONNECTIONS with toolkits: ["timelinesai"] and ensure the session is ACTIVE.
Step 3: Discover a tool slug from RUBE_SEARCH_TOOLS and execute it with RUBE_MULTI_EXECUTE_TOOL, including memory and the required arguments.

Best Practices

Always call RUBE_SEARCH_TOOLS first to get current schemas.
Check that RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing any tools.
Use exact field names and types from the search results.
Always include memory in RUBE_MULTI_EXECUTE_TOOL calls (even if empty).
Reuse session IDs within a workflow and handle pagination if responses are paginated.

Example Use Cases

Automate a weekly Timelinesai report: discover tools, verify connection, run the reporting tool.
Orchestrate a multi-step task: search tools, run Tool A, then Tool B with proper memory and session reuse.
Handle schema changes by re-fetching tool schemas before execution.
Bulk-update timelines via RUBE_REMOTE_WORKBENCH with run_composio_tool().
Fetch all available tool schemas using RUBE_GET_TOOL_SCHEMAS to map fields.

Frequently Asked Questions

Add this skill to your agents