home / skills / composiohq / awesome-claude-skills / safetyculture-automation

safetyculture-automation skill

safe

/safetyculture-automation

This skill automates Safetyculture tasks using Rube MCP and Composio toolkit, ensuring real-time tool discovery and active connection checks.

npx playbooks add skill composiohq/awesome-claude-skills --skill safetyculture-automation

Review the files below or copy the command above to add this skill to your agents.

Files (1)

SKILL.md

2.9 KB

---
name: safetyculture-automation
description: "Automate Safetyculture tasks via Rube MCP (Composio). Always search tools first for current schemas."
requires:
  mcp: [rube]
---

# Safetyculture Automation via Rube MCP

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

**Toolkit docs**: [composio.dev/toolkits/safetyculture](https://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.

1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `safetyculture`
3. If connection is not ACTIVE, follow the returned auth link to complete setup
4. 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](https://composio.dev)*

Overview

This skill automates SafetyCulture operations using the Composio Safetyculture toolkit via Rube MCP. It guides discovery of current tool schemas, manages SafetyCulture connections, and runs toolkit actions reliably. The workflow emphasizes always searching tools first and validating connection status before execution.

How this skill works

The skill queries Rube MCP to discover available SafetyCulture tools and their input schemas using RUBE_SEARCH_TOOLS. It verifies or establishes an active SafetyCulture connection with RUBE_MANAGE_CONNECTIONS, then invokes one or more toolkit actions via RUBE_MULTI_EXECUTE_TOOL or RUBE_REMOTE_WORKBENCH. Each execution uses the schema returned by the search step and includes a memory object and session management for reliable runs.

When to use it

Automate inspections, checklist creation, or report retrieval in SafetyCulture
Run bulk operations or orchestrated workflows across multiple SafetyCulture tools
Whenever tool schemas may have changed or to avoid hardcoding tool interfaces
Integrate SafetyCulture tasks into larger Rube MCP-driven automation pipelines
Perform repeated runs that require session reuse or pagination handling

Best practices

Always call RUBE_SEARCH_TOOLS first to get current tool slugs and input schemas
Confirm the SafetyCulture connection is ACTIVE via RUBE_MANAGE_CONNECTIONS before executing tools
Supply schema-compliant arguments exactly as returned; field names and types must match
Include a memory parameter (even if empty) in RUBE_MULTI_EXECUTE_TOOL calls
Reuse session IDs for a single workflow and generate new sessions for separate workflows
Check for pagination tokens and continue fetching until responses are complete

Example use cases

Discover available SafetyCulture endpoints, then create or update checklists programmatically
Bulk-run inspections and collect results via RUBE_MULTI_EXECUTE_TOOL and memory aggregation
Automate authentication flow: trigger RUBE_MANAGE_CONNECTIONS, follow returned auth URL, then confirm ACTIVE status
Fetch full tool schemas with RUBE_GET_TOOL_SCHEMAS for advanced validation or mapping
Orchestrate multi-step workflows using RUBE_SEARCH_TOOLS to plan execution and RUBE_REMOTE_WORKBENCH for bulk processing

FAQ

Do I need API keys to use Rube MCP with this skill?

No API keys are required for Rube MCP. Add the MCP endpoint (https://rube.app/mcp) to your client configuration and use the Rube MCP calls.

What if a tool schema changes mid-workflow?

Always call RUBE_SEARCH_TOOLS before each run or step that depends on tool inputs. If a schema changes, update arguments to match the returned schema and restart the step.