Name: google-analytics
Rating: 60 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

google-analytics

Google Analytics integration. Manage Accounts. Use when the user wants to interact with Google Analytics data.

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/google-analytics/SKILL.md

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.

The body is highly actionable with concrete executable Membrane commands, a complete action catalog, and a well-sequenced connection workflow including validation checkpoints and feedback loops. Its main weakness is the padded introductory paragraph and a couple of minor structural/numbering gaps.

Suggestions

Remove or drastically shorten the opening definition paragraph ('Google Analytics is a web analytics service that tracks and reports website traffic...') since Claude already knows what Google Analytics is.

Fix the step numbering: define an explicit 'Step 1: Create the connection' header to match the '1b' and 'Step 2' references, or remove the dangling 'Step 2' reference.

Consider moving the 20-row Popular actions table into a references file (e.g. references/actions.md) and keeping only the most common actions inline, to tighten the SKILL.md overview.

Dimension	Reasoning	Score
Conciseness	The opening paragraph explaining what Google Analytics is and who uses it is concept padding Claude already knows, and auth-handling is restated under the Proxy section; the remainder is efficient commands and tables, matching 'mostly efficient but includes some unnecessary explanation.'	3 / 5
Actionability	Provides copy-paste-ready, fully executable commands throughout (install, login, connection ensure/get with --wait, action list/run with JSON --input, request proxy) plus complete flag tables and a 20-row action table, matching the 'fully executable, covers common cases' anchor.	5 / 5
Workflow Clarity	The connection workflow is clearly sequenced with polling checkpoints, state branching (READY/CLIENT_ACTION_REQUIRED sub-types/CONFIGURATION_ERROR), and a re-poll feedback loop, matching 'clear sequence with most checkpoints present'; a minor gap is the referenced but undefined 'Step 2' and loose '1b' numbering.	4 / 5
Progressive Disclosure	No bundle files exist and the skill is a single self-contained, well-sectioned SKILL.md with no external references, matching 'good structure, most content appropriately placed'; the large inline Popular-actions reference table is bulk that could be split into a separate file, keeping it just below 5.	4 / 5
	Total	16 / 20 Passed

Description

66%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 concise, third-person, and clearly scoped to Google Analytics with both a 'what' and an explicit 'Use when' clause. Its main weaknesses are thin concrete-action coverage and missing common synonyms/variations like GA4, web analytics, or reports.

Suggestions

Add 2-3 more concrete actions beyond 'Manage Accounts' (e.g., 'run reports, manage properties and data streams, view key events') to raise specificity.

Expand the trigger clause with natural variations: 'Use when the user wants to interact with Google Analytics data, GA4 properties, web traffic reports, or conversion events.'

Dimension	Reasoning	Score
Specificity	Names the domain and one concrete action ('Manage Accounts') plus a generic one ('interact with Google Analytics data'), matching the anchor that lists 1-2 concrete actions without comprehensive coverage; it falls short of 'several specific actions' at 4.	3 / 5
Completeness	Provides a clear 'what' ('Google Analytics integration. Manage Accounts.') and an explicit 'Use when...' trigger, but the 'when' is generic ('interact with Google Analytics data') rather than concrete varied triggers, matching the score-4 anchor.	4 / 5
Trigger Term Quality	Includes the natural core term 'Google Analytics' (repeated) and 'Accounts', but lacks common variations a user would say such as 'GA4', 'web analytics', 'traffic', 'reports', or 'properties', matching the 'some relevant keywords but missing variations' anchor.	3 / 5
Distinctiveness Conflict Risk	Scoped to a single named product (Google Analytics) with distinctive triggers, giving it a clear niche with minimal overlap with other skills, matching the 'clear niche, minimal conflict risk' anchor.	5 / 5
	Total	15 / 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: membranedev/application-skills
Path: skills/google-analytics/SKILL.md
Commit: f484c82

Reviewed: 5 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.