home / skills / composiohq / awesome-claude-skills / timelink-automation

timelink-automation skill

safe

/timelink-automation

This skill automates Timelink operations via Rube MCP, discovering tool schemas first to ensure current workflows and connections.

npx playbooks add skill composiohq/awesome-claude-skills --skill timelink-automation

Review the files below or copy the command above to add this skill to your agents.

Files (1)

SKILL.md

2.9 KB

---
name: timelink-automation
description: "Automate Timelink tasks via Rube MCP (Composio). Always search tools first for current schemas."
requires:
  mcp: [rube]
---

# Timelink Automation via Rube MCP

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

**Toolkit docs**: [composio.dev/toolkits/timelink](https://composio.dev/toolkits/timelink)

## Prerequisites

- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Timelink connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `timelink`
- 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.

1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `timelink`
3. If connection is not ACTIVE, follow the returned auth link to complete setup
4. Confirm connection status shows ACTIVE before running any workflows

## Tool Discovery

Always discover available tools before executing workflows:

```
RUBE_SEARCH_TOOLS
queries: [{use_case: "Timelink 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 Timelink task"}]
session: {id: "existing_session_id"}
```

### Step 2: Check Connection

```
RUBE_MANAGE_CONNECTIONS
toolkits: ["timelink"]
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 Timelink-specific use case |
| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `timelink` |
| 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](https://composio.dev)*

Overview

This skill automates Timelink tasks through Rube MCP (Composio) to run Timelink toolkits programmatically. It guides discovery of available Composio tools, verifies Timelink connections, and executes operations reliably using RUBE_* MCP actions. The workflow enforces schema-driven calls and safe session handling.

How this skill works

The skill always starts by calling RUBE_SEARCH_TOOLS to fetch current tool slugs, input schemas, and execution plans. It checks or establishes an active Timelink connection using RUBE_MANAGE_CONNECTIONS, then runs tools via RUBE_MULTI_EXECUTE_TOOL or RUBE_REMOTE_WORKBENCH with schema-compliant arguments and an explicit memory object. The skill handles pagination, session reuse, and schema lookups to avoid hardcoded fields.

When to use it

Automate Timelink data syncs, exports, or scheduled actions
Integrate Timelink operations into agent workflows or pipelines
Run bulk operations across Timelink via remote workbench
When tool schemas may change or connections need explicit validation
When you need reliable, repeatable Timelink execution with session control

Best practices

Always call RUBE_SEARCH_TOOLS first; never hardcode tool slugs or fields
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE for the timelink toolkit before executing
Use schema fields exactly as returned (types and names) to avoid validation errors
Include a memory object (even {}) in RUBE_MULTI_EXECUTE_TOOL calls
Reuse session IDs for a workflow; generate new sessions for distinct workflows
Check responses for pagination tokens and iterate until complete

Example use cases

Discover and call Timelink tools to export project timelines to CSV
Authenticate and run a scheduled Timelink bulk update across multiple projects
Use RUBE_REMOTE_WORKBENCH to run composio run_composio_tool() for batch processing
Embed Timelink operations into an automated agent that updates tasks based on external events
Fetch full tool schemas with RUBE_GET_TOOL_SCHEMAS to build a dynamic UI for Timelink actions

FAQ

What is the first MCP action I must run?

Always run RUBE_SEARCH_TOOLS to retrieve current tool slugs and input schemas before any other action.

Do I need API keys to use Rube MCP?

No API keys are required. Add https://rube.app/mcp as an MCP server in your client configuration and use the RUBE_* actions.