ga4

Query Google Analytics 4 (GA4) data via the Analytics Data API. Use when you need to pull website analytics like top pages, traffic sources, user counts, sessions, conversions, or any GA4 metrics/dimensions. Supports custom date ranges and filtering.

Quality

90%

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

The canonical home for this skill is clean-test-workspace/ga4

Quality

Content

88%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 lean, highly actionable body: executable one-line commands for the common GA4 queries, exact env-var setup, an explicit validation step, and a tight troubleshooting section. The gaps are minor — the OAuth token-acquisition flow is under-specified and the bundled auth script is never referenced.

Suggestions

In the Setup section, replace "from initial auth flow" with the actual command, e.g. "python3 scripts/ga4_auth.py" to obtain GOOGLE_REFRESH_TOKEN, so the one-time setup is fully executable.

In Troubleshooting, point "Re-run the OAuth flow" at scripts/ga4_auth.py so the recovery path names a concrete file instead of an implied one.

Dimension	Reasoning	Score
Conciseness	Every section is commands, environment variables, or terse lists; there is no explanation of concepts Claude already knows, and metrics/dimensions sections list only common values with an external link for the full schema. Each token earns its place.	5 / 5
Actionability	All query examples are copy-paste executable (flags verified against scripts/ga4_query.py's argparse) and setup names exact env vars with a validation command, but the OAuth setup step is vague — "(from initial auth flow)" gives no runnable command even though scripts/ga4_auth.py ships in the bundle and is never referenced.	4 / 5
Workflow Clarity	Setup is a numbered sequence with an explicit validation checkpoint ("python3 scripts/ga4_query.py --metric sessions --dimension date --limit 1"), stated success/failure criteria, and a Troubleshooting section that closes the validate→fix→retry loop; queries are read-only so the destructive/batch cap does not apply.	5 / 5
Progressive Disclosure	Sections are well organized, the query script path is referenced consistently, and there are no nested references, but scripts/ga4_auth.py exists in the bundle and is never linked — "Re-run the OAuth flow" in Troubleshooting leaves Claude without a path to the flow it is told to re-run.	4 / 5
	Total	18 / 20 Passed

Description

92%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 strong description that clearly and explicitly states both what the skill does and when to use it, with concrete domain-specific capability terms and low conflict risk. The only weakness is modest keyword coverage of everyday analytics vocabulary (e.g., "pageviews", "visitors") beyond the GA4-native metric names.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "Query Google Analytics 4 (GA4) data via the Analytics Data API", "top pages, traffic sources, user counts, sessions, conversions", "custom date ranges and filtering" — with comprehensive coverage of the domain and no significant gaps.	5 / 5
Completeness	Explicitly answers both questions: the "what" ("Query Google Analytics 4 (GA4) data via the Analytics Data API") and the "when" ("Use when you need to pull website analytics like top pages, traffic sources, user counts...") with concrete trigger phrases.	5 / 5
Trigger Term Quality	Covers the full name and acronym ("Google Analytics 4 (GA4)") plus natural user phrasings like "top pages", "traffic sources", and "website analytics", but omits common layman terms such as "pageviews", "visitors", or "traffic report" that users would most often say.	4 / 5
Distinctiveness Conflict Risk	The GA4/Analytics Data API niche is unambiguous and the triggers ("GA4", "traffic sources", "conversions") are distinct from generic analytics or database skills, so conflict risk is minimal.	5 / 5
	Total	19 / 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
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: bap-jorkim/agent-skills-fork-feb-25
Path: skills/ga4/SKILL.md
Commit: f4ed46f

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