Skip to main content
NEW · APP STORE Now on iOS · macOS · iPad Android & Windows soon GET IT
Prompts Countdown API Rube MCP Automation Guide

agent tool_use skill risk: low

Countdown API Rube MCP Automation Guide

The prompt instructs on automating Countdown API operations via Composio's toolkit using Rube MCP, including prerequisites, setup steps, tool discovery with RUBE_SEARCH_TOOLS, conn…

  • External action: medium

SKILL 1 file

SKILL.md
---
name: countdown-api-automation
description: "Automate Countdown API tasks via Rube MCP (Composio). Always search tools first for current schemas."
---
# 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](https://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.

1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `countdown_api`
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: "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](https://composio.dev)*

REQUIRED CONTEXT

  • RUBE_SEARCH_TOOLS availability
  • countdown_api connection status

TOOLS REQUIRED

  • RUBE_SEARCH_TOOLS
  • RUBE_MANAGE_CONNECTIONS
  • RUBE_MULTI_EXECUTE_TOOL
  • RUBE_GET_TOOL_SCHEMAS
  • RUBE_REMOTE_WORKBENCH

ROLES & RULES

  1. Always search tools first for current schemas
  2. Always call RUBE_SEARCH_TOOLS first to get current tool schemas
  3. Always discover available tools before executing workflows
  4. Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds
  5. If connection is not ACTIVE, follow the returned auth link to complete setup
  6. Confirm connection status shows ACTIVE before running any workflows
  7. Never hardcode tool slugs or arguments without calling RUBE_SEARCH_TOOLS
  8. Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status before executing tools
  9. Use exact field names and types from the search results
  10. Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty
  11. Reuse session IDs within a workflow
  12. Generate new session IDs for new workflows
  13. Check responses for pagination tokens and continue fetching until complete

EXPECTED OUTPUT

Format
markdown
Constraints
  • always call RUBE_SEARCH_TOOLS first
  • verify ACTIVE connection before execution
  • use exact schemas returned by search
  • include memory and session_id in execute calls

SUCCESS CRITERIA

  • Always search first
  • Verify connection is ACTIVE
  • Use schema-compliant arguments
  • Include memory parameter
  • Reuse sessions appropriately

FAILURE MODES

  • Hardcoding tool slugs without searching first
  • Skipping connection status check
  • Using incorrect field names or types
  • Omitting memory parameter in execute calls
  • Not handling pagination

EXAMPLES

Includes multiple example RUBE_SEARCH_TOOLS, RUBE_MANAGE_CONNECTIONS, and RUBE_MULTI_EXECUTE_TOOL calls with sample arguments and session handling.

CAVEATS

Dependencies
  • Rube MCP connection (RUBE_SEARCH_TOOLS available)
  • Active Countdown API connection via RUBE_MANAGE_CONNECTIONS
Missing context
  • Concrete examples of Countdown API tasks with sample arguments
  • Error handling or retry guidance when tool calls fail
Ambiguities
  • Session management instructions mix 'generate_id: true' and 'id: existing_session_id' without clarifying how to obtain or switch IDs.
  • RUBE_REMOTE_WORKBENCH and RUBE_GET_TOOL_SCHEMAS are mentioned in the table but never explained in the workflow steps.

QUALITY

OVERALL
0.81
CLARITY
0.82
SPECIFICITY
0.88
REUSABILITY
0.78
COMPLETENESS
0.80

IMPROVEMENT SUGGESTIONS

  • Add 2-3 worked examples of common Countdown API operations (e.g., create countdown, list events) showing full tool calls.
  • Clarify session lifecycle: when to generate a new ID versus reuse an existing one.

USAGE

Copy the prompt above and paste it into your AI of choice — Claude, ChatGPT, Gemini, or anywhere else you're working. Replace any placeholder sections with your own context, then ask for the output.

MORE FOR AGENT