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.
91
89%
Does it follow best practices?
Impact
99%
1.80xAverage score across 3 eval scenarios
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description that clearly identifies the tool (GA4 Analytics Data API), lists specific capabilities (top pages, traffic sources, user counts, sessions, conversions), and provides explicit trigger guidance with a 'Use when' clause. The description is concise, uses third person voice, and includes natural keywords that users would employ when requesting analytics data.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'pull website analytics like top pages, traffic sources, user counts, sessions, conversions' and mentions 'custom date ranges and filtering' as additional capabilities. | 3 / 3 |
Completeness | Clearly answers both what ('Query GA4 data via the Analytics Data API, supports custom date ranges and filtering') and when ('Use when you need to pull website analytics like top pages, traffic sources, user counts, sessions, conversions, or any GA4 metrics/dimensions'). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'Google Analytics', 'GA4', 'top pages', 'traffic sources', 'user counts', 'sessions', 'conversions', 'metrics', 'dimensions', 'website analytics'. These are all terms a user would naturally use when requesting analytics data. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with clear niche targeting Google Analytics 4 specifically via the Analytics Data API. The combination of 'GA4', 'Analytics Data API', and specific metric types makes it very unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
79%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured, concise skill that provides immediately actionable CLI commands for querying GA4 data. Its main weaknesses are the lack of error handling/validation guidance (what happens when auth fails or queries return empty results?) and the absence of any reference to the underlying script's location or the full GA4 API docs for advanced use cases.
Suggestions
Add a brief troubleshooting/validation section covering common failure modes: invalid property ID, expired refresh token, empty results—with how to diagnose each.
Link to the ga4_query.py script location and/or the GA4 API dimension/metric reference for users who need less common fields.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. It doesn't explain what GA4 is or how analytics work—it assumes Claude knows. Every section serves a purpose: setup, common queries with executable commands, and reference lists for metrics/dimensions. | 3 / 3 |
Actionability | Every query example is a concrete, copy-paste-ready bash command with specific flags and values. The setup section lists exact environment variables needed. Metrics and dimensions are listed by their exact API names. | 3 / 3 |
Workflow Clarity | The setup steps are clear and sequential, and the query examples are straightforward single-step commands. However, there's no validation or error handling guidance—no mention of what to do if authentication fails, if the property ID is wrong, or how to verify the query returned expected results. | 2 / 3 |
Progressive Disclosure | The content is well-organized with clear sections, but it references a script (scripts/ga4_query.py) without linking to its source or documentation. The metrics and dimensions lists are inline but could benefit from a reference to the full GA4 API documentation for discovery of less common options. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
metadata_field | 'metadata' should map string keys to string values | Warning |
Total | 9 / 11 Passed | |
6768672
Table of Contents
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.