CtrlK
BlogDocsLog inGet started
Tessl Logo

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).

71

Quality

88%

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

SKILL.md
Quality
Evals
Security

Quality

Content

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-organized, actionable reference with executable code and a clear process sequence, weakened mainly by a verbose inline events catalog that would benefit from progressive disclosure into a separate reference file.

Suggestions

Move the long 'Default Baseline Events' catalog (event field listings, attribution params) into a separate reference file and keep SKILL.md as an overview pointing to it.

Tighten the dense $ai_generation and http.response field lists, removing duplicate attribution fields already covered in the 'Referral / viral attribution' section.

Add a one-line cross-link under each built-in provider to its config/secret details so the table stays scannable.

DimensionReasoningScore

Conciseness

The API section is lean with executable code, but the 'Default Baseline Events' catalog is a dense field dump (utm_*, $ai_* fields) with attribution fields restated, and could be tightened or split out rather than inlined.

2 / 3

Actionability

Provides fully executable TypeScript with imports, concrete env var tables, exact file paths, and copy-paste-ready examples across all API entry points.

3 / 3

Workflow Clarity

The 'How It Works' section gives a clear numbered fan-out sequence; the fire-and-forget analytics calls are not destructive/batch operations requiring validation checkpoints, so the unambiguous single process scores 3.

3 / 3

Progressive Disclosure

The body is well-sectioned but monolithic at ~208 lines with no bundle files; the lengthy baseline-events catalog is inline content that could be separated into a reference file rather than kept in the overview.

2 / 3

Total

10

/

12

Passed

Description

100%

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, third-person description that names concrete actions, lists natural trigger terms including specific providers, and gives an explicit 'Use when' clause covering both what and when. It is concise without padding.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'adding analytics events, registering custom tracking providers, or configuring built-in providers' — matching the score-3 anchor rather than the partial score-2 anchor.

3 / 3

Completeness

Explicitly states what it does ('Server-side analytics tracking with pluggable providers') and when to use it via a clear 'Use when...' clause, answering both halves.

3 / 3

Trigger Term Quality

Uses natural developer terms ('analytics events', 'tracking') plus the exact provider names (PostHog, Mixpanel, Amplitude, Webhook) a user would mention, giving strong keyword coverage.

3 / 3

Distinctiveness Conflict Risk

Scoped to 'server-side analytics tracking' with provider-specific triggers, forming a clear niche unlikely to overlap with unrelated skills.

3 / 3

Total

12

/

12

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.

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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

13

/

16

Passed

Repository
BuilderIO/agent-native
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.