databricks-webhooks-events
Configure Databricks job notifications, webhooks, and event handling. Use when setting up Slack/Teams notifications, configuring alerts, or integrating Databricks events with external systems. Trigger with phrases like "databricks webhook", "databricks notifications", "databricks alerts", "job failure notification", "databricks slack".
80
77%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Risky
Do not use without reviewing
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/saas-packs/databricks-pack/skills/databricks-webhooks-events/SKILL.mdQuality
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 well-structured skill description with strong trigger term coverage and clear 'what/when' guidance. The explicit trigger phrases section is a notable strength for disambiguation. The main weakness is that the capability description could be more specific about the concrete actions performed beyond the high-level 'configure notifications, webhooks, and event handling'.
Suggestions
Add more specific concrete actions to the capability description, e.g., 'Create webhook endpoints, configure job failure/success email alerts, set up Slack channel integrations, define event filters and routing rules'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Databricks job notifications) and some actions (configure notifications, webhooks, event handling), but doesn't list multiple concrete specific actions like 'set up webhook endpoints, configure retry policies, parse event payloads'. | 2 / 3 |
Completeness | Clearly answers both 'what' (configure Databricks job notifications, webhooks, and event handling) and 'when' (explicit 'Use when' clause with specific scenarios plus a 'Trigger with phrases' section listing concrete trigger terms). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'databricks webhook', 'databricks notifications', 'databricks alerts', 'job failure notification', 'databricks slack', plus mentions Slack/Teams which are common integration targets. | 3 / 3 |
Distinctiveness Conflict Risk | Very distinct niche combining Databricks-specific functionality with notifications/webhooks/alerts. The specific trigger phrases like 'databricks webhook' and 'job failure notification' make it unlikely to conflict with generic notification or generic Databricks skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a highly actionable skill with excellent executable code examples covering multiple notification patterns (Slack, email, PagerDuty, custom webhooks, SQL alerts, system tables). Its main weaknesses are the lack of validation/verification steps between workflow stages and the monolithic structure that could benefit from splitting advanced topics into separate files. The error handling table is a strong addition.
Suggestions
Add explicit validation checkpoints after key steps, e.g., verify notification destination creation with `w.notification_destinations.get(slack.id)` and test webhook delivery before attaching to production jobs.
Split the custom webhook handler (Step 3), Slack formatter (Step 6), and SQL alert queries into separate referenced files to improve progressive disclosure and reduce the main skill's length.
Add a quick verification step after Step 2 such as triggering a test run and confirming notifications were received before proceeding to advanced configurations.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly efficient and avoids explaining basic concepts, but it's quite long (~200 lines) with some sections that could be trimmed. The Slack message formatter (Step 6) and the custom webhook handler (Step 3) are extensive and could be more concise. The error handling table and output section add value without excessive verbosity. | 2 / 3 |
Actionability | Every step provides fully executable, copy-paste-ready code with correct SDK imports, concrete API calls, SQL queries, and CLI commands. Examples cover Python SDK, YAML config, FastAPI handlers, and SQL — all with specific parameters and realistic values. | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced (create destinations → attach to jobs → build handler → monitor → alert → format), but there are no explicit validation checkpoints or feedback loops. For example, after creating notification destinations, there's no step to verify they were created successfully or test that webhooks fire correctly before proceeding. | 2 / 3 |
Progressive Disclosure | The content is well-structured with clear headers and a logical flow, and it links to external documentation. However, for a skill this long, the custom webhook handler, Slack formatter, and SQL alert sections could be split into separate reference files. Everything is inline in a single monolithic document. | 2 / 3 |
Total | 9 / 12 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.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
3a2d27d
- 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.