CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

79%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

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

75%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, actionable reference for GA4 automation with clear tool sequences, parameters, and pitfalls. Weaknesses are modest: duplicated pitfall content, a filler closing line, no sample request payload, and no use of reference files for the longer catalogs.

Suggestions

Add a copy-paste-ready example RUN_REPORT request body (property, dateRanges, dimensions, metrics) to make report execution fully executable.

Remove the vague 'When to Use' closing sentence and consolidate date-format and ID-format pitfalls that are repeated across sections.

Move the common dimensions/metrics catalog and per-workflow parameter details into a references/ file, keeping SKILL.md as a lean overview with clearly signaled links.

DimensionReasoningScore

Conciseness

The body is dense and assumes Claude's competence (no conceptual padding about GA4), but pitfalls are duplicated between workflow sections and the 'Known Pitfalls' section (date formats, property ID formats), and the trailing 'When to Use' line ('This skill is applicable to execute the workflow or actions described in the overview.') is pure filler — minor trimming needed, so anchor 4 rather than 5.

4 / 5

Actionability

Concrete tool names, exact parameter names, resource-name formats, and date values make the guidance mostly executable, but there is no example request payload (e.g., a sample RUN_REPORT request body with dateRanges/dimensions/metrics objects), keeping it below the copy-paste-ready anchor 5.

4 / 5

Workflow Clarity

Each workflow has a clear numbered tool sequence with prerequisites, and validation checkpoints exist (confirm connection ACTIVE before workflows, CHECK_COMPATIBILITY before complex reports, check individual responses in batch reports), but there are no explicit error-recovery loops, so it sits between anchors 3 and 5.

4 / 5

Progressive Disclosure

The single-file skill is well organized with clear section headers, consistent per-workflow structure, and a quick-reference table for navigation; at ~230 lines with per-workflow details and dimension/metric catalogs all inline, some content could be split into reference files, so it does not reach the clear-overview-with-signaled-references anchor 5.

4 / 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.

A specific, well-scoped description with strong action coverage and low conflict risk, written in appropriate third-person voice. Its main weakness is the missing 'Use when...' trigger clause and absent common synonyms like 'GA4' or 'conversions'.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks about Google Analytics / GA4 data, reports, funnels, conversion tracking, or property management.'

Include common user synonyms such as 'GA4', 'conversions', and 'traffic data' alongside 'key events' to improve trigger matching.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — 'run reports, list accounts/properties, funnels, pivots, key events' — covering all core GA4 workflows the skill supports, matching the comprehensive-coverage anchor rather than the minor-gaps anchor.

5 / 5

Completeness

It clearly answers 'what' (automate GA4 reporting and property management via Rube MCP) but has no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3; it is not a 4 because the 'when' is entirely absent rather than merely imprecise.

3 / 5

Trigger Term Quality

Good natural keyword coverage ('Google Analytics', 'reports', 'funnels', 'pivots', 'key events', 'accounts/properties'), but common synonyms like 'GA4', 'conversions', or 'traffic data' are missing, so it falls between the good and comprehensive anchors.

4 / 5

Distinctiveness Conflict Risk

'Automate Google Analytics tasks via Rube MCP (Composio)' carves out a clear niche with distinct triggers (GA4 reports, funnels, pivots, key events) and minimal overlap with other analytics skills.

5 / 5

Total

17

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository

administrakt0r/AI-Agents-Safe-Coding-Skills

Path

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

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.