What is Countdown API Automation via Rube MCP?

A workflow that discovers, connects to, and executes tools from Composio's Countdown API toolkit using the Rube MCP platform.

Why must I search tools first?

Tool schemas change over time; fetching current slugs and input schemas prevents broken integrations and ensures correct arguments are used.

What if the connection is not ACTIVE?

Follow the auth flow provided by RUBE_MANAGE_CONNECTIONS to complete setup, then re-check until the status shows ACTIVE before running workflows.

countdown-api-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Countdown API Automation via Rube MCP

Automate Countdown API operations through Composio's Countdown API toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/countdown_api

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["countdown_api"]
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 Countdown API-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `countdown_api`
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/countdown-api-automation/SKILL.md

View on GitHub

Overview

This skill automates Countdown API operations through Composio's Countdown API toolkit via Rube MCP. It emphasizes always searching for current tool schemas before execution to adapt to changes. By coordinating discovery, connection management, and multi-tool execution, you can run countdown workflows reliably.

How This Skill Works

Technically, you first use RUBE_SEARCH_TOOLS to discover available Countdown API tools and their schemas. Then you establish and verify an ACTIVE connection with RUBE_MANAGE_CONNECTIONS, and finally execute one or more tools via RUBE_MULTI_EXECUTE_TOOL, including the required memory payload. The workflow ensures schemas are current and avoids hardcoding slugs.

When to Use It

When automating recurring Countdown API tasks and need repeatable, scriptable runs
When tool schemas may change and you must always fetch current slugs and fields
When you require a confirmed ACTIVE connection before executing workflows
When orchestrating multi-tool sequences in a single session
When performing bulk Countdown API operations or using remote benches

Quick Start

Step 1: Configure Rube MCP by adding https://rube.app/mcp as an MCP server
Step 2: Verify connectivity with RUBE_SEARCH_TOOLS and connect via RUBE_MANAGE_CONNECTIONS (countdown_api), ensuring ACTIVE status
Step 3: Discover tools and execute with RUBE_MULTI_EXECUTE_TOOL using the proper memory payload

Best Practices

Always run RUBE_SEARCH_TOOLS before any execution to fetch current tool schemas
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before running tools
Use exact field names and types from the search results; avoid hardcoding
Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty
Reuse session IDs within a workflow and generate new ones for new tasks

Example Use Cases

Auto-discover and run a countdown creation tool against a new API schema
Batch-create multiple countdowns using discovered tool slugs
Validate tool schemas via RUBE_GET_TOOL_SCHEMAS before first run
Execute a sequence: search, connect, then run multiple countdown tools
Perform bulk countdown operations via RUBE_REMOTE_WORKBENCH run_composio_tool

Frequently Asked Questions

Add this skill to your agents