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

76%

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

78%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.

The body is highly actionable and well-sequenced with concrete tool sequences and validation checkpoints, but it is monolithic — no reference files split out the bulk parameter/material despite the skill's length. Minor redundancy between per-workflow pitfalls and the summary section slightly hurts conciseness.

Suggestions

Move the full parameter reference and common dimensions/metrics lists into a separate references file (e.g., REFERENCE.md) and link to it from the body to improve progressive disclosure.

Collapse the standalone 'Known Pitfalls' section into the per-workflow pitfalls (or vice versa) to remove redundancy and tighten conciseness.

Add an explicit validate/fix/retry loop for BATCH_RUN_REPORTS (check each report response, retry failed individual requests) to strengthen workflow clarity for the batch operation.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean and action-dense (tool slugs, parameters, examples), but the standalone 'Known Pitfalls' section repeats date-range and property-ID guidance already in per-workflow 'Pitfalls', which could be trimmed.	4 / 5
Actionability	Concrete tool slugs, exact parameter names, literal examples ('properties/123456', 'YYYY-MM-DD', '7daysAgo'), ID-resolution code blocks, and a quick-reference table make the guidance copy-paste ready across common cases.	5 / 5
Workflow Clarity	Each workflow is a clearly numbered tool sequence with [Required]/[Optional]/[Prerequisite] tags and checkpoints (connection-ACTIVE confirmation, CHECK_COMPATIBILITY before reports), though the batch workflow's error-handling feedback loop is only weakly implied rather than explicit.	4 / 5
Progressive Disclosure	No bundle files exist and the ~250-line body keeps all parameter reference, dimension/metric lists, and quick-reference inline with no one-level-deep references, fitting the score-3 anchor of content that could be split being inlined.	3 / 5
	Total	16 / 20 Passed

Description

75%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.

The description is specific and distinct, naming concrete GA4 capabilities, but lacks an explicit 'Use when...' trigger clause, which caps its completeness. Trigger-term coverage is good but not exhaustive.

Suggestions

Add an explicit 'Use when...' clause (e.g., 'Use when the user asks about Google Analytics 4 reports, traffic metrics, funnels, or property management') to lift completeness above 3.

Include a few user-natural synonyms/variations (e.g., 'GA4', 'web analytics', 'audience reports') to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'run reports, list accounts/properties, funnels, pivots, key events' — covering GA4's reporting surface comprehensively, matching the score-5 anchor.	5 / 5
Completeness	A clear 'what' is present, but there is no explicit 'Use when...' trigger clause; per the guidelines a missing 'when' caps completeness at 3.	3 / 5
Trigger Term Quality	Natural terms like 'Google Analytics', 'reports', 'funnels', 'pivots', 'key events' give good coverage, but it lacks common synonyms/variations a user might say, stopping short of the score-5 anchor.	4 / 5
Distinctiveness Conflict Risk	'Google Analytics tasks via Rube MCP (Composio)' carves a clear, distinct niche with minimal overlap risk against other skills.	5 / 5
	Total	17 / 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: a9fa86d

Reviewed: about 19 hours 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.