CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

tracking

Server-side analytics tracking with pluggable providers. Use when adding analytics events, registering custom tracking providers, or configuring built-in providers (PostHog, Mixpanel, Amplitude, Webhook).

Quality

75%

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

Quality

Content

56%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 highly actionable for the core tasks (API usage, provider configuration, custom provider registration) with executable code and specific file-level rules. Its main weakness is scale: a monolithic 545-line file inlines deep operational detail (consent, noise filtering, event schemas) that belongs in reference files, costing token efficiency and progressive disclosure.

Suggestions

Move the Error Capture, Cookie consent, MCP Server Events, and Default Baseline Events sections into separate reference files (e.g. references/error-capture.md, references/consent.md) and keep one-line pointers with "See X when..." triggers in SKILL.md.

Tighten the long bullets (e.g. "Browser outcomes are bounded, too", "Rates are events, not log lines") into short rule statements plus property tables, cutting run-on edge-case narration.

Lead with a short Quick Start (set one env var, call track()) before the API section so the common path is reachable without reading the full document.

DimensionReasoningScore

Conciseness

The body runs ~545 lines of dense edge-case prose, e.g. the enormous "Browser outcomes are bounded, too" bullet and the multi-paragraph cookie-consent section detailing sampling rates, cookie attributes, and Consent Mode mechanics. It never explains generic concepts Claude already knows (so not 1), but the sheer volume of inlined detail is noticeably verbose even though accurate.

2 / 5

Actionability

Executable, import-bearing code for track(), identify(), and registerTrackingProvider(), env-var tables with defaults, and concrete rules like "update both server/posthog-config.ts and the mirrored worker emitter in deploy/build.ts". Below 5 because large sections (baseline event property catalogs, MCP event tables) are descriptive schemas rather than copy-paste-ready guidance.

4 / 5

Workflow Clarity

"How It Works" gives a clear 4-step startup-to-fan-out sequence, and verification hooks exist ("posthog-config.spec.ts pins the two outputs together", "check what an event looks like in its UI, not just that the request returned 200"). Below 5 because mandated multi-file edits lack an explicit validate-and-retry loop; the destructive/batch cap does not apply since tracking is non-destructive.

4 / 5

Progressive Disclosure

No bundle files exist; ~400 lines of error-capture, cookie-consent, MCP-event, and baseline-event detail that clearly belongs in separate reference files are inlined in SKILL.md. Scored above 2 because the file does have consistent, well-named section headers throughout, giving real structure — but nothing is split out or referenced one level deep.

3 / 5

Total

13

/

20

Passed

Description

87%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 a strong example: it states what the skill does in one clause and gives three explicit 'Use when' triggers naming concrete providers. Minor gaps in capability coverage (identify, consent, error capture) and a few missing synonyms like "telemetry" keep it just short of perfect on specificity and trigger terms.

Suggestions

Mention one or two more capabilities such as user identify() or error capture to close the specificity gap.

Add the synonym "telemetry" and a phrase like "event tracking" to the trigger list for broader natural-term coverage.

DimensionReasoningScore

Specificity

"adding analytics events, registering custom tracking providers, or configuring built-in providers (PostHog, Mixpanel, Amplitude, Webhook)" lists several concrete actions with named providers. Not 5 because coverage has gaps (identify, error capture, consent, browser tracking are unmentioned); not 3 because it names three specific actions rather than 1-2.

4 / 5

Completeness

"Server-side analytics tracking with pluggable providers" answers what, and "Use when adding analytics events, registering custom tracking providers, or configuring built-in providers" explicitly answers when with three concrete trigger phrases. This matches the 5 anchor; the when clause is specific, so the 4 anchor ("'when' could be more explicit") does not fit.

5 / 5

Trigger Term Quality

"analytics events", "tracking", "PostHog", "Mixpanel", "Amplitude" are natural phrases a user would say when needing this skill. A few natural synonyms are missing (e.g. "telemetry", "event tracking", "identify users"), keeping it below the comprehensive 5 anchor.

4 / 5

Distinctiveness Conflict Risk

"Server-side analytics tracking" with named providers (PostHog, Mixpanel, Amplitude, Webhook) carves out a clear niche with distinct triggers, so it is unlikely to fire for the wrong skill. Distinct from adjacent skills like general error handling or secrets.

5 / 5

Total

18

/

20

Passed

Validation

75%

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

Validation — 12 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (557 lines); consider splitting into references/ and linking

Warning

metadata_version

'metadata.version' is missing

Warning

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

Total

12

/

16

Passed

Repository

BuilderIO/agent-native

Path

.agents/skills/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.