CtrlK
BlogDocsLog inGet started
Tessl Logo

analytics

Instrument and discover analytics events in Sentry's frontend UI. Use when adding tracking to buttons, pages, modals, or custom interactions, when defining new analytics events, when searching for existing events, when auditing analytics coverage for a feature, or when answering questions about how users interact with a feature. Trigger on "add analytics", "track event", "instrument analytics", "analytics event", "track click", "track page view", "add tracking", "what events exist for", "audit analytics", "how many people", "how many users", "are people using", "is anyone clicking", "usage of", "who is using".

80

Quality

100%

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

100%Weight 40%Scale 1-3

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

The body is a tight, actionable overview that assumes competence, sequences risky workflows with explicit confirmation/validation checkpoints, and defers detail to real one-level-deep reference files. No verbosity or concept-explanation padding is present.

DimensionReasoningScore

Conciseness

Lean and dense — no preamble explaining what analytics or Sentry are; every section (naming rules, tracking patterns, key files, event pipeline) earns its place with tables instead of prose. Assumes Claude's competence throughout.

3 / 3

Actionability

Concrete and copy-paste-ready: real file paths ('static/app/utils/analytics.tsx'), a working grep command, named APIs ('trackAnalytics', 'analyticsEventKey', 'AnalyticsArea'), and pipeline destinations with their query tools. The single inline code block is a grep example, with full trackAnalytics usage deferred to references, but the guidance is specific and executable.

3 / 3

Workflow Clarity

Multi-step processes are explicitly sequenced with validation checkpoints: the 'How Many People' flow has Amplitude→grep fallback and a confirmation gate ('Do not proceed to instrumentation without explicit confirmation'), and 'Before Any Change: Search First' is gated by 'NEVER create a new event without checking'. Not level 2 because checkpoints and feedback loops are explicit, not implicit.

3 / 3

Progressive Disclosure

SKILL.md is a concise overview with clearly signaled one-level-deep references to real bundle files (amplitude-mcp.md, tracking-patterns.md with section anchors, event-definitions.md, troubleshooting.md), all confirmed present in references/. Content is appropriately split and easy to navigate.

3 / 3

Total

12

/

12

Passed

Description

100%Weight 40%Scale 1-3

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 specific, complete, and rich in natural trigger terms, clearly scoping a Sentry analytics instrumentation niche. It answers both 'what' and 'when' without vague fluff or over-claims.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Instrument and discover analytics events', 'adding tracking to buttons, pages, modals, or custom interactions', 'defining new analytics events', 'searching for existing events', 'auditing analytics coverage' — rather than vague language.

3 / 3

Completeness

Explicitly answers both what ('Instrument and discover analytics events in Sentry's frontend UI') and when ('Use when adding tracking...', 'Trigger on...'), with explicit trigger guidance present.

3 / 3

Trigger Term Quality

Includes natural phrases a user would say — 'how many people', 'is anyone clicking', 'track event', 'add analytics', 'usage of' — giving good coverage of common variations. Not merely technical jargon.

3 / 3

Distinctiveness Conflict Risk

Scoped to a clear niche (Sentry frontend analytics) with distinct trigger vocabulary, making it unlikely to fire for the wrong skill. Not level 2 because the domain and triggers are specific rather than merely 'somewhat specific'.

3 / 3

Total

12

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
getsentry/sentry
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.