CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

analytics-tracking

Compatibility pointer for GA4 event, key-event and User-ID tracking; maintained in Open Analytics.

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

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

Quality

Content

92%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 an exemplary minimal redirect: lean, unambiguous about its moved status, and actionable via a concrete install command and a clearly signaled one-level-deep link. The only gap is the absence of an explicit instruction to defer to the successor's instructions when this skill triggers. For its purpose as a compatibility pointer, the content is strong.

DimensionReasoningScore

Conciseness

The body is two lean sentences under a single heading — a link, an install command, and a one-line scope statement. Every token earns its place; nothing explains concepts Claude already knows. This matches the 'Lean and efficient' anchor.

5 / 5

Actionability

It provides a concrete copy-paste-ready command ('npx skills add kostja94/open-analytics --skill analytics-tracking') and a direct link to the maintained instructions, which is mostly executable guidance. Not 5 because it never explicitly instructs Claude to follow or defer to the successor when this skill triggers — the redirect is implied rather than stated.

4 / 5

Workflow Clarity

This is a simple single-purpose skill and its single action — fetch the maintained instructions or install the successor — is unambiguous, satisfying the simple-skill exception. The body also explicitly states 'contains no independent tracking rules', so there is no ambiguity about whether to act on this file's content.

5 / 5

Progressive Disclosure

The skill is well under 50 lines, has no bundle files, and needs no external references; per the simple-skill guidance this alone qualifies for 5. The one reference present (the GitHub link to the successor) is clearly signaled and exactly one level deep.

5 / 5

Total

19

/

20

Passed

Description

56%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 honestly signals the skill's moved status and covers a specific GA4 niche with natural keywords, but it describes no concrete actions and lacks any 'Use when...' trigger guidance, leaving it below the quality bar for discoverability. As a compatibility pointer it is serviceable, yet it would serve users better by naming what the successor actually does and when it should be used.

Suggestions

Add an explicit 'Use when...' clause (e.g., 'Use when the user asks about GA4 events, key events/conversions, or User-ID tracking') so the skill has concrete trigger guidance.

Describe the concrete capabilities the maintained skill provides (e.g., 'implement GA4 event tracking, configure key events/conversions, and set up User-ID reporting') instead of only naming the domain.

Include common synonyms such as the spelled-out 'Google Analytics 4', 'conversions', and 'gtag' so natural-language triggers match more reliably.

DimensionReasoningScore

Specificity

The description names the domain richly ("GA4 event, key-event and User-ID tracking") but the only stated action is being a "Compatibility pointer" — no concrete capability verbs are listed at all, matching the anchor 'Names the domain but actions are minimal or generic'. It does not reach 3 because no concrete actions like implementing, configuring, or debugging tracking are described.

2 / 5

Completeness

The 'what' is stated — a compatibility pointer for GA4 tracking whose maintained version lives in Open Analytics — but there is no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines. It is not 2 because the 'what' is clear and specific rather than vague.

3 / 5

Trigger Term Quality

"GA4 event, key-event and User-ID tracking" provides five natural practitioner terms (GA4, event, key-event, User-ID, tracking) with density comparable to the anchor-4 example. It falls short of 5 because common synonyms like the spelled-out "Google Analytics 4", "conversions", and "gtag" are missing.

4 / 5

Distinctiveness Conflict Risk

GA4 key-event and User-ID tracking is a clear niche with distinct triggers, so it is mostly distinct with only minor overlap risk against general web-analytics or gtag skills. Not 5, because without explicit trigger phrasing it could still fire for adjacent analytics questions it no longer answers.

4 / 5

Total

13

/

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

kostja94/marketing-skills

Path

skills/analytics/tracking/SKILL.md

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.