Skip to main content
ClaudeWave
Skill470 estrellas del repoactualizado 3d ago

api-labz-automation

The api-labz-automation skill enables automated workflows for API Labz operations through Composio's toolkit via Rube MCP. Use this when you need to programmatically interact with API Labz by first discovering available tools through RUBE_SEARCH_TOOLS, verifying the active connection status via RUBE_MANAGE_CONNECTIONS, and then executing tasks with RUBE_MULTI_EXECUTE_TOOL while adhering to the returned schemas and recommended execution plans.

Instalar en Claude Code
Copiar
git clone --depth 1 https://github.com/openteams-lab/openteams /tmp/api-labz-automation && cp -r /tmp/api-labz-automation/assets/skills/api-labz-automation ~/.claude/skills/api-labz-automation
Después abre una sesión nueva de Claude Code; el skill carga automáticamente.

SKILL.md

# API Labz Automation via Rube MCP

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

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

## Prerequisites

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

### Step 2: Check Connection

```
RUBE_MANAGE_CONNECTIONS
toolkits: ["api_labz"]
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 API Labz-specific use case |
| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `api_labz` |
| 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)*