CtrlK
BlogDocsLog inGet started
Tessl Logo

databricks-observability

Set up comprehensive observability for Databricks with metrics, traces, and alerts. Use when implementing monitoring for Databricks jobs, setting up dashboards, or configuring alerting for pipeline health. Trigger with phrases like "databricks monitoring", "databricks metrics", "databricks observability", "monitor databricks", "databricks alerts", "databricks logging".

72

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

80%

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

The content is highly actionable and token-efficient with executable SQL and Python throughout. Its weaknesses are the absence of explicit validation feedback loops in the workflow and the monolithic single-file structure with no progressive disclosure references.

Suggestions

Add explicit validation checkpoints (e.g., 'verify the SQL alert fires and rearm works before relying on it') and a validate-fix-retry loop for Step 5/6 operations to lift workflow_clarity.

Split the reference material (catalog/schema map, error-handling table, examples) into a REFERENCES.md or EXAMPLES.md linked one level deep so SKILL.md stays a concise overview.

Reconcile the description's 'traces' claim with the body, which covers metrics, costs, and audit logs but no distributed tracing.

DimensionReasoningScore

Conciseness

The body is lean, dominated by executable SQL/Python with brief comments and avoids explaining concepts Claude already knows, so every token earns its place.

3 / 3

Actionability

It provides fully executable SQL queries against real system tables and copy-paste-ready databricks.sdk Python snippets with specific columns, joins, and filters.

3 / 3

Workflow Clarity

Seven numbered steps are clearly sequenced, but there are no explicit validation checkpoints or validate-fix-retry feedback loops for batch/alert operations, capping clarity at 2.

2 / 3

Progressive Disclosure

At over 200 lines with everything inline and no bundle files or one-level-deep references, it is organized into sections but lacks the clear overview-to-detail split the rubric rewards.

2 / 3

Total

10

/

12

Passed

Description

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.

The description is specific, complete, and well-triggered with natural user phrases and a clear Databricks niche. It earns top marks on all four dimensions. Minor caveat: 'traces' is promised in the description but the body delivers metrics/costs/audit rather than tracing, a content-mismatch not reflected in the description scores.

DimensionReasoningScore

Specificity

It names concrete actions ('Set up comprehensive observability for Databricks with metrics, traces, and alerts') comparable to the multiple-specific-actions anchor.

3 / 3

Completeness

It explicitly answers both what (observability with metrics/traces/alerts) and when ('Use when implementing monitoring for Databricks jobs, setting up dashboards, or configuring alerting').

3 / 3

Trigger Term Quality

It lists natural trigger phrases ('databricks monitoring', 'databricks metrics', 'monitor databricks', 'databricks alerts', 'databricks logging') a user would actually say.

3 / 3

Distinctiveness Conflict Risk

It targets a clear Databricks-observability niche with distinct triggers, making conflict with other skills unlikely.

3 / 3

Total

12

/

12

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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

14

/

16

Passed

Repository
jeremylongshore/claude-code-plugins-plus-skills
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.