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.
72
58%
Does it follow best practices?
Impact
99%
1.26xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/all-skills/skills/google-analytics-automation/SKILL.mdQuality
Discovery
67%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 strong on specificity and distinctiveness, clearly naming the tool integration and listing concrete actions. However, it lacks an explicit 'Use when...' clause, which limits completeness, and the trigger terms could be expanded to include more natural user language like 'GA4', 'traffic', or 'conversions'.
Suggestions
Add a 'Use when...' clause such as 'Use when the user asks about Google Analytics data, GA4 reports, website traffic, conversions, or analytics account management.'
Include common user-facing trigger terms like 'GA4', 'website traffic', 'page views', 'conversions', 'analytics data' to improve discoverability from natural user requests.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'run reports, list accounts/properties, funnels, pivots, key events' and includes the operational instruction to 'search tools first for current schemas.' | 3 / 3 |
Completeness | Clearly answers 'what does this do' with specific actions, but lacks an explicit 'Use when...' clause or equivalent trigger guidance explaining when Claude should select this skill. | 2 / 3 |
Trigger Term Quality | Includes relevant terms like 'Google Analytics', 'reports', 'accounts', 'properties', 'funnels', 'pivots', 'key events', but misses common user variations like 'GA4', 'analytics data', 'traffic', 'page views', 'conversions', or 'metrics'. Also 'Rube MCP (Composio)' is technical jargon unlikely to be used by end users. | 2 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to Google Analytics via a specific MCP integration (Rube/Composio), making it highly distinctive and unlikely to conflict with other analytics or reporting skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a competent reference skill that covers GA4 workflows comprehensively with clear tool sequences and useful pitfall documentation. Its main weaknesses are significant repetition (property ID format and date ranges mentioned 3+ times), lack of executable examples showing actual tool call structures, and missing validation/error-recovery steps in workflows. Trimming redundancy and adding concrete invocation examples would substantially improve it.
Suggestions
Consolidate repeated pitfalls (property ID format, date ranges, compatibility) into a single 'Common Pitfalls' section and reference it from workflows instead of duplicating across sections.
Add at least one concrete, copy-paste-ready tool invocation example showing exact parameter structure (e.g., a complete RUBE_SEARCH_TOOLS call followed by a RUN_REPORT call with real JSON parameters).
Add explicit validation/error-recovery steps to workflows—e.g., 'If CHECK_COMPATIBILITY returns incompatible, remove the flagged dimension and retry' or 'If report returns no rows key, verify property ID and date range'.
Consider splitting the detailed per-workflow parameter lists and pitfalls into a separate REFERENCE.md file, keeping SKILL.md as a concise overview with the quick reference table and common patterns.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably well-structured but contains significant repetition—pitfalls about property ID format and date ranges are repeated across multiple sections and again in the 'Known Pitfalls' summary. Some sections explain things Claude would know (e.g., what pagination is). The content could be ~30-40% shorter without losing information. | 2 / 3 |
Actionability | Tool names and parameter lists are concrete and useful, but there are no executable code examples—the 'Common Patterns' section uses pseudocode-style numbered steps rather than actual tool invocation examples with real parameter structures. Claude would need to call RUBE_SEARCH_TOOLS anyway to get schemas, so the parameter descriptions are somewhat redundant without showing exact call formats. | 2 / 3 |
Workflow Clarity | Workflows are clearly sequenced with labeled steps and prerequisite/required annotations, which is good. However, there are no validation checkpoints or error recovery steps—e.g., no guidance on what to do if a report returns empty results, if compatibility check fails, or if batch reports partially fail. The skill mentions pitfalls but doesn't integrate them into feedback loops. | 2 / 3 |
Progressive Disclosure | The content is well-organized with clear sections and a quick reference table, but it's monolithic at ~200+ lines with no bundle files to offload detail into. The detailed pitfalls, common patterns, and per-workflow parameter lists could be split into separate reference files. The single external link to Composio docs is appropriate but insufficient for the volume of inline content. | 2 / 3 |
Total | 8 / 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 |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- davepoon/buildwithclaude
- Commit
d065ead
- 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.