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
100%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
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.
This is an excellent skill description that hits all the marks. It provides specific concrete actions, comprehensive trigger terms covering both technical and natural language variations, explicit 'Use when' and 'Trigger on' clauses, and a clearly distinctive niche scoped to Sentry's frontend analytics. The description is well-structured and concise despite its thoroughness.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: instrumenting analytics events, discovering existing events, adding tracking to buttons/pages/modals/custom interactions, defining new analytics events, searching for existing events, and auditing analytics coverage. | 3 / 3 |
Completeness | Clearly answers both 'what' (instrument and discover analytics events in Sentry's frontend UI) and 'when' (explicit 'Use when...' clause with multiple specific scenarios, plus an explicit 'Trigger on' list of keywords). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms including both technical phrases ('add analytics', 'track event', 'instrument analytics') and natural user language ('how many people', 'are people using', 'is anyone clicking', 'who is using'). Covers a wide range of variations users would actually say. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche: Sentry's frontend UI analytics instrumentation. The combination of the specific product context (Sentry) and the specific domain (analytics events/tracking) makes it very unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an excellent skill file that demonstrates strong content quality across all dimensions. It efficiently communicates a complex analytics instrumentation workflow through well-structured tables, clear decision trees, and concrete examples while appropriately delegating detailed instructions to reference files. The interaction rules section is particularly well-crafted, providing explicit behavioral guidance for handling less technical users.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient throughout. Every section serves a clear purpose, tables are used effectively to compress information, and there's no explanation of concepts Claude already knows. No unnecessary padding or verbose descriptions. | 3 / 3 |
Actionability | Provides concrete file paths, specific grep commands, exact naming conventions with examples, clear decision tables for choosing tracking patterns, and explicit constraints. The interaction rules table gives precise behavioral instructions rather than vague guidance. | 3 / 3 |
Workflow Clarity | Multi-step processes are clearly sequenced: the 'Answering How Many People Do X' section has a numbered workflow with explicit decision points and confirmation gates. The 'Before Any Change: Search First' section enforces a validation-first approach. The interaction rules table provides clear feedback loops (event not found → ask user → implement or stop). | 3 / 3 |
Progressive Disclosure | The SKILL.md serves as a well-organized overview with clear one-level-deep references to supporting files (references/amplitude-mcp.md, references/tracking-patterns.md, references/event-definitions.md, references/troubleshooting.md). Each reference is clearly signaled with context about when to consult it. The main file contains enough to act on common cases without needing the references. | 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- getsentry/sentry
- Commit
552fb5c
- 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.