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.

1.26x

Quality

68%

Does it follow best practices?

Impact

99%

1.26x

Average score across 3 eval scenarios

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/all-skills/skills/google-analytics-automation/SKILL.md

Quality

Content

67%Weight 40%Scale 1-5

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

A well-structured, highly actionable operational guide with concrete tool sequences, parameters, and genuine pitfalls that Claude would not know on its own. The main costs are duplicated pitfall content across sections and a single-file layout that inlines reference-grade detail.

Suggestions

De-duplicate the pitfalls: state date formats, property-ID format, and compatibility warnings once, in the "Known Pitfalls" section, and remove the repeats from individual workflows.

Move the per-tool parameter details and the common dimensions/metrics list into a references/ file (e.g., references/tool-reference.md) linked from the body, keeping SKILL.md as a lean overview.

Add one complete example RUN_REPORT request payload (property, dateRanges, dimensions, metrics) so the most common workflow is copy-paste ready.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean, tool-specific operational data, but pitsfall content is duplicated: date formats appear in both workflow 2 and "Known Pitfalls" ("'YYYY-MM-DD' or relative ('today', 'yesterday', '7daysAgo'...)"), and the 'properties/123456' ID format is stated three times. Fits 3's "mostly efficient but could be tightened" better than 4's "minor instances".	3 / 5
Actionability	Concrete, executable guidance throughout: exact tool slugs ("GOOGLE_ANALYTICS_RUN_REPORT"), numbered sequences with [Required]/[Prerequisite] tags, key parameters, and a Quick Reference table. Not 5 because there is no complete example request payload (e.g., a full RUN_REPORT arguments object) to copy-paste.	4 / 5
Workflow Clarity	Setup has an explicit validation checkpoint ("Confirm connection status shows ACTIVE before running any workflows") and each workflow is a clearly labeled sequence; the batch workflow notes "check individual report responses" for error recovery. Not 5 because compatibility checks are only [Optional] rather than enforced steps, and response-error handling is not an explicit step with a retry loop.	4 / 5
Progressive Disclosure	No bundle files exist, and the single-file body is well organized with clear section headers, when-to-use framing per workflow, and a Quick Reference table. Not 5 because ~200 lines of per-tool reference (parameters, pitfalls, common dimensions/metrics) could reasonably live in a one-level-deep reference file to keep SKILL.md a leaner overview.	4 / 5
	Total	15 / 20 Passed

Description

70%Weight 40%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.

A specific, well-scoped description that names concrete GA4 capabilities in third person with strong distinctiveness. Its main weakness is the missing "Use when..." trigger clause, which caps completeness and leaves activation guidance implicit.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user wants GA4 reports, traffic/metrics queries, funnel analysis, or account/property discovery."

Include natural synonyms users say: "GA4", "traffic", "conversions" (alongside "key events").

Mention batch reports and dimension/metric compatibility checks to close the coverage gaps in the action list.

Dimension	Reasoning	Score
Specificity	"run reports, list accounts/properties, funnels, pivots, key events" names five concrete action areas with specific tool-level language. Not 5 because coverage has minor gaps (batch reports, metadata/compatibility workflows unmentioned); well above 3's "1-2 concrete actions".	4 / 5
Completeness	The "what" is clear ("Automate Google Analytics tasks via Rube MCP... run reports, list accounts/properties, funnels, pivots, key events"), but there is no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. Not 4 because "when" is entirely absent rather than merely imprecise.	3 / 5
Trigger Term Quality	"Google Analytics", "reports", "funnels", "pivots", "key events" are phrases users naturally say. Missing common synonyms like "GA4", "traffic", or "conversions" (the legacy name for key events), so not the comprehensive synonym coverage of 5; clearly better than 3's partial keyword set.	4 / 5
Distinctiveness Conflict Risk	"Google Analytics" + "Rube MCP (Composio)" carves out a clear niche with distinct triggers (reports, funnels, pivots, key events) that no generic analytics skill would claim. Minimal conflict risk; matches the 5 anchor's clear-niche example.	5 / 5
	Total	16 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

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

	Total	15 / 16 Passed

Repository: davepoon/buildwithclaude
Path: plugins/all-skills/skills/google-analytics-automation/SKILL.md
Commit: b90e2de

Reviewed: 4 days 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.