CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

55

Quality

63%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills/skills/google-analytics-automation/SKILL.md

The canonical home for this skill is google-analytics-automation in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

56%Scale 1-5

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

This skill provides a comprehensive overview of GA4 automation via Rube MCP with well-organized workflow sections and useful pitfall documentation. Its main weaknesses are repetitive content (property ID format and date ranges mentioned 3+ times), lack of executable examples with concrete parameter values, and a monolithic structure that could benefit from splitting detailed workflows into separate files. The 'When to Use' footer section adds no value.

Suggestions

Add at least one concrete, copy-paste-ready tool call example with actual JSON parameters (e.g., a complete RUN_REPORT call with sample dateRanges, dimensions, and metrics arrays) to improve actionability.

Consolidate repeated pitfalls (property ID format, date ranges, compatibility) into the 'Known Pitfalls' section only, and reference that section from individual workflows instead of restating the same information.

Remove the vacuous 'When to Use' section at the bottom, and trim explanatory phrases like 'User wants to analyze conversion funnels and drop-off rates' which describe what funnels are rather than adding actionable guidance.

Consider splitting the 6 detailed workflow sections into a separate WORKFLOWS.md file, keeping SKILL.md as a concise overview with the quick reference table and links to details.

DimensionReasoningScore

Conciseness

The skill is reasonably structured but contains significant repetition—pitfalls about property ID format and date ranges are repeated across multiple sections and again in the 'Known Pitfalls' summary. The 'When to Use' section at the bottom is vacuous. Several workflow sections explain things Claude would know (e.g., what a funnel is, what a pivot table is). Could be tightened by ~30%.

3 / 5

Actionability

The skill provides tool names, parameter lists, and sequences, but lacks executable code examples—the 'Common Patterns' section uses pseudocode-style numbered lists rather than actual tool call examples with concrete parameter values. No copy-paste-ready tool invocations with sample JSON payloads are provided, leaving gaps in how to actually construct the calls.

3 / 5

Workflow Clarity

Workflows are clearly sequenced with prerequisite steps marked, tool ordering is explicit, and optional vs required steps are labeled. However, there are no explicit validation/verification checkpoints (e.g., checking report response for errors, verifying returned data before presenting to user). Since these aren't destructive operations, the lack of validation doesn't cap the score, but it prevents a 5.

4 / 5

Progressive Disclosure

All content is in a single monolithic file with no bundle files or references to separate documents. At ~200 lines with substantial detail across 6 workflows plus common patterns and pitfalls, this content would benefit from splitting detailed workflow sections or the quick reference table into separate files. The internal structure with headers is decent but the file is longer than ideal for a SKILL.md overview.

3 / 5

Total

13

/

20

Passed

Description

70%Scale 1-5

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

The description does a good job listing specific Google Analytics capabilities and is highly distinctive due to its domain-specific terminology and tooling reference. Its main weakness is the lack of an explicit 'Use when...' clause that would help Claude know when to select this skill, and it could benefit from additional natural trigger terms users might say (e.g., 'GA4', 'traffic data').

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about Google Analytics data, GA4 reports, website traffic, or analytics account management.'

Include common synonyms and abbreviations like 'GA4', 'analytics data', 'traffic', 'pageviews', 'sessions' to improve trigger term coverage.

DimensionReasoningScore

Specificity

Lists several specific actions: 'run reports, list accounts/properties, funnels, pivots, key events.' These are concrete capabilities, though coverage could be slightly more comprehensive (e.g., creating properties, managing users, setting up conversions).

4 / 5

Completeness

The 'what' is clearly stated with specific actions, but there is no explicit 'when' clause (e.g., 'Use when...'). The instruction to 'always search tools first' is operational guidance rather than a trigger condition. Per rubric guidelines, missing 'Use when...' caps completeness at 3.

3 / 5

Trigger Term Quality

Includes good natural keywords like 'Google Analytics', 'reports', 'accounts', 'properties', 'funnels', 'pivots', 'key events'. Missing some common user phrases like 'GA4', 'analytics data', 'traffic', 'pageviews', 'sessions', or 'metrics'.

4 / 5

Distinctiveness Conflict Risk

Highly distinctive with specific references to 'Google Analytics', 'Rube MCP (Composio)', and GA-specific terminology like 'funnels', 'pivots', 'key events'. Very unlikely to conflict with other skills.

5 / 5

Total

16

/

20

Passed

Validation

90%

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

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

10

/

11

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
Reviewed

Table of Contents

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.