Cats Automation via Rube MCP
SkillSearchThis skill lets your AI work directly in Cats, an applicant tracking system. Once added, your AI can search and update records and handle routine Cats tasks for you, so you spend less time clicking through the app yourself.
Instructions available. Your AI can read the instructions. Execution depends on the setup they require.
Account requirements not reviewed. Check the skill instructions before use; ahel provides instructions and does not run this skill.
After adding the skill, tell your AI what you want done in Cats, such as finding or updating a record. It checks the available actions first to make sure it uses the right ones for the current setup.
Then ask your AI: use the Cats Automation via Rube MCP skill
What your AI can do with it
- Search records in the Cats applicant tracking system
- Update records in Cats
- Automate routine Cats tasks from start to finish
What this skill tells your AI
The instructions your AI receives, as published by composio-community/awesome-codex-skills in composio-skills/cats-automation/SKILL.md and read by ahel’s review.
Automate Cats operations through Composio's Cats toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/cats
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Cats connection via
RUBE_MANAGE_CONNECTIONSwith toolkitcats - Always call
RUBE_SEARCH_TOOLSfirst 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_TOOLSresponds - Call
RUBE_MANAGE_CONNECTIONSwith toolkitcats - 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: "Cats 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 Cats task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["cats"]
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_CONNECTIONSshows ACTIVE status before executing tools - Schema compliance: Use exact field names and types from the search results
- Memory parameter: Always include
memoryinRUBE_MULTI_EXECUTE_TOOLcalls, 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 Cats-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit cats |
| 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
Signals
- GitHub stars
- 17k
- Forks
- 2k
- Last commit
- Jul 2026
Others that do the same job
Advanced
- Item type
- skill
- Key
cats-automation- Source
- github.com/composio-community/awesome-codex-skills
github.com/composio-community/awesome-codex-skills