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.

56

Quality

65%

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

61%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 a well-structured, actionable reference for GA4 via Rube MCP, with concrete tool sequences and parameters. Its weak spots are redundant pitfalls, a filler "When to Use" line, and missing validation checkpoints on batch operations.

Suggestions

Add an explicit validation step to the batch workflow sequence (e.g. "3. Verify each report response; re-run failed report requests individually") to satisfy the batch-operation feedback-loop requirement.

Remove the duplicate "Known Pitfalls" section or replace it with a pointer back to per-workflow pitfalls to reduce redundancy, and delete the boilerplate "When to Use" sentence.

Include one complete example RUN_REPORT request object so the guidance is fully copy-paste ready.

DimensionReasoningScore

Conciseness

Mostly efficient reference material (tool slugs, parameter limits, value formats), but the "Known Pitfalls" section largely duplicates pitfalls already listed per workflow, and the closing "When to Use" line ("This skill is applicable to execute the workflow or actions described in the overview.") is boilerplate filler.

3 / 5

Actionability

Provides concrete tool slugs, parameter names, and value formats (e.g. 'properties/123456', 'YYYY-MM-DD', '7daysAgo') plus a task→tool Quick Reference table — mostly executable guidance with the minor gap of no full example request object.

4 / 5

Workflow Clarity

Each workflow has a numbered tool sequence and the Setup section includes a validation checkpoint ("Confirm connection status shows ACTIVE"), but the batch workflow (BATCH_RUN_REPORTS) and others lack explicit validation/verification steps, which caps workflow clarity at 3 per the batch-operation rule.

3 / 5

Progressive Disclosure

No bundle files exist; the skill is self-contained with well-organized headers (Prerequisites, Setup, Core Workflows, Common Patterns, Known Pitfalls, Quick Reference) and easy navigation, fitting the good-structure anchor with minor organization gaps from inlined parameter reference material.

4 / 5

Total

14

/

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.

The description is specific and well-scoped to a distinct GA4-via-Rube-MCP niche, but it omits an explicit "Use when..." trigger clause, capping its completeness. Adding concrete trigger phrases would lift the weakest dimension.

Suggestions

Append an explicit trigger clause, e.g. "Use when the user asks to pull GA4 reports, list accounts/properties, or analyze funnels, pivots, or key events."

Mention batch reports and metadata discovery to close the minor specificity gap between the description and the body's full workflow coverage.

DimensionReasoningScore

Specificity

Lists several concrete actions — "run reports, list accounts/properties, funnels, pivots, key events" — but omits some capabilities (batch reports, metadata) present in the body, so it falls at the several-actions-with-minor-gaps anchor rather than comprehensive.

4 / 5

Completeness

The "what" is clear (automate GA4 tasks with concrete actions listed) but there is no "Use when..." clause or equivalent explicit trigger guidance in the description, which caps completeness at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

Includes natural user-facing terms like "Google Analytics", "funnels", "pivots", and "key events" with good coverage, but lacks common synonyms/variations, fitting the good-but-a-few-natural-terms-missing anchor.

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche — Google Analytics 4 via the specific Rube MCP (Composio) — with distinct triggers and minimal overlap risk against other skills.

5 / 5

Total

16

/

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.

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