brilliant-directories-automation
Scannednpx machina-cli add skill ComposioHQ/awesome-claude-skills/brilliant-directories-automation --openclawBrilliant Directories Automation via Rube MCP
Automate Brilliant Directories operations through Composio's Brilliant Directories toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/brilliant_directories
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Brilliant Directories connection via
RUBE_MANAGE_CONNECTIONSwith toolkitbrilliant_directories - 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 toolkitbrilliant_directories - 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: "Brilliant Directories 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 Brilliant Directories task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["brilliant_directories"]
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 Brilliant Directories-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit brilliant_directories |
| 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/brilliant-directories-automation/SKILL.mdView on GitHub Overview
Automate Brilliant Directories operations through Composio toolkit via Rube MCP. It emphasizes discovering tool schemas first to adapt to changes and ensures an ACTIVE Brilliant Directories connection before running workflows. This approach coordinates discovery, validation, and execution to keep tasks consistent and up to date.
How This Skill Works
First fetch current tool schemas with RUBE_SEARCH_TOOLS to learn available tools and arguments. Then verify an ACTIVE connection with RUBE_MANAGE_CONNECTIONS for the brilliant_directories toolkit. Finally execute the chosen tool with RUBE_MULTI_EXECUTE_TOOL, supplying memory and the discovered arguments, reusing session IDs when possible.
When to Use It
- Starting a Brilliant Directories routine where tool schemas may change, so always fetch current schemas first.
- Connecting a Brilliant Directories account or reactivating a previously saved connection before running workflows.
- Running a discovered tool that matches a defined use case for listing, updates, or data sync.
- Debugging campaigns by checking exact field names and types against the latest tool schemas.
- Running recurring or multi-step tasks in a single session to maximize reuse and consistency.
Quick Start
- Step 1: Ensure Rube MCP is configured as an MCP server and RUBE_SEARCH_TOOLS responds.
- Step 2: Discover tools with RUBE_SEARCH_TOOLS using the Brilliant Directories use case to obtain slugs and schemas.
- Step 3: Manage the connection with RUBE_MANAGE_CONNECTIONS and execute a tool with RUBE_MULTI_EXECUTE_TOOL, including memory and a session_id.
Best Practices
- Always call RUBE_SEARCH_TOOLS first to get current tool schemas.
- Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools.
- Use exact field names and types from the search results; avoid hardcoding slugs.
- Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty.
- Reuse session IDs within a workflow; generate new ones only for new workflows.
Example Use Cases
- Create a new Brilliant Directories listing using a discovered tool slug from RUBE_SEARCH_TOOLS.
- Update multiple listings in bulk by applying a discovered update tool with current schemas.
- Sync new member data from an external source into Brilliant Directories using a mapped tool.
- Audit available tools by fetching tool schemas before performing large changes.
- Run a combined search, connect, and execute sequence within a single session for a seamless workflow.
