CtrlK
BlogDocsLog inGet started
Tessl Logo

analytics-tracking

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

54

Quality

61%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/analytics-tracking/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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.

The body is a well-structured, actionable measurement framework with a clear gated workflow, but it is a long monolithic file with some redundant phrasing and no progressive disclosure into reference files.

Suggestions

Move tool-specific implementation detail (GA4/GTM section) and the full event taxonomy into separate reference files, linking to them from SKILL.md.

Trim repetition between the Core Principles section and the index category definitions to improve token efficiency.

Add an explicit post-implementation validation loop (validate -> fix -> re-score the readiness index) to lift workflow clarity toward 5.

DimensionReasoningScore

Conciseness

Mostly efficient bullet-list structure, but the Core Principles section repeats guidance already encoded in the index categories and the 'You do not track everything' framing is restated several times, so it could be tightened.

3 / 5

Actionability

Provides concrete event taxonomy, a naming pattern with worked examples, property rules, and a required output-format table; as an instruction-only skill the guidance is actionable with only minor gaps.

4 / 5

Workflow Clarity

Clear Phase 0 -> Phase 1 sequence with the Measurement Readiness Index acting as an explicit gate ('If verdict is Broken, stop and recommend remediation first') and a required output format; minor validation gaps keep it below 5.

4 / 5

Progressive Disclosure

Well-sectioned but ~400 lines all inlined in one file with no bundle references; tool-specific guidance (GA4/GTM) and the event taxonomy reference could live in separate files, so it is not fully split.

3 / 5

Total

14

/

20

Passed

Description

58%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.

The description is specific and names a clear niche, but it lacks an explicit 'Use when' trigger clause and natural user keywords (GA4, GTM, conversions), which limit its completeness and trigger quality.

Suggestions

Add a 'Use when...' clause naming concrete trigger situations (e.g., setting up or auditing GA4/GTM tracking, fixing unreliable conversion data).

Include natural user-facing keywords and synonyms such as GA4, GTM, conversions, UTMs, and event tracking.

Mention the output artifact (a tracking plan / measurement-readiness score) so users can recognize when they need this skill.

DimensionReasoningScore

Specificity

Lists three concrete actions ('Design, audit, and improve') on a named domain (analytics tracking systems); minor gaps in coverage versus the comprehensive multi-action anchor at 5.

4 / 5

Completeness

Clearly states what the skill does but provides no 'Use when...' clause or equivalent trigger guidance, which per the rubric caps completeness at 3.

3 / 5

Trigger Term Quality

'analytics tracking systems' is a relevant keyword but the description omits natural user phrases like GA4, GTM, conversions, UTMs, or 'set up tracking' that users would actually say.

3 / 5

Distinctiveness Conflict Risk

The analytics-tracking niche is fairly distinct with minor overlap risk only against closely related skills like ab-test-setup or page-cro.

4 / 5

Total

14

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
sickn33/antigravity-awesome-skills
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.