notification-platform
Guide for adding notifications, custom renderers, or new providers to Sentry's NotificationPlatform. Use when asked to "add notification", "new notification", "notification platform", "send notification", "notification template", "notification renderer", "notification provider", "NotificationPlatform", "notify user", "send email notification", "send slack notification".
94
95%
Does it follow best practices?
Impact
89%
1.28xAverage score across 3 eval scenarios
Passed
No known issues
Quality
Discovery
89%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 a solid skill description with excellent trigger term coverage and a clear 'Use when' clause. Its main weakness is that the 'what' portion could be more specific about the concrete actions involved (e.g., defining message templates, configuring delivery channels, writing renderer classes). Overall it performs well for skill selection purposes.
Suggestions
Expand the capability description to list more specific concrete actions, e.g., 'define message templates, configure delivery channels, implement renderer classes, register new provider integrations'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | It names the domain (Sentry's NotificationPlatform) and mentions some actions ('adding notifications, custom renderers, or new providers'), but doesn't list deeply specific concrete actions like creating templates, configuring routing, or handling delivery callbacks. | 2 / 3 |
Completeness | Clearly answers both 'what' (guide for adding notifications, custom renderers, or new providers to Sentry's NotificationPlatform) and 'when' (explicit 'Use when asked to...' clause with a comprehensive list of trigger phrases). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms including variations like 'add notification', 'new notification', 'notification template', 'notification renderer', 'notification provider', 'send email notification', 'send slack notification', and 'notify user'. These are terms users would naturally say. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific mention of Sentry's NotificationPlatform and the focused scope on notification-related additions. The trigger terms are specific enough to avoid conflicts with general coding or other notification systems. | 3 / 3 |
Total | 11 / 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 exceptionally well-crafted skill that provides a complete, actionable guide for extending Sentry's NotificationPlatform. It combines concise orientation (glossary, routing table) with executable code examples at every step, clear sequencing with validation checkpoints, and well-signaled references to deeper documentation. The only minor concern is that the referenced bundle files weren't provided for verification, but the skill content itself is exemplary.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient throughout. The glossary table is dense but necessary for orientation. No unnecessary explanations of basic concepts—it assumes Claude understands dataclasses, protocols, enums, and registry patterns. Every section earns its place. | 3 / 3 |
Actionability | Provides fully executable, copy-paste-ready code for every step: data class definition, template creation, registration, sending pattern, and tests. Concrete examples with real imports, decorators, and assertions. File paths are specific. | 3 / 3 |
Workflow Clarity | Clear routing table (Step 1) directs to the right steps. Steps 2-9 are well-sequenced with explicit validation: Step 8 provides test patterns, Step 9 provides a pre-flight checklist with verification items. The 'If no existing category fits' branching and rollout gating add appropriate checkpoints. | 3 / 3 |
Progressive Disclosure | Excellent progressive disclosure with clear one-level-deep references to detailed docs (references/data-and-templates.md, references/targets-and-sending.md, references/custom-renderers.md, references/provider-template.md). The main SKILL.md serves as a complete overview while pointing to deeper material. Note: no bundle files were provided to verify these references exist, but the structure and signaling are well-organized. | 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.