analytics-tracking

Design, audit, and improve analytics tracking systems that produce reliable, decision-ready data.

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

62%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The skill has strong workflow sequencing with explicit validation gates and a useful diagnostic index, but it is hurt by verbosity, vague implementation sections, and a monolithic structure with no progressive disclosure. Tightening the GA4/GTM and validation sections and splitting reference material into bundle files would raise the weaker dimensions.

Suggestions

Replace vague GA4/GTM and Validation bullets with concrete, executable steps (e.g., specific GTM dataLayer push examples, GA4 DebugView checks, duplicate-firing detection commands).

Move the event taxonomy, GA4/GTM implementation guidance, and output-format templates into separate reference files under references/, linked one level deep from the overview.

Cut repetition between the scoring index category definitions and the Core Principles section, and remove the generic 'When to Use' boilerplate in favor of the body's existing guidance.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean bullet lists, but it repeats concepts across the scoring index and Core Principles and includes generic filler like 'This skill is applicable to execute the workflow or actions described in the overview.'	2 / 3
Actionability	It gives concrete naming patterns, an event taxonomy, and output table templates, but the GA4/GTM and Validation sections stay vague ('Push clean dataLayer events', 'Real-time verification') with no executable steps.	2 / 3
Workflow Clarity	A clearly sequenced phased process (Phase 0 scoring → Phase 1 context → design → required output) with explicit gating checkpoints — 'Proceed only after scoring' and 'If verdict is Broken, stop and recommend remediation first.'	3 / 3
Progressive Disclosure	Sections are well-organized with headers, but it is a monolithic ~400-line file with no bundle references; content like GA4/GTM implementation guidance and the event model could be split into separate reference files.	2 / 3
	Total	9 / 12 Passed

Description

60%

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 specific and action-oriented in third person, but it is missing an explicit 'Use when…' trigger and natural keyword variations, which weakens completeness and trigger quality. Adding trigger guidance would lift two of the four dimensions.

Suggestions

Append an explicit trigger clause, e.g. 'Use when designing or auditing analytics tracking, event plans, GA4/GTM instrumentation, or conversion definitions.'

Add natural keyword variations users actually say (GA4, GTM, tracking plan, conversion events, attribution) to improve trigger-term coverage.

Sharpen distinctiveness by contrasting with sibling skills (e.g. '...measurement design — not CRO testing or SEO analysis').

Dimension	Reasoning	Score
Specificity	The description lists three concrete actions — 'Design, audit, and improve analytics tracking systems' — matching the anchor for multiple specific concrete actions.	3 / 3
Completeness	It states what the skill does but lacks any explicit 'Use when…' trigger clause, capping completeness at 2 per the judging guidelines.	2 / 3
Trigger Term Quality	It includes relevant terms ('analytics tracking systems', 'decision-ready data') but omits common variations users would say (GA4, GTM, tracking plan, events), so coverage is partial.	2 / 3
Distinctiveness Conflict Risk	The measurement-design niche is somewhat specific, but without explicit triggers it could overlap with sibling analytics skills (page-cro, ab-test-setup, seo-audit).	2 / 3
	Total	9 / 12 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: boisenoise/skills-collections
Commit: f36337d

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