CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

rum-tracking

Guides product analytics and RUM event tracking in web and React Native apps — what to capture, what is noise or PII, naming, tracking plans, compliance, and clean implement / audit / remove. Triggers on "track this event", "add analytics", "what should I track", "is this PII", "/rum-tracking".

Quality

78%

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/analysis/rum-tracking/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

66%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 SKILL.md body is an exemplarily structured thin index: clear mode detection, well-sequenced per-mode workflows with explicit gates and a Definition of Done, and lean one-liner principles with no padding. Its critical weakness is that the bundle ships only 2 of the 14 files it references — all rules/*.md and templates/* are missing — so the progressive-disclosure structure and the per-mode workflows dead-end on execution, leaving the detailed guidance (PII gate, implementation rules, wrapper template) undeliverable.

Suggestions

Ship the referenced bundle files: add the 10 rules/*.md files (what-to-track, pii-and-compliance, implementation-web/mobile, etc.) and both templates/* files (analytics-wrapper.template.ts, tracking-plan.template.yaml) — without them every mode's first step fails and progressive disclosure is non-functional.

Add one small inline executable example in implement mode (e.g., a minimal typed track() call through the centralized wrapper) so the skill retains actionable guidance even before the referenced files load.

De-duplicate the file lists: either drop the 'Required Reading by Mode' table or remove the per-mode file references from 'Workflow by Mode', keeping one canonical navigation path.

DimensionReasoningScore

Conciseness

The body is an efficient thin index with no concept-explanation padding (no 'what is RUM' filler), dense one-liner principles and anti-patterns, and every section serving navigation. Minor trims possible: the "Required Reading by Mode" table duplicates the per-mode file lists already given in "Workflow by Mode", and the external-dependency callout ("and otherwise skips them with a one-line report, never silently") is wordy — matching anchor 4's 'minor instances that could be trimmed', not anchor 3's unnecessary explanation.

4 / 5

Actionability

Process guidance is specific ("gate the user before writing instrumentation", "≤ 30 event names", named codegen tools "Avo, RudderTyper, Typewriter", "Mark deprecated first, set a sunset date"), but the body contains no executable code or commands and delegates all concrete payloads to files that are missing from the bundle — following "Load rules/what-to-track.md" (step 1 of guide mode) or the wrapper template dead-ends. This matches anchor 3: concrete guidance present but incomplete, key details missing; it exceeds anchor 2's 'high-level hints only' but falls short of anchor 4's 'concrete code or commands with minor gaps'.

3 / 5

Workflow Clarity

Each of the five modes has a numbered sequence with explicit conditional branches and validation checkpoints: "gate the user before writing instrumentation", "Run the PII gate ... on every property before the diff is final", "Identify downstream consumers ... before deletion", "do not auto-edit unless the user approved a pre-defined audit scope", plus mode detection with a stated default and a Definition of Done checklist. The destructive remove mode is properly guarded (deprecate → check consumers → delete), so the destructive-operation cap does not apply; this matches anchor 5's 'explicit validation steps ... checklists for complex processes' rather than anchor 4, which reserves room for missing checkpoints that are not missing here.

5 / 5

Progressive Disclosure

The index design itself is well-signaled and one level deep (SKILL.md → rules/references/templates, with a per-mode loading table), but scored against the actual bundle only 2 of the 14 referenced paths exist (references/event-catalog.md, references/platforms.md); all 10 rules/*.md files and both templates/* files are absent, so every mode's step-1 load fails and the structure is non-functional as shipped. This is a navigation failure of comparable severity to anchor 2 — 'references are buried'/minimal functional structure — rather than anchor 3's mere organizational improvement, and well below anchor 4's 'references mostly clear' because most references do not resolve at all.

2 / 5

Total

14

/

20

Passed

Description

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

A strong description that clearly and explicitly states both scope (what to capture, PII filtering, naming, tracking plans, compliance, implement/audit/remove across web and React Native) and concrete trigger phrases. Its only weaknesses are minor: a few missing natural trigger synonyms (instrument, telemetry, vendor names) and one cross-domain trigger ("is this PII") with slight conflict risk against general privacy skills.

DimensionReasoningScore

Specificity

"what to capture, what is noise or PII, naming, tracking plans, compliance, and clean implement / audit / remove" enumerates several concrete capability areas across named platforms (web and React Native), matching the 'lists several specific actions; minor gaps' anchor. Held below 5 because the actions stay at the 'guides/decides' level rather than fully concrete operations, and no per-platform actions (e.g., instrumenting a React component) are named.

4 / 5

Completeness

Explicitly answers both: what — "Guides product analytics and RUM event tracking in web and React Native apps — what to capture, what is noise or PII, naming, tracking plans, compliance, and clean implement / audit / remove" — and when — "Triggers on 'track this event', 'add analytics', 'what should I track', 'is this PII', '/rum-tracking'" with concrete trigger phrases. This matches the anchor-5 example structure exactly, and the score-4 anchor ("'when' could be more explicit") clearly does not apply.

5 / 5

Trigger Term Quality

The quoted triggers "track this event", "add analytics", "what should I track", "is this PII" are natural phrases users would actually say, plus domain keywords (RUM, product analytics, PII, tracking plans). Below 5 because common variations are missing: "instrument", "telemetry", "deprecate/delete this event", "audit analytics", and vendor names (Mixpanel, PostHog, Amplitude).

4 / 5

Distinctiveness Conflict Risk

A clear niche (RUM/product-analytics event tracking) with mostly domain-specific triggers gives low conflict risk. Below 5 because the standalone trigger "is this PII" would also fire on general privacy/GDPR questions unrelated to analytics, creating minor overlap risk with a dedicated privacy/compliance skill — the score-4 anchor's 'minor overlap risk with closely related skills'.

4 / 5

Total

17

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

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

Warning

relative_links

Relative link issues: 35 missing

Warning

Total

13

/

16

Passed

Repository

mthines/agent-skills

Path

skills/analysis/rum-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.