CtrlK
BlogDocsLog inGet started
Tessl Logo

analytics-tracking

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

72

1.18x
Quality

60%

Does it follow best practices?

Impact

95%

1.18x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills/skills/analytics-tracking/SKILL.md

The canonical home for this skill is analytics-tracking in sickn33/agentic-awesome-skills

SKILL.md
Quality
Evals
Security

Quality

Content

67%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 content is a well-structured, actionable analytics-measurement playbook with a clear phased workflow and concrete taxonomies, though it is somewhat long and repeats itself between the scoring index and core principles. Progressive disclosure is reasonable but all material is inlined with no reference files.

Suggestions

Deduplicate the overlap between the 'Measurement Readiness & Signal Quality Index' categories and the 'Core Principles' section to tighten token use.

Make the validation phase an explicit validate->fix->retry loop with concrete checks rather than a list of failure modes.

Move the GA4/GTM implementation guidance and detailed event taxonomy into reference files (e.g., references/ga4-gtm.md, references/event-taxonomy.md) with one-level-deep links from SKILL.md.

DimensionReasoningScore

Conciseness

The body is mostly lean bullet lists but repeats concepts (the Phase 0 scoring categories are restated as 'Core Principles') and the readiness-index section could be tightened; some redundancy keeps it below a 4.

3 / 5

Actionability

Provides concrete, executable guidance: an event taxonomy, the 'object_action[_context]' naming pattern with examples, property include/avoid lists, conversion rules, and output tables; only minor gaps prevent a 5.

4 / 5

Workflow Clarity

Clear phased sequence (Phase 0 scoring -> Phase 1 context -> design -> validation -> output) with checkpoints like "Proceed only after scoring" and "If verdict is Broken, stop"; not a 5 because feedback loops are lightly specified rather than explicit validate->fix->retry cycles.

4 / 5

Progressive Disclosure

Well-organized with clear section headers and no nested references (no bundle files exist), but the ~400-line monolith inlines GA4/GTM and event-taxonomy material that could live in reference files; stops short of the clean one-level-deep split of a 5.

4 / 5

Total

15

/

20

Passed

Description

53%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 clearly states what the skill does but lacks an explicit 'when to use' trigger and relies on generic action verbs, with moderate but incomplete keyword coverage. It is distinct enough to avoid most conflicts.

Suggestions

Add a 'Use when...' clause with concrete trigger phrases (e.g., 'Use when designing or auditing analytics tracking, event taxonomies, GA4/GTM instrumentation, or conversion definitions').

Replace abstract verbs with specific actions and surface natural terms users say, such as 'tracking plan', 'events', 'conversions', and tool names like GA4 and GTM.

Include synonyms/file-format-style triggers to broaden keyword coverage toward the comprehensive anchor.

DimensionReasoningScore

Specificity

Quotes "Design, audit, and improve analytics tracking systems" name the domain and three actions, but the verbs are high-level and abstract rather than concrete like 'extract text, fill forms'; not comprehensive enough for a 4.

3 / 5

Completeness

Provides a clear 'what' ("Design, audit, and improve analytics tracking systems") but no 'Use when...' trigger clause; per the rubric a missing explicit trigger caps completeness at 3.

3 / 5

Trigger Term Quality

Contains 'analytics tracking systems' and 'decision-ready data' but omits natural user phrases and tool names (GA4, GTM, events, conversions, tracking plan) users would actually say; missing common synonyms.

3 / 5

Distinctiveness Conflict Risk

The niche ('analytics tracking systems that produce reliable, decision-ready data') is mostly distinct with only minor overlap risk against broader analytics or data-quality skills; not fully a 5 due to that adjacency.

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.

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
administrakt0r/AI-Agents-Safe-Coding-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.