simple-analytics-automation
by ComposioHQsimple-analytics-automation helps agents automate Simple Analytics via Composio Rube MCP by verifying the simple_analytics connection, discovering current tool schemas with RUBE_SEARCH_TOOLS, and running workflow automation tasks safely.
This skill scores 66/100, which means it is acceptable for directory listing but should be presented as a lightweight MCP workflow guide rather than a complete automation package. It gives agents enough trigger and setup guidance to use Rube MCP for Simple Analytics, but directory users should expect to rely on live tool discovery because the repository evidence does not include concrete end-to-end Simple Analytics task examples or supporting files.
- Valid frontmatter clearly names the skill and declares its Rube MCP requirement for Simple Analytics automation.
- Prerequisites and setup steps explain how to verify Rube MCP, manage the Simple Analytics connection, and ensure the connection is ACTIVE before use.
- The skill repeatedly instructs agents to call RUBE_SEARCH_TOOLS first, which reduces schema guesswork when Composio tool definitions change.
- No support files, scripts, references, or bundled examples beyond SKILL.md, so all execution depends on live Rube MCP discovery.
- The available excerpt is mostly a generic discovery/setup pattern and does not show concrete Simple Analytics workflows or parameters for common tasks.
Overview of simple-analytics-automation skill
What simple-analytics-automation does
simple-analytics-automation is a Claude skill for automating Simple Analytics tasks through Composio’s Rube MCP server. Its main value is not a fixed set of hard-coded analytics commands; it teaches the agent to discover the current Simple Analytics tool schemas first, verify the connection, and then execute the right Rube tool for the requested analytics workflow.
Best fit for Workflow Automation users
This simple-analytics-automation skill is best for teams that already use Simple Analytics and want an agent-assisted way to run repeatable reporting, data lookup, or account operations without manually navigating every API detail. It fits Workflow Automation scenarios where the exact tool inputs may change over time, because the skill requires RUBE_SEARCH_TOOLS before execution instead of relying on stale assumptions.
Key adoption requirement
The critical dependency is Rube MCP. Your AI client must be configured with the Rube MCP server at https://rube.app/mcp, and the Simple Analytics toolkit connection must be active through RUBE_MANAGE_CONNECTIONS using toolkit simple_analytics. If Rube MCP is unavailable, or if the Simple Analytics connection is not authenticated, this skill will not be useful beyond serving as a setup checklist.
What makes it different from a generic prompt
A generic prompt might ask an assistant to “get Simple Analytics data” and hope it knows the API. This skill adds a safer operating pattern: search the available Rube tools, inspect current schemas, confirm authentication, then run the appropriate Simple Analytics operation. That reduces failures caused by outdated tool names, missing fields, or guessed parameters.
How to Use simple-analytics-automation skill
simple-analytics-automation install context
If your environment supports installing skills from this repository, use:
npx skills add ComposioHQ/awesome-claude-skills --skill simple-analytics-automation
Then configure Rube MCP in your AI client by adding:
https://rube.app/mcp
The upstream skill itself expects Rube MCP tools to be available, especially RUBE_SEARCH_TOOLS and RUBE_MANAGE_CONNECTIONS. After installation, open composio-skills/simple-analytics-automation/SKILL.md first; there are no extra scripts/, resources/, or references/ folders in the current repository tree, so the skill file is the primary source of operating instructions.
Required inputs before running workflows
Before asking the agent to perform a Simple Analytics task, provide:
- The exact Simple Analytics goal, such as “retrieve traffic metrics for a site,” “check available analytics operations,” or “prepare a recurring report.”
- The site, domain, date range, filters, or metric names if relevant.
- Whether the task should only discover tools, validate access, or actually execute an operation.
- Any output format requirements, such as a table, CSV-ready summary, JSON, or short executive brief.
The skill’s most important rule is to search first. A strong prompt should explicitly permit the agent to call RUBE_SEARCH_TOOLS for the current schema instead of guessing fields.
Strong prompt pattern for usage
A weak prompt is:
“Use Simple Analytics to get my stats.”
A better simple-analytics-automation usage prompt is:
“Use the simple-analytics-automation skill. First verify Rube MCP is available and check the simple_analytics connection status. Then call RUBE_SEARCH_TOOLS for the current Simple Analytics tool schema for retrieving website traffic metrics. If the connection is active, fetch metrics for example.com for the last 30 days. Return a concise table with visitors, pageviews, top pages if available, and mention any fields or metrics that the discovered schema does not support.”
This works better because it defines the connection check, discovery step, target domain, time range, desired metrics, and output format.
Practical workflow to follow
Use a three-pass workflow:
- Connection pass: confirm Rube MCP responds and Simple Analytics is ACTIVE through
RUBE_MANAGE_CONNECTIONS. - Discovery pass: run
RUBE_SEARCH_TOOLSwith the specific use case, not a vague query. For example: “Simple Analytics traffic summary by domain and date range.” - Execution pass: use the returned tool slug and schema exactly, then summarize the result with any limitations.
Do not skip discovery just because a previous run worked. The skill’s design assumes current Rube schemas are the source of truth.
simple-analytics-automation skill FAQ
Is simple-analytics-automation only for developers?
No. Non-developers can use it if their AI client supports MCP tools and someone has connected Rube MCP. However, setup is more technical than a normal chat prompt because it depends on MCP configuration and Simple Analytics authentication.
When should I not use this skill?
Do not use it when you need offline analysis, direct access to the Simple Analytics API without Composio/Rube, or a fully custom analytics pipeline. The simple-analytics-automation skill is designed around Rube MCP tool execution, so it is a poor fit if your environment cannot expose MCP tools to the agent.
Does it replace Simple Analytics dashboards?
No. It complements the dashboard by automating specific lookups, summaries, and repeatable reporting flows. For exploratory visual analysis, the Simple Analytics interface may still be faster. For scheduled, agent-driven, or multi-step Workflow Automation tasks, this skill is more useful.
Why does the skill insist on tool discovery first?
Because Composio toolkit schemas, tool slugs, and required fields can change. RUBE_SEARCH_TOOLS returns current tool names, input schemas, execution plans, and pitfalls. This is the main reliability mechanism in the simple-analytics-automation guide and the first thing to verify when troubleshooting.
How to Improve simple-analytics-automation skill
Improve simple-analytics-automation prompts
The fastest improvement is better task framing. Include the analytics object, time range, domain, metrics, output format, and whether execution is allowed. For example:
“Discover the current Simple Analytics tools for listing top referrers for example.com over the previous calendar month. If supported, run the operation and return top referrers with counts. If not supported, report the closest available tool and the missing field.”
This gives the agent a clear success condition and a safe fallback.
Common failure modes to prevent
The most common failures are skipped schema discovery, inactive Simple Analytics connection, vague metric requests, and assumed field names. Prevent them by requiring the agent to:
- Confirm
RUBE_SEARCH_TOOLSis available. - Check
simple_analyticsconnection status before execution. - Use the discovered schema exactly.
- Ask for missing domain, date range, or metric details before calling execution tools.
These checks matter more than clever prompt wording.
Iterate after the first result
After the first output, refine based on what the discovered tools actually support. If the result lacks a metric you expected, ask the agent to search again for a narrower use case, such as “Simple Analytics top pages by date range” instead of “analytics report.” If the schema exposes pagination, filters, or grouping options, use a second pass to improve completeness rather than accepting the first summary.
Repository reading path for maintainers
For maintainers evaluating or extending the simple-analytics-automation skill, start with SKILL.md. Focus on the prerequisite block, setup sequence, tool discovery instruction, and core workflow pattern. Since the current skill has no companion scripts or reference files, improvements should likely add concrete example prompts, troubleshooting branches for inactive connections, and sample task categories such as traffic summaries, referrer checks, and recurring report generation.