google-analytics-automation

Automate Google Analytics tasks via Rube MCP (Composio): run reports, list accounts/properties, funnels, pivots, key events. Always search tools first for current schemas.

Install with Tessl CLI

npx tessl i github:Lingjie-chen/MT5 --skill google-analytics-automation

What are skills?

1.26x

Quality

65%

Does it follow best practices?

Impact

99%

1.26x

Average score across 3 eval scenarios

Optimize this skill with Tessl

npx tessl skill review --optimize ./.trae/skills/google-analytics-automation/SKILL.md

SKILL.md

Review

Evals

Discovery

67%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This description effectively communicates specific Google Analytics capabilities and has a clear technical niche that distinguishes it from other skills. However, it lacks an explicit 'Use when...' clause and could benefit from additional natural trigger terms that users commonly say when requesting analytics help.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about Google Analytics, GA4, website traffic analysis, or needs to pull analytics reports.'

Include common user-facing trigger terms like 'GA', 'GA4', 'website traffic', 'page views', 'conversions', 'analytics dashboard' to improve discoverability.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: 'run reports, list accounts/properties, funnels, pivots, key events' - these are clear, actionable capabilities within the Google Analytics domain.	3 / 3
Completeness	Clearly answers 'what' (automate GA tasks, run reports, etc.) but lacks an explicit 'Use when...' clause. The 'when' is only implied by the capabilities listed, not explicitly stated.	2 / 3
Trigger Term Quality	Includes relevant terms like 'Google Analytics', 'reports', 'accounts', 'properties', 'funnels', 'pivots', 'key events', but missing common user variations like 'GA', 'GA4', 'analytics data', 'website traffic', 'page views', or 'conversions'.	2 / 3
Distinctiveness Conflict Risk	Highly distinctive with clear niche: 'Google Analytics' + 'Rube MCP (Composio)' creates a very specific scope that is unlikely to conflict with other skills. The technical stack and domain are clearly defined.	3 / 3
	Total	10 / 12 Passed

Implementation

62%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill provides comprehensive coverage of Google Analytics automation with excellent workflow clarity and clear tool sequencing. However, it lacks executable code examples (showing actual tool calls with real parameters) and could be more concise by consolidating repeated information. The content would benefit from concrete invocation examples rather than parameter lists.

Suggestions

Add at least one complete, executable tool invocation example per workflow showing actual parameter values (e.g., a real RUBE_SEARCH_TOOLS call followed by GOOGLE_ANALYTICS_RUN_REPORT with concrete dateRanges, dimensions, and metrics)

Consolidate the repeated pitfalls about property ID format ('properties/123456') into a single 'ID Formats' section referenced elsewhere

Move the detailed dimension/metric compatibility rules and filter expression syntax to a separate REFERENCE.md file, keeping only essential guidance in the main skill

Dimension	Reasoning	Score
Conciseness	The skill is reasonably efficient but includes some redundancy (e.g., repeating 'Property ID (required)' across multiple workflows, explaining pagination concepts Claude knows). The pitfalls sections are valuable but could be consolidated to reduce repetition.	2 / 3
Actionability	Provides tool names and parameter lists, but lacks executable code examples. The 'Common Patterns' section uses pseudocode-style numbered steps rather than actual API call examples with concrete parameter values. No copy-paste ready examples showing actual tool invocations.	2 / 3
Workflow Clarity	Workflows are clearly sequenced with explicit [Required]/[Prerequisite]/[Optional] markers. Each workflow has a clear 'When to use' trigger, tool sequence, key parameters, and pitfalls. The setup section includes validation steps (confirm ACTIVE status before proceeding).	3 / 3
Progressive Disclosure	Content is well-organized with clear sections and a quick reference table, but everything is in one monolithic file. Complex topics like funnel configuration or filter expressions could be split into separate reference files. The external toolkit docs link is good but underutilized.	2 / 3
	Total	9 / 12 Passed

Validation

90%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.