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

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

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

Highly actionable content with executable examples and concrete configuration detail, organized into clear sections. The main weakness is progressive disclosure: with no bundle files, lengthy reference enumerations live inline in SKILL.md rather than in dedicated reference files.

Suggestions

Move the MCP event property enumeration and the lifecycle event taxonomy into separate reference files (e.g. references/mcp-events.md, references/lifecycle-taxonomy.md) and link to them from SKILL.md to improve progressive disclosure.

Trim or tabularize the exhaustive per-event property lists to reduce token cost while keeping the most-used fields inline.

Add a brief executable example for flushTracking() and the browser-side trackEvent() path to close the small actionability gaps.

Dimension	Reasoning	Score
Conciseness	Dense and free of padding about basic concepts, with most tokens earning their place, but the exhaustive inline property lists (MCP events, lifecycle taxonomy) could be trimmed for token efficiency.	4 / 5
Actionability	Copy-paste-ready code examples with real imports and signatures for track(), identify(), and registerTrackingProvider(), plus concrete env vars, defaults, and a typed provider interface covering the common cases.	5 / 5
Workflow Clarity	A clear numbered How-It-Works sequence and explicit operational checkpoints ('update both posthog-config.ts and deploy/build.ts', 'check what an event looks like in its UI') are present, though the document is reference-heavy rather than a single sequenced procedure.	4 / 5
Progressive Disclosure	Well-sectioned with headers and a Key Files table, but with no bundle files present the body is a ~340-line monolith whose MCP property enumeration and lifecycle taxonomy are inline reference material that could be split into separate files.	3 / 5
	Total	16 / 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.

A strong description that explicitly answers both 'what' and 'when' with concrete, named providers and clear trigger phrases. Minor gaps in action/synonym coverage keep specificity and trigger_term_quality at 4 rather than 5.

Dimension	Reasoning	Score
Specificity	Names the domain and several concrete actions ('adding analytics events', 'registering custom tracking providers', 'configuring built-in providers') plus enumerated providers, but coverage is not fully comprehensive (no mention of identify, error capture, or telemetry sampling).	4 / 5
Completeness	Clearly states what the skill does ('Server-side analytics tracking with pluggable providers') and provides an explicit 'Use when...' clause with three concrete trigger conditions and named providers.	5 / 5
Trigger Term Quality	A natural 'Use when adding analytics events...' trigger plus product names (PostHog, Mixpanel, Amplitude, Webhook) give good keyword coverage, though common synonyms like 'pageview', 'telemetry', and 'funnel' are absent.	4 / 5
Distinctiveness Conflict Risk	The server-side, pluggable-provider framing with specific product names carves a clear niche with minimal overlap risk against generic analytics skills.	5 / 5
	Total	18 / 20 Passed

Validation

81%

Warnings & errors only

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

Criteria	Description	Result
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
Path: .agents/skills/tracking/SKILL.md
Commit: a06e0ac

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.