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.

72

1.26x
Quality

58%

Does it follow best practices?

Impact

99%

1.26x

Average score across 3 eval scenarios

SecuritybySnyk

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./plugins/all-skills/skills/google-analytics-automation/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

50%

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

This is a competent reference skill that covers GA4 workflows comprehensively with clear tool sequences and useful pitfall warnings. Its main weaknesses are repetition of key information across sections (property ID format, date ranges), lack of executable examples with real parameter values, and missing validation/verification steps in workflows. The document would benefit from consolidation of repeated warnings, addition of concrete tool call examples, and splitting detailed content into supporting files.

Suggestions

Add at least one fully concrete tool call example per major workflow showing actual parameter JSON (e.g., a complete RUN_REPORT call with realistic dateRanges, dimensions, and metrics values).

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.

Add explicit validation checkpoints to workflows, e.g., 'Verify the response contains a `rows` key before processing' or 'Check for error responses before proceeding to the next step.'

Consider splitting detailed workflow sections (pivot reports, funnel reports, key events) into separate referenced files to keep SKILL.md as a concise overview with navigation.

DimensionReasoningScore

Conciseness

The skill is reasonably well-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. Some sections explain things Claude would know (e.g., what pagination is). The document could be tightened by ~30% without losing information.

2 / 3

Actionability

Tool names and parameter lists are concrete and useful, but the 'Common Patterns' code blocks are pseudocode/numbered steps rather than actual executable tool calls with example parameters. No complete example showing a full tool invocation with realistic parameter values is provided, making it harder to copy-paste into action.

2 / 3

Workflow Clarity

Each workflow has a clear tool sequence with prerequisite/required labels, which is good. However, there are no explicit validation or verification checkpoints—no step says 'verify the report returned data' or 'check for errors in the response before proceeding.' For batch operations and complex pivots/funnels, this lack of feedback loops is a gap.

2 / 3

Progressive Disclosure

The content is well-sectioned with a quick reference table, but it's a monolithic ~200-line document with no bundle files to offload detailed content. The common dimensions/metrics list, detailed pitfalls, and individual workflow sections could be split into referenced files. The single external link to Composio docs is helpful but insufficient for progressive disclosure.

2 / 3

Total

8

/

12

Passed

Description

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.

The description is strong on specificity and distinctiveness, clearly naming the platform (Google Analytics), the integration method (Rube MCP/Composio), and concrete actions. However, it lacks an explicit 'Use when...' clause which caps completeness, and the trigger terms could be improved by including common user-facing synonyms like 'GA4', 'website traffic', or 'analytics 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 metrics.'

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

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: 'run reports, list accounts/properties, funnels, pivots, key events' and includes the operational guidance to 'search tools first for current schemas.'

3 / 3

Completeness

Clearly answers 'what does this do' with specific actions, but lacks an explicit 'Use when...' clause or equivalent trigger guidance explaining when Claude should select this skill.

2 / 3

Trigger Term Quality

Includes relevant terms like 'Google Analytics', 'reports', 'accounts', 'properties', 'funnels', 'pivots', 'key events', but misses common user variations like 'GA4', 'analytics data', 'website traffic', 'page views', 'conversions'. The mention of 'Rube MCP (Composio)' is technical jargon unlikely to be used by end users.

2 / 3

Distinctiveness Conflict Risk

Clearly scoped to Google Analytics via a specific integration (Rube MCP/Composio), making it highly distinctive and unlikely to conflict with other skills.

3 / 3

Total

10

/

12

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
davepoon/buildwithclaude
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.