feb-25-workspace/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.
93
Quality
93%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
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 an excellent skill description that hits all the marks. It clearly identifies the specific platform (GA4), lists concrete capabilities users would request, includes an explicit 'Use when' clause with natural trigger terms, and is distinctive enough to avoid conflicts with other skills.
| 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 capabilities. | 3 / 3 |
Completeness | Clearly answers both what ('Query Google Analytics 4 data via the Analytics Data API') and when ('Use when you need to pull website analytics like...') with explicit trigger guidance and specific use cases. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'Google Analytics', 'GA4', 'website analytics', 'top pages', 'traffic sources', 'user counts', 'sessions', 'conversions', 'metrics', 'dimensions' - all terms users naturally use when requesting analytics data. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with clear niche - specifically targets GA4/Google Analytics with unique triggers like 'GA4', 'Analytics Data API', and analytics-specific terms that wouldn't overlap with general data or reporting skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, well-crafted skill that excels at conciseness and actionability. The executable command examples cover common use cases effectively. The main weakness is the setup section lacks validation steps to confirm credentials and property ID are working before running queries.
Suggestions
Add a validation step after setup, e.g., 'Test your setup: python3 scripts/ga4_query.py --metric sessions --dimension date --limit 1' with expected success/failure output
Include brief troubleshooting for common auth errors (invalid refresh token, wrong property ID format)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. No unnecessary explanations of what GA4 is or how APIs work. Every section provides direct, actionable information without padding. | 3 / 3 |
Actionability | Provides fully executable, copy-paste ready bash commands for all common use cases. Includes specific flags, example values, and clear parameter patterns. | 3 / 3 |
Workflow Clarity | Setup steps are listed but lack validation checkpoints. No guidance on verifying credentials work, handling auth errors, or confirming the property ID is correct before running queries. | 2 / 3 |
Progressive Disclosure | Well-organized with clear sections progressing from setup to common queries to reference lists. Appropriate length for a single file; no need for external references given the scope. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
Total | 10 / 11 Passed | |
Install with Tessl CLI
npx tessl i feb-25-workspace/ga4Reviewed
Table of Contents