What is Classmarker Automation via Rube MCP?

It's a workflow-driven approach to automate Classmarker tasks using Composio's Rube MCP toolkit, enforcing current tool schemas and managed connections.

Do I need to call RUBE_SEARCH_TOOLS every time?

Yes. Tool schemas can change, so you should fetch current schemas before discovering tools and executing workflows.

What if a tool schema changes mid-workflow?

If a schema changes, re-run RUBE_SEARCH_TOOLS to refresh tool slugs and inputs, then adapt the execution step to the new schema before continuing.

classmarker-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Classmarker Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/classmarker

Prerequisites

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

Step 2: Check Connection

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

View on GitHub

Overview

Automate Classmarker operations through Composio's Rube MCP toolkit. Always search tool schemas first to ensure compatibility and avoid breaking changes. This skill streamlines discovering tools, validating connections, and executing Classmarker tasks in a repeatable workflow.

How This Skill Works

It uses Rube MCP to connect to the Classmarker toolkit, fetch current tool schemas via RUBE_SEARCH_TOOLS, and manage the Classmarker connection with RUBE_MANAGE_CONNECTIONS. When executing, it runs RUBE_MULTI_EXECUTE_TOOL with the discovered tool slug and schema-compliant arguments, always including memory and following the session lifecycle.

When to Use It

Automating recurring Classmarker operations at scale (e.g., exams setup, roster syncing, and results processing).
Ensuring tool schemas are current by always performing RUBE_SEARCH_TOOLS before workflows.
Verifying the Classmarker connection is ACTIVE via RUBE_MANAGE_CONNECTIONS before execution.
Coordinating multi-step workflows that run multiple Classmarker tools in a single session.
Bulk operations like exporting results or bulk tagging via RUBE_REMOTE_WORKBENCH when needed.

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server in your client configuration.
Step 2: Verify RUBE_SEARCH_TOOLS responds and fetch current tool schemas.
Step 3: Call RUBE_MANAGE_CONNECTIONS with toolkit 'classmarker' and ensure ACTIVE before running workflows.

Best Practices

Always search first: tool schemas change, so avoid hardcoding slugs or arguments.
Check connection: ensure RUBE_MANAGE_CONNECTIONS shows ACTIVE before any run.
Schema compliance: use exact field names/types from the search results.
Memory parameter: include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty.
Session management: reuse session IDs within a workflow and paginate results as needed.

Example Use Cases

Daily automated exam setup for a course: discover tools, create an exam with dynamic inputs, and schedule it for students.
Roster sync with Classmarker: fetch the latest fields from the schema and update enrollments accordingly.
Create, publish, and assign an exam: retrieve tool schema, execute create_exam, then publish and assign to a class.
Bulk results export after a testing window: run the appropriate tool via RUBE_REMOTE_WORKBENCH for all students.
End-to-end workflow: discover tools, verify ACTIVE connection, and execute a sequence of tools within one session.

Frequently Asked Questions

Add this skill to your agents