$ ~/registry/skill/composiohq-composio-skills-raisely-automation

SKILL

raisely-automation

Automate Raisely operations and workflows through Rube MCP and Composio.

Stars

★ 73,862

Source

GitHub

Updated

2026-08-29

// securityLow risk

Prompt only, no code
Open source
Community-trusted· 73.9k

Running security audit…

Credentials
Network egress
Code execution
Data access
Supply chain

// install

Copy the install command and let the AI configure it · recommended for beginners

Please install the "raisely-automation" skill from askskill:
1. Download https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/composio-skills/raisely-automation/SKILL.md
2. Save it as ~/.claude/skills/raisely-automation/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// use cases

Confirm Raisely tools and parameters before execution

Developers or operations staff can search for the currently available Raisely tools and parameter schemas before building a workflow, reducing failures caused by changing tool definitions.

Verify that the Raisely integration is connected

Before running any Raisely workflow, users can verify the connection status first; if it is not active, they can complete setup through the returned authorization link and continue afterward.

Run a session-based Raisely automation workflow

After obtaining tool discovery results and connection status, users can reuse the same session_id to execute Raisely tools and continue with pagination or follow-up steps based on the response.

// docs

AI summary

The README explains how to automate Raisely operations through Composio's Raisely toolkit via Rube MCP. The recommended workflow is to first use RUBE_SEARCH_TOOLS to discover current tools and schemas, then verify the Raisely connection with RUBE_MANAGE_CONNECTIONS, and finally execute actions with RUBE_MULTI_EXECUTE_TOOL. It also highlights key cautions such as reusing session IDs, always including the memory parameter, handling pagination, and avoiding hardcoded schemas.

Show full docs ▾

Raisely Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/raisely

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["raisely"]
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 Raisely-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `raisely`
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

// FAQ

What does this skill do?

It uses Rube MCP to access Composio's Raisely toolkit for automating Raisely operations. The docs emphasize searching for tools first, checking the connection, and then executing with the returned schema.

What prerequisites are required?

You need Rube MCP to be available and RUBE_SEARCH_TOOLS to respond. You also need to configure and activate the Raisely connection through RUBE_MANAGE_CONNECTIONS.

Why must I search for tools first?

Because tool slugs and input schemas can change, the docs explicitly say not to hardcode arguments. You should call RUBE_SEARCH_TOOLS first and execute using the returned field names and types.

Automate Recallai workflows through Rube MCP with tool-schema lookup first.

ComposioGet→

$ loading_