Do I need an API key for Rube MCP?

No, you only need to add the MCP endpoint (e.g., https://rube.app/mcp); API keys are not required.

What should I do before executing any workflow?

Always search for tools with RUBE_SEARCH_TOOLS to fetch current tool schemas and ensure the D2lbrightspace connection is ACTIVE via RUBE_MANAGE_CONNECTIONS.

How do I execute a tool?

Use RUBE_MULTI_EXECUTE_TOOL with the discovered tool_slug, supply schema-compliant arguments, include a memory payload, and provide a session_id.

d2lbrightspace-automation

npx machina-cli add skill ComposioHQ/awesome-claude-skills/d2lbrightspace-automation --openclaw

Files (1)

SKILL.md

3.0 KB

D2lbrightspace Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/d2lbrightspace

Prerequisites

Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
Active D2lbrightspace connection via RUBE_MANAGE_CONNECTIONS with toolkit d2lbrightspace
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.

Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds
Call RUBE_MANAGE_CONNECTIONS with toolkit d2lbrightspace
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: "D2lbrightspace 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 D2lbrightspace task"}]
session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["d2lbrightspace"]
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 D2lbrightspace-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `d2lbrightspace`
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/d2lbrightspace-automation/SKILL.md

View on GitHub

Overview

Automate D2lbrightspace operations using Composio's D2lbrightspace toolkit via Rube MCP. This skill orchestrates tool discovery, connection management, and execution, ensuring you always fetch current schemas before acting.

How This Skill Works

Discover available D2lbrightspace tools and their input schemas with RUBE_SEARCH_TOOLS, then verify an ACTIVE D2lbrightspace connection using RUBE_MANAGE_CONNECTIONS. Finally, execute the chosen tool with RUBE_MULTI_EXECUTE_TOOL, supplying a memory payload and a session_id, and reuse sessions within a workflow for continuity.

When to Use It

When you need to perform a specific D2lbrightspace operation and want the exact input schema.
When you have an active D2lbrightspace connection and want to run a discovered tool.
When tool schemas may change and you must search tools first to avoid hardcoding slugs or args.
When executing a batch of D2lbrightspace tools in a single workflow and reusing a session.
When you need to fetch the full tool schemas with RUBE_GET_TOOL_SCHEMAS to confirm fields.

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server in your client configuration and verify RUBE_SEARCH_TOOLS responds.
Step 2: Use RUBE_SEARCH_TOOLS with a D2lbrightspace use_case to discover tools and their input schemas.
Step 3: Call RUBE_MANAGE_CONNECTIONS for the d2lbrightspace toolkit, then run RUBE_MULTI_EXECUTE_TOOL with the discovered tool_slug, proper arguments, memory, and a session_id.

Best Practices

Always call RUBE_SEARCH_TOOLS before executing any tool to ensure current schemas.
Check that RUBE_MANAGE_CONNECTIONS shows ACTIVE status before running tools.
Use exact field names and types from the search results; avoid hardcoding.
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 D2L course using a discovered tool from RUBE_SEARCH_TOOLS.
Enroll users into a D2L course via a tool after establishing a D2L connection.
Bulk update grades or course content using a discovered D2lbrightspace tool.
Sync user data from an external system into D2L using the toolset.
Inspect and reload tool schemas with RUBE_GET_TOOL_SCHEMAS before a new workflow.

Frequently Asked Questions

Add this skill to your agents