What is safetyculture-automation?

A Composio skill to automate Safetyculture operations via the Rube MCP (Composio) toolkit, using discovered tool schemas.

Do I need API keys to use this skill?

No API keys are required. Just add the MCP server endpoint (https://rube.app/mcp) in your client configuration.

How do I ensure I’m using current tool schemas?

Always call RUBE_SEARCH_TOOLS to fetch current tool slugs and input schemas before execution; avoid hardcoding slugs or arguments, and include the memory payload in multi-execute calls.

safetyculture-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Safetyculture Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/safetyculture

Prerequisites

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

Step 2: Check Connection

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

View on GitHub

Overview

This skill automates Safetyculture operations through Composio's Safetyculture toolkit using Rube MCP. It emphasizes discovering current tool schemas first via RUBE_SEARCH_TOOLS and ensuring an ACTIVE connection via RUBE_MANAGE_CONNECTIONS before execution.

How This Skill Works

Connect Rube MCP, discover Safetyculture tools with RUBE_SEARCH_TOOLS, then validate the connection with RUBE_MANAGE_CONNECTIONS before execution. Execute the chosen tool with RUBE_MULTI_EXECUTE_TOOL, using the memory payload and session management per the discovered schemas.

When to Use It

Setting up an automated Safetyculture workflow from scratch with live tool schemas.
Running a specific Safetyculture task using discovered tool slugs and inputs.
Validating and reusing an ACTIVE Safetyculture connection before execution.
Installing Safetyculture tool executions into larger Composio workflows.
Handling paginated or updated tool schemas to ensure latest fields are used.

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 connect to the Safetyculture toolkit with RUBE_MANAGE_CONNECTIONS; ensure the status is ACTIVE.
Step 3: Discover available tools with RUBE_SEARCH_TOOLS, then execute a chosen tool with RUBE_MULTI_EXECUTE_TOOL using the discovered slug and input schema.

Best Practices

Always call RUBE_SEARCH_TOOLS before execution to get current tool slugs and schemas.
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status prior to running tools.
Use exact field names and types from the discovered tool schemas; avoid hardcoding.
Always include a memory payload in RUBE_MULTI_EXECUTE_TOOL calls, even if empty.
Reuse session IDs within a workflow and generate new ones for new workflows.

Example Use Cases

Discover tools for a Safetyculture incident audit and execute the tool with the appropriate inputs.
Establish a Safetyculture connection and run a checklist creation or inspection tool.
Automate a sequence of Safetyculture tasks in a scheduled workflow with multiple tool executions.
Use RUBE_MULTI_EXECUTE_TOOL to run several safety tools in a single session with re-used IDs.
Paginate tool schemas via RUBE_GET_TOOL_SCHEMAS or RUBE_SEARCH_TOOLS to fetch latest fields before running.

Frequently Asked Questions

Add this skill to your agents