Do I need API keys to use this skill?

No. You only need to add the Rube MCP endpoint (e.g., https://rube.app/mcp) in your client configuration; no API keys are required.

Why must I always search tools first?

Tool schemas can change. Always calling RUBE_SEARCH_TOOLS ensures you use current slugs and argument fields instead of hardcoding them.

How should I handle the memory parameter?

Include the memory field in every RUBE_MULTI_EXECUTE_TOOL call, even if it’s empty ({}), to satisfy the required schema structure.

lessonspace-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Lessonspace Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/lessonspace

Prerequisites

Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
Active Lessonspace connection via RUBE_MANAGE_CONNECTIONS with toolkit lessonspace
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 lessonspace
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: "Lessonspace 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 Lessonspace task"}]
session: {id: "existing_session_id"}

Step 2: Check Connection

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

View on GitHub

Overview

Automate Lessonspace operations by invoking Composio's Lessonspace toolkit through Rube MCP. The workflow centers on discovering current tool schemas with RUBE_SEARCH_TOOLS and ensuring an ACTIVE Lessonspace connection before execution.

How This Skill Works

First, RUBE_SEARCH_TOOLS retrieves available Lessonspace tools and their input schemas. Then RUBE_MANAGE_CONNECTIONS establishes or verifies an ACTIVE connection for the lessonspace toolkit. Finally, RUBE_MULTI_EXECUTE_TOOL runs a chosen tool with the required arguments, memory, and a session_id (reusing sessions across steps when appropriate).

When to Use It

When you need to perform a Lessonspace operation after discovering current tool schemas
When establishing or validating an ACTIVE Lessonspace connection before tasks
When executing a discovered tool with proper arguments and memory
When you want to reuse a session_id across multiple steps in a workflow
When handling paginated results or tool lists and continuing until complete

Quick Start

Step 1: Configure Rube MCP endpoint (https://rube.app/mcp) in your client
Step 2: Run RUBE_SEARCH_TOOLS to load current Lessonspace tool schemas
Step 3: Manage connections and run a tool with RUBE_MULTI_EXECUTE_TOOL using memory and a session_id

Best Practices

Always search tools first to get current schemas
Check that RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools
Use exact field names and types from search results
Always include memory in RUBE_MULTI_EXECUTE_TOOL calls (even if empty)
Reuse session IDs within a workflow; generate new ones for new workflows

Example Use Cases

Create a new Lessonspace workspace by discovering the create-space tool and executing it with required fields
Add members to an existing space by running the discovered add_members tool with exact schema fields
Chain steps: discover -> connect -> execute -> update, reusing a session_id across steps
Bulk update tasks using RUBE_REMOTE_WORKBENCH with run_composio_tool for multiple tools
Regularly re-scan tool schemas with RUBE_GET_TOOL_SCHEMAS to keep tools in sync with API changes

Frequently Asked Questions

Add this skill to your agents