$ ~/registry/skill/composiohq-composio-skills-api-labz-automation

SKILL

api-labz-automation

Name: api-labz-automation
Author: Composio

Automate API Labz tasks via Rube MCP using current tool schemas.

Stars

★ 67,763

Source

GitHub

Updated

2026-07-15

// securityCaution

Prompt only, no code
Open source
Community-trusted· 64.7k

Summary

This skill is primarily prompt/documentation-based and does not itself declare built-in secrets, code execution, or local data access. The main security consideration is that it directs users to connect to third-party Rube MCP/Composio remote services and execute API Labz operations through external connections; given the open-source source and strong community adoption, the overall posture is closer to low-to-moderate risk with attention to external data flows and authorization scope.

CredentialsCaution

The material says 'No API keys needed,' but it requires establishing an ACTIVE `api_labz` connection via `RUBE_MANAGE_CONNECTIONS` and potentially completing auth through an external authorization link; this implies credentials/authorization are actually handled by the external Rube/Composio connection flow, which carries the usual caution around third-party managed tokens.

Network egressCaution

The README explicitly requires adding the remote MCP endpoint `https://rube.app/mcp` and performing operations through Composio/API Labz tools; user requests, tool arguments, session IDs, and possibly business data would be sent to the declared third-party service as part of the workflow, but no unrelated or hidden exfiltration endpoints are evident in the material.

Code executionLow risk

Based on the provided material, this is a prompt-only skill description with no auditable executable code, install script, or local process-launching steps; it describes invoking external MCP tools rather than directly executing system commands on the local machine.

Data accessLow risk

The material does not declare any direct ability to read or write local files, system directories, or local databases; data access appears limited to handling relevant remote resources through external API Labz/Composio connections, with no sign of excessive local permission requests.

Supply chainLow risk

The source is an open GitHub repository with strong community adoption (64.7k stars), which is a meaningful risk-reducing signal; although the license is unspecified and maintenance status is unknown, the current material is only documentation/prompt content and shows no suspicious install chain, obfuscated code, or clear supply-chain red flags.

Recommendations

Only establish the connection after confirming you trust the Rube/Composio and API Labz authorization flow, and review the exact permission scope requested on the auth page.
Restrict which MCP services and session data this skill can access in the client, and avoid sending unnecessary sensitive business content to external tools.
Review the linked repository and toolkit documentation to confirm the actual tool set, data flows, and log retention behavior.
For production use, validate the connection and operation boundaries first with a low-sensitivity test account.

Audited by: gpt-5.4 · 2026-06-17

// install

Copy the install command and let the AI configure it · recommended for beginners

Please install the "api-labz-automation" skill from askskill:
1. Download https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/composio-skills/api-labz-automation/SKILL.md
2. Save it as ~/.claude/skills/api-labz-automation/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// docs

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

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.

Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds
Call RUBE_MANAGE_CONNECTIONS with toolkit api_labz
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: "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

Automate API Bible tasks via Rube MCP with schema lookup first.

ComposioGet→

$ loading_