gosquared-automation
by ComposioHQgosquared-automation helps Claude run GoSquared workflows through Composio Rube MCP by searching current tools first, checking the gosquared connection, and using live schemas before execution.
This skill scores 64/100, which makes it acceptable for listing but limited. Directory users can understand when to invoke it and how to begin connecting Gosquared through Rube MCP, but it offers relatively little Gosquared-specific workflow detail, examples, or supporting documentation, so installers should expect to rely on live Rube tool discovery for most execution details.
- Valid frontmatter declares the required Rube MCP dependency and a clear purpose: automating Gosquared tasks through Composio.
- Prerequisites and setup steps explain that users need RUBE_SEARCH_TOOLS and an active Gosquared connection before running workflows.
- The skill emphasizes searching tools first for current schemas, which reduces stale-schema risk when operating through Rube MCP.
- No support files, scripts, references, or README are provided beyond SKILL.md, so adoption depends entirely on the brief inline instructions.
- The workflow guidance is mostly generic Rube MCP tool discovery rather than Gosquared-specific automation examples, and the excerpts show inconsistent connection tool naming between RUBE_MANAGE_CONNECTIONS and RUBE_MANAGE_CONNECTION.
Overview of gosquared-automation skill
What gosquared-automation is for
gosquared-automation is a Claude skill for running GoSquared-related workflows through Composio’s Rube MCP server. Instead of hard-coding one GoSquared API shape, the skill tells the agent to discover the currently available Rube tools first, then execute the right GoSquared operation using the returned schemas.
Use it when you want an AI agent to help with GoSquared workflow automation, connection checks, tool discovery, and task execution without manually browsing the Composio toolkit docs every time.
Best-fit users and jobs
The gosquared-automation skill is best for users who already use GoSquared and want Claude to operate through an MCP tool layer. It fits teams handling analytics, visitor/customer activity, engagement workflows, or operational tasks where the exact GoSquared tool schema may change.
It is especially useful if your workflow starts as a business request, such as “check recent visitor activity” or “run this GoSquared operation,” and needs to become a valid Rube MCP tool call.
Main differentiator
The important differentiator is the “search tools first” pattern. The skill does not assume a fixed GoSquared tool list. It requires RUBE_SEARCH_TOOLS before execution so Claude can retrieve current tool slugs, input schemas, recommended plans, and pitfalls.
That makes gosquared-automation more robust than a static prompt, but it also means adoption depends on having Rube MCP connected and an active GoSquared connection.
How to Use gosquared-automation skill
gosquared-automation install context
Install the skill from the Composio skills collection if your client supports Claude skill installation:
npx skills add ComposioHQ/awesome-claude-skills --skill gosquared-automation
Then add Rube MCP as an MCP server in your client configuration:
https://rube.app/mcp
The skill requires the rube MCP server. Before expecting any GoSquared automation to work, confirm that RUBE_SEARCH_TOOLS is available. Then use RUBE_MANAGE_CONNECTIONS with toolkit gosquared and complete the returned authorization flow if the connection is not ACTIVE.
Inputs the skill needs
A weak request like “use GoSquared” leaves too much guesswork. Give the agent:
- the GoSquared job you want completed;
- the object or activity type involved, if known;
- date range, filters, IDs, email addresses, project/site context, or segment names;
- whether the agent should only plan, retrieve data, or make changes;
- any limits on destructive actions or customer-facing updates.
A stronger prompt:
“Use the gosquared-automation skill. First search Rube tools for the current GoSquared schema. Check that the gosquared connection is active. I want to retrieve visitor or customer activity for the last 7 days for our production project. Do not modify records. Show the tool you plan to call, required fields, and any missing information before executing.”
Recommended workflow
Start by reading SKILL.md in composio-skills/gosquared-automation; it contains the full operating pattern and the required Rube MCP dependency. There are no extra rules/, resources/, references/, or helper scripts in this skill, so the single file is the source of truth.
In practice, ask Claude to follow this sequence:
- Call
RUBE_SEARCH_TOOLSfor the specific GoSquared use case. - Inspect returned tool names, schemas, and pitfalls.
- Confirm the GoSquared connection through
RUBE_MANAGE_CONNECTIONS. - Ask for missing required fields before execution.
- Execute only after the schema and connection are verified.
Practical prompt pattern
Use the skill when you can describe the outcome but not the exact API call. For example:
“Use gosquared-automation for Workflow Automation. Search tools for ‘GoSquared customer lookup and recent activity’. If multiple tools match, compare them briefly and choose the safest read-only option. If auth is inactive, stop and give me the connection step. If required fields are missing, ask me instead of guessing.”
This prompt works better because it defines the use case, safety boundary, discovery behavior, and decision rule.
gosquared-automation skill FAQ
Is gosquared-automation enough without Rube MCP?
No. The skill depends on Rube MCP and the Composio GoSquared toolkit. If RUBE_SEARCH_TOOLS is not available, Claude cannot follow the intended discovery-first workflow. If the gosquared connection is not active, the agent may be able to plan but should not execute GoSquared operations.
How is this better than an ordinary prompt?
An ordinary prompt may invent tool names or rely on outdated GoSquared assumptions. The gosquared-automation skill explicitly instructs the agent to search for current schemas before acting. That is valuable for MCP-based automation because tool names, required fields, and execution guidance can vary.
Is this suitable for beginners?
It is beginner-friendly if your client already supports MCP servers and Claude skills. It is not a one-click GoSquared setup guide. Beginners should expect to configure the Rube MCP endpoint, authorize the GoSquared connection, and provide clear task details before running workflows.
When should I not use this skill?
Do not use it if you need direct GoSquared API code, offline documentation, or automation that bypasses Composio/Rube. Also avoid it for vague requests that could change customer data without review. For write actions, require the agent to show the selected tool, fields, and expected effect before execution.
How to Improve gosquared-automation skill
Make gosquared-automation prompts more specific
The biggest quality improvement comes from replacing broad goals with operational context. Instead of “automate GoSquared reporting,” specify the metric, time window, audience, project, output format, and whether the result should be read-only.
Better input:
“Find the current Rube tools for GoSquared analytics retrieval. I need a summary for the previous calendar week, grouped by day if supported. Return a table and do not create or update anything.”
This reduces schema mismatch and helps the agent choose the least risky tool.
Prevent common failure modes
Common failures include skipping tool discovery, assuming a connection is active, guessing required fields, or using a write-capable tool when a read-only tool is enough. Tell the agent to stop when required inputs are missing and to prefer read-only calls unless you explicitly approve a mutation.
For sensitive workflows, add: “Before any write action, summarize the exact tool call and wait for confirmation.”
Iterate after the first output
After the first run, refine with concrete feedback: missing filters, wrong date range, too much raw data, or the need for a different grouping. Because gosquared-automation relies on live tool discovery, iteration should reference the discovered tool schema rather than generic GoSquared terms.
Example follow-up:
“Use the same discovered tool if appropriate, but narrow the result to visitors from paid campaigns and return only fields needed for a weekly operations report.”
Improve the skill source if you fork it
If you maintain a fork, useful improvements would include example prompts for common GoSquared tasks, explicit read-only versus write workflow patterns, and a short troubleshooting section for inactive connections. Keep the discovery-first rule prominent; it is the core behavior that makes gosquared-automation reliable.