What is gosquared-automation?

A skill that automates Gosquared tasks by using the Composio Gosquared toolkit through Rube MCP.

Do I need API keys to use it?

No. You add the MCP endpoint (https://rube.app/mcp) and set up an ACTIVE Gosquared connection with RUBE_MANAGE_CONNECTIONS.

What should I do before executing tools?

Always search for current tool schemas with RUBE_SEARCH_TOOLS, then verify the connection is ACTIVE before execution; ensure memory is provided in calls.

gosquared-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Gosquared Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/gosquared

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["gosquared"]
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 Gosquared-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `gosquared`
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/gosquared-automation/SKILL.mdView on GitHub

Overview

This skill automates Gosquared operations by leveraging Composio's Gosquared toolkit through Rube MCP. It emphasizes discovering current tool schemas with RUBE_SEARCH_TOOLS before executing workflows to avoid broken integrations.

How This Skill Works

First discover tools using RUBE_SEARCH_TOOLS to obtain tool slugs and input schemas. Then verify that the Gosquared connection is ACTIVE with RUBE_MANAGE_CONNECTIONS and run tools via RUBE_MULTI_EXECUTE_TOOL, supplying the discovered slug, memory, and session data. The workflow relies on the documented sequence: discovery, connection check, then execution.

When to Use It

Automating recurring Gosquared tasks such as data pulls or updates
When tool schemas change frequently and you want current slugs and fields
When you need to confirm the Gosquared connection is ACTIVE before running workflows
When performing multiple Gosquared operations in a single session
When you want to reuse session IDs within a single workflow and create new sessions for new runs

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server in your client config
Step 2: Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds
Step 3: Call RUBE_MANAGE_CONNECTIONS with toolkit gosquared and ensure ACTIVE before running workflows

Best Practices

Always call RUBE_SEARCH_TOOLS first to fetch current tool slugs and schemas
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before execution
Use exact field names and types from the search results
Include memory in RUBE_MULTI_EXECUTE_TOOL calls even if empty
Reuse session IDs within a workflow and generate new ones for new runs

Example Use Cases

Schedule a daily Gosquared data pull using a discovered tool slug
Run multiple Gosquared operations in a single session to optimize throughput
Test a new Gosquared tool after a schema update to ensure compatibility
Reconnect the Gosquared toolkit after a failed ACTIVE status via the auth flow
Explore available Gosquared tools via RUBE_SEARCH_TOOLS to compare capabilities

Frequently Asked Questions

Add this skill to your agents