CtrlK
BlogDocsLog inGet started
Tessl Logo

databricks-model-serving

Databricks Model Serving endpoint lifecycle and ops. Use when asked to: CRUD serving endpoints (CLI or MLflow Deployments client); configure traffic routing for A/B / canary deploys and zero-downtime version swaps; retrieve OpenAPI schemas; inspect logs, metrics, or permissions; manage AI Gateway rate limits; discover Foundation Model API endpoints at runtime; integrate endpoints into Databricks Apps; or stream from off-platform clients (Vercel AI SDK v6, standalone Node.js). NOT for: training, MLflow autologging, UC registration, custom PyFunc/ResponsesAgent authoring (databricks-ml-training); Knowledge Assistants/Supervisor Agents (databricks-agent-bricks); MLflow evaluation (databricks-mlflow-evaluation).

78

Quality

100%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

100%

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

A lean, highly actionable operations skill body with executable CLI/Python examples, explicit sequencing and validation checkpoints for risky lifecycle operations, and well-signaled one-level-deep references. It assumes Claude's competence and reserves detail for genuine gotchas.

DimensionReasoningScore

Conciseness

The body is dense, operational guidance — CLI commands, complete JSON specs, jq filters, and gotchas — and largely avoids explaining concepts Claude already knows; the brief intro establishes the name-keyed model used throughout, and nearly every token earns its place.

3 / 3

Actionability

Provides fully executable, copy-paste-ready guidance: complete `create`/`update-config` JSON specs, a working Python zero-downtime-swap snippet, a runtime Foundation Model discovery jq filter, and a concrete error-to-command troubleshooting table.

3 / 3

Workflow Clarity

Multi-step processes are explicitly sequenced with validation checkpoints — 'ALWAYS Do This First' discovery, the alias-plus-update_endpoint swap with its 'missing either half is the common bug' warning, and the readiness feedback loop requiring both `state.ready == READY` AND `state.config_update == NOT_UPDATING` before querying.

3 / 3

Progressive Disclosure

SKILL.md serves as a clear overview with one-level-deep, well-signaled references to a real `references/off-platform-streaming.md` bundle file and cross-skill pointers (`databricks-apps`, `databricks-ml-training`); the bundle reference exists and is appropriately split off rather than nested.

3 / 3

Total

12

/

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.

A high-quality, third-person description with explicit 'Use when' triggers, a comprehensive list of concrete serving-endpoint operations, and a clear 'NOT for' exclusion set that distinguishes it from adjacent skills. It concisely covers both what the skill does and when to invoke it.

DimensionReasoningScore

Specificity

Lists many concrete, domain-specific actions — 'CRUD serving endpoints (CLI or MLflow Deployments client)', 'configure traffic routing for A/B / canary deploys and zero-downtime version swaps', 'retrieve OpenAPI schemas', 'manage AI Gateway rate limits', 'discover Foundation Model API endpoints at runtime', 'stream from off-platform clients' — rather than vague language.

3 / 3

Completeness

Explicitly answers both 'what' ('endpoint lifecycle and ops' plus the enumerated actions) and 'when' via an explicit 'Use when asked to:' clause, and adds a 'NOT for' exclusion list — clearly satisfies both halves.

3 / 3

Trigger Term Quality

Trigger phrasings map to natural task requests users would say ('configure traffic routing', 'inspect logs, metrics, or permissions', 'discover Foundation Model API endpoints', 'integrate endpoints into Databricks Apps'), with broad coverage; not reduced to technical jargon alone.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear niche (Model Serving ops) and explicitly disambiguates from sibling skills via 'NOT for: ... (databricks-ml-training); ... (databricks-agent-bricks); ... (databricks-mlflow-evaluation)', making wrong-skill triggering 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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 2 suspicious

Warning

Total

14

/

16

Passed

Repository
databricks/databricks-agent-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.