/composio-search-automation
Automate Composio Search tasks via Rube MCP (Composio). Always search tools first for current schemas.
$ npx -y skills add openteams-lab/openteams --skill composio-search-automation --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/composio-search-automation
Context preview
The summary Claude sees to decide when to auto-load this skill.
Automate Composio Search tasks via Rube MCP (Composio). Always search tools first for current schemas.
SKILL.md
composio-search-automation.SKILL.mdname: composio-search-automation
description: "Automate Composio Search tasks via Rube MCP (Composio). Always search tools first for current schemas."
requires:
mcp: [rube]
Composio Search Automation via Rube MCP
Automate Composio Search operations through Composio's Composio Search toolkit via Rube MCP.
**Toolkit docs**: [composio.dev/toolkits/composio_search](https://composio.dev/toolkits/composio_search)
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Composio Search connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `composio_search`
- 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 `composio_search` 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: "Composio Search 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 Composio Search task"}]
session: {id: "existing_session_id"}Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["composio_search"]
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 Composio Search-specific use case | | Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `composio_search` | | 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)*
Read more
name: composio-search-automation description: "Automate Composio Search tasks via Rube MCP (Composio). Always search tools first for current schemas." requires: mcp: [rube]
Composio Search Automation via Rube MCP
Automate Composio Search operations through Composio's Composio Search toolkit via Rube MCP.
**Toolkit docs**: [composio.dev/toolkits/composio_search](https://composio.dev/toolkits/composio_search)
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Composio Search connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `composio_search`
- 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 `composio_search` 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: "Composio Search 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 Composio Search task"}]
session: {id: "existing_session_id"}Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS toolkits: ["composio_search"] 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 Composio Search-specific use case | | Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `composio_search` | | 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)*
Plan, Build, and Ship — with a team of AI agents instead of one
Repo: openteams-lab/openteams
Other skills on openteams.
- /ably-automation
Automate Ably tasks via Rube MCP (Composio). Always search tools first for current schemas.
Open skill - /abstract-automation
Automate Abstract tasks via Rube MCP (Composio). Always search tools first for current schemas.
Open skill - /abuselpdb-automation
Automate Abuselpdb tasks via Rube MCP (Composio). Always search tools first for current schemas.
Open skill - /abyssale-automation
Automate Abyssale tasks via Rube MCP (Composio). Always search tools first for current schemas.
Open skill - /accelo-automation
Automate Accelo tasks via Rube MCP (Composio). Always search tools first for current schemas.
Open skill - /accredible-certificates-automation
Automate Accredible Certificates tasks via Rube MCP (Composio). Always search tools first for current schemas.
Open skill

