What is the purpose of this skill?

It automates Token Metrics tasks through Composio's toolkit using Rube MCP.

Do I need API keys to use it?

No API keys are required; you just add the MCP endpoint (https://rube.app/mcp) and use RUBE_SEARCH_TOOLS to fetch schemas.

What if tool schemas change?

Always re-run RUBE_SEARCH_TOOLS to fetch updated tool slugs and arguments before execution.

token-metrics-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Token Metrics Automation via Rube MCP

Automate Token Metrics operations through Composio's Token Metrics toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/token_metrics

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["token_metrics"]
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 Token Metrics-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `token_metrics`
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/token-metrics-automation/SKILL.md

View on GitHub

Overview

Automates Token Metrics operations through Composio's Token Metrics toolkit via Rube MCP. It emphasizes discovering current tool schemas first using RUBE_SEARCH_TOOLS and validating an ACTIVE connection before execution.

How This Skill Works

The workflow follows three steps: discover available tools with RUBE_SEARCH_TOOLS, verify the token_metrics connection with RUBE_MANAGE_CONNECTIONS, then execute the chosen tool using RUBE_MULTI_EXECUTE_TOOL, always including memory and reusing sessions where appropriate.

When to Use It

Automating routine Token Metrics operations while keeping tool schemas up-to-date
Before running workflows, ensure the token_metrics connection is ACTIVE
When you need to discover available Tool Slugs and input schemas dynamically (not hardcoded)
Executing multiple tools in a single session and reusing the same session_id
Handling pagination and changing tool schemas to avoid errors from hardcoded values

Quick Start

Step 1: Connect to Rube MCP and verify tool schemas with RUBE_SEARCH_TOOLS
Step 2: Manage token_metrics connection and confirm ACTIVE with RUBE_MANAGE_CONNECTIONS
Step 3: Discover tools and execute a chosen tool via RUBE_MULTI_EXECUTE_TOOL, ensuring memory and session_id

Best Practices

Always search first for current schemas before every run to avoid stale tool slugs
Check that RUBE_MANAGE_CONNECTIONS shows an ACTIVE status before execution
Follow 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; generate new sessions for new workflows

Example Use Cases

Fetch token metrics deltas and push updated values to a dashboard
Validate token metrics across multiple networks and surface inconsistencies
Generate periodic token metrics reports using dynamically discovered tools
Bulk update token metrics parameters for a batch of tokens
Retry failed metric workflows by reusing the same session and rechecking the connection

Frequently Asked Questions

Add this skill to your agents