Blackboard Automation

When to use this skill

Use Blackboard Automation when an AI agent needs a reusable SKILL.md workflow for this job: Automate Blackboard tasks via Rube MCP (Composio). Always search tools first for current schemas.

When not to use it

Skip Blackboard Automation when the task is outside the productivity category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.

How to install

1. Personal install: create ~/.claude/skills/blackboard-automation/SKILL.md (and any bundled scripts) so Claude Code, Claude Desktop, and compatible agents can load it in every project.
2. Project install: commit the same folder at .claude/skills/blackboard-automation/ so teammates get the skill with the repo.
3. Restart the agent session after copying files so it re-scans the skills directory, then ask for the task in words that match the skill description.

Full install guide for Claude, Cursor, and Codex

What this skill does

# Blackboard Automation via Rube MCP

Automate Blackboard operations through Composio's Blackboard toolkit via Rube MCP.

**Toolkit docs**: [composio.dev/toolkits/blackboard](https://composio.dev/toolkits/blackboard)

## Prerequisites

- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) - Active Blackboard connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `blackboard` - 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 `blackboard` 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: "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_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 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](https://composio.dev)*

Intended uses

• Use Blackboard Automation when this documented workflow matches the task.