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

70

Quality

87%

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

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

A thorough, actionable reference with executable examples and clear sequencing that largely respects the reader's intelligence. Its main limitation is monolithic inline detail that, with bundle files, could be split for better progressive disclosure.

Suggestions

Move the lengthy Default Baseline Events and Referral/attribution reference into a dedicated reference file (e.g. references/baseline-events.md) and summarize it in SKILL.md to improve progressive disclosure.

Tighten the dense http.response and attribution parameter prose into compact tables or bullet summaries to recover token budget.

Add a short 'Quick start' snippet near the top showing the minimal set-env-var-and-track path before the full API reference.

DimensionReasoningScore

Conciseness

Efficient and assumes Claude's competence without explaining basics, though some dense prose blocks (attribution params, http.response telemetry) could be tightened without losing meaning.

4 / 5

Actionability

Copy-paste-ready code for track/identify/register, an env-var table per provider, concrete TypeScript interfaces, and exact file paths cover the common cases fully.

5 / 5

Workflow Clarity

'How It Works' gives a clear 4-step startup→call→fan-out→batch sequence, and error-capture guidance provides feedback loops; not a destructive/batch workflow requiring validation checkpoints, so minor gaps are acceptable.

4 / 5

Progressive Disclosure

Well-organized sections with a Key Files table and Related Skills pointers, but no bundle files exist to offload the large inline reference material, leaving some content that could live in separate files.

4 / 5

Total

17

/

20

Passed

Description

92%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 concretely names capabilities and gives explicit trigger guidance with specific provider names, making it clearly distinguishable. Only minor room for more colloquial trigger phrasing.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ('adding analytics events', 'registering custom tracking providers', 'configuring built-in providers (PostHog, Mixpanel, Amplitude, Webhook)') with comprehensive coverage of the skill's surface.

5 / 5

Completeness

Explicitly states what the skill does ('Server-side analytics tracking with pluggable providers') and when to use it via a concrete 'Use when adding analytics events, registering custom tracking providers, or configuring built-in providers' clause.

5 / 5

Trigger Term Quality

Good natural terms like 'analytics events' and 'tracking providers' plus named backends, but 'pluggable providers' and 'server-side analytics tracking' lean technical and a few common synonyms are absent.

4 / 5

Distinctiveness Conflict Risk

Clear niche (server-side analytics only) anchored by named providers and 'server-side only' scope, giving it distinct triggers with minimal overlap risk against other skills.

5 / 5

Total

19

/

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.

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.