blackboard-automation
Scannednpx machina-cli add skill ComposioHQ/awesome-claude-skills/blackboard-automation --openclawBlackboard Automation via Rube MCP
Automate Blackboard operations through Composio's Blackboard toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/blackboard
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Blackboard connection via
RUBE_MANAGE_CONNECTIONSwith toolkitblackboard - 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 toolkitblackboard - 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: "Blackboard 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 Blackboard task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["blackboard"]
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 Blackboard-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit blackboard |
| 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/blackboard-automation/SKILL.mdView on GitHub Overview
This skill automates Blackboard operations through Composio's Rube MCP toolkit. It emphasizes discovering current tool schemas with RUBE_SEARCH_TOOLS, establishing an ACTIVE Blackboard connection via RUBE_MANAGE_CONNECTIONS, and executing tools with RUBE_MULTI_EXECUTE_TOOL while supplying a memory object and session_id.
How This Skill Works
First, discover available Blackboard tools using RUBE_SEARCH_TOOLS to fetch tool slugs and input schemas. Next, verify the Blackboard connection is ACTIVE with RUBE_MANAGE_CONNECTIONS. Finally, execute the chosen tool via RUBE_MULTI_EXECUTE_TOOL, including the memory payload and a valid session_id.
When to Use It
- Automating routine Blackboard operations by discovering and running tools discovered via RUBE_SEARCH_TOOLS.
- Initial setup: connect Rube MCP to Blackboard and ensure the connection shows ACTIVE.
- Before workflows, fetch current tool schemas to avoid hardcoding tool slugs.
- Executing a discovered tool with RUBE_MULTI_EXECUTE_TOOL using the correct arguments and session.
- Handling multi-step workflows with session reuse and memory management across tools.
Quick Start
- Step 1: Verify RUBE_SEARCH_TOOLS is available by connecting Rube MCP and testing the endpoint.
- Step 2: Connect to Blackboard with RUBE_MANAGE_CONNECTIONS and confirm ACTIVE status.
- Step 3: Discover a tool with RUBE_SEARCH_TOOLS, then execute it using RUBE_MULTI_EXECUTE_TOOL with memory: {} and a valid session_id.
Best Practices
- Always call RUBE_SEARCH_TOOLS first to fetch current schemas.
- Verify RUBE_MANAGE_CONNECTIONS reports ACTIVE before execution.
- Use exact field names and types from search results; avoid hardcoding.
- Include memory in each RUBE_MULTI_EXECUTE_TOOL call, even if empty.
- Reuse session IDs within a workflow; generate new ones for new tasks.
Example Use Cases
- Automate posting a course update by discovering the appropriate tool via RUBE_SEARCH_TOOLS and executing with arguments.
- Reconnect and validate a Blackboard integration before a scheduled run.
- Run a sequence of tools in a session and reuse the session_id across steps.
- Bulk operations using RUBE_REMOTE_WORKBENCH with run_composio_tool for performance.
- Fetch full tool schemas with RUBE_GET_TOOL_SCHEMAS to map required fields before automation.
