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
Passed
No known issues
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 completeness, explicitly stating both what the skill does and when to use it. The main weakness is that the capability description could be more specific about the concrete actions it performs (e.g., creating webhook endpoints, configuring notification templates, setting up alert thresholds). The explicit trigger phrases section is a notable strength for skill selection.
Suggestions
Expand the capability description with more specific concrete actions, e.g., 'Create webhook endpoints, configure notification templates, set up job failure/success alerts, manage event subscriptions' instead of the more general 'configure notifications, webhooks, and event handling'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Databricks job notifications) and lists some actions (configure notifications, webhooks, event handling), but doesn't enumerate specific concrete actions like 'create webhook endpoints', 'set up retry policies', or 'configure email alerts'. It's more of a category description than a list of concrete capabilities. | 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 exact trigger terms). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms including 'databricks webhook', 'databricks notifications', 'databricks alerts', 'job failure notification', 'databricks slack', plus mentions of Slack/Teams and external systems. These are terms users would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with the specific combination of Databricks + notifications/webhooks/alerts. The trigger terms are narrowly scoped to Databricks event handling and notification integrations, making it unlikely to conflict with general Databricks skills or general notification 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 strong, highly actionable skill with excellent executable code examples covering multiple notification patterns (Slack, email, PagerDuty, SQL alerts, system tables). Its main weaknesses are the lack of inline validation/verification steps between operations and the monolithic structure that could benefit from splitting advanced topics (custom webhook handler, Slack formatter) into separate files. The error handling table is a nice touch but would be more effective as inline checkpoints.
Suggestions
Add verification steps after key operations, e.g., after Step 1: `assert slack.id is not None` and list destinations to confirm creation; after Step 2: trigger a test run to verify notifications fire.
Move the custom webhook handler (Step 3) and Slack formatter (Step 6) into separate referenced files to keep the main skill focused on core Databricks configuration.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient with executable code examples, but includes some unnecessary elements like the Overview section restating what's obvious from the title, and the Prerequisites section listing things Claude can infer. The Slack formatter (Step 6) adds useful but somewhat verbose content. Overall reasonably lean but could be tightened. | 2 / 3 |
Actionability | Every step includes fully executable, copy-paste ready code — Python SDK calls, SQL queries, YAML config, CLI commands, and a complete FastAPI webhook handler. Specific imports, method signatures, and parameter values are provided throughout. | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced (1-6) covering the full notification pipeline, but there are no validation checkpoints between steps. For example, after creating notification destinations there's no verification step, and after attaching notifications to jobs there's no test/confirm step. The error handling table is helpful but reactive rather than inline. | 2 / 3 |
Progressive Disclosure | The skill has good section structure and a Resources section linking to external docs, but the content is quite long (~180 lines of instructions) with everything inline. The Slack formatter and custom webhook handler could be split into separate reference files, with the main skill providing a concise overview and links. | 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
3e83543
- 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.