databricks-zerobus-ingest

Build Zerobus Ingest clients for near real-time data ingestion into Databricks Delta tables via gRPC. Use when creating producers that write directly to Unity Catalog tables without a message bus, working with the Zerobus Ingest SDK in Python/Java/Go/TypeScript/Rust, generating Protobuf schemas from UC tables, or implementing stream-based ingestion with ACK handling and retry logic.

Quality

86%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Risky

Do not use without reviewing

Quality

Discovery

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.

This is an excellent skill description that clearly defines a narrow, specific domain (Zerobus Ingest SDK for Databricks Delta table ingestion) with concrete actions and explicit trigger conditions. It uses appropriate third-person voice, includes rich domain-specific trigger terms, and has a well-structured 'Use when...' clause covering multiple scenarios. The description is concise yet comprehensive, making it easy for Claude to select this skill precisely when needed.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: building Zerobus Ingest clients, writing to Unity Catalog tables via gRPC, generating Protobuf schemas from UC tables, implementing stream-based ingestion with ACK handling and retry logic. Very detailed and actionable.	3 / 3
Completeness	Clearly answers both 'what' (build Zerobus Ingest clients for near real-time data ingestion into Databricks Delta tables via gRPC) and 'when' with an explicit 'Use when...' clause listing four distinct trigger scenarios.	3 / 3
Trigger Term Quality	Excellent coverage of natural terms a user would say: 'Zerobus Ingest', 'Databricks Delta tables', 'gRPC', 'Unity Catalog', 'Protobuf schemas', 'SDK', 'Python/Java/Go/TypeScript/Rust', 'stream-based ingestion', 'ACK handling', 'retry logic'. These are the exact terms a developer working in this domain would use.	3 / 3
Distinctiveness Conflict Risk	Highly distinctive with a very clear niche: Zerobus Ingest is a specific product/SDK, combined with specific technologies (gRPC, Protobuf, Unity Catalog, Delta tables). Extremely unlikely to conflict with other skills.	3 / 3
	Total	12 / 12 Passed

Implementation

72%

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

This is a well-structured skill with strong progressive disclosure and actionable guidance, including executable code and specific tool invocation patterns. Its main weaknesses are redundancy (context reuse and failure handling are duplicated, documentation links appear twice) and a workflow that lacks explicit validation/verification steps after ingestion. The 'Critical Learning' about timestamps feels like a patch rather than integrated guidance.

Suggestions

Remove duplicate content: consolidate 'Context Reuse Pattern' and 'Handling Failures' into a single section, and remove the duplicated documentation links at the bottom.

Add an explicit validation step to the workflow (e.g., step 6: 'Verify ingestion by querying the target table to confirm records landed') to ensure the workflow has proper checkpoints.

Trim the 'What Is Zerobus Ingest?' and 'Key Concepts' sections — Claude doesn't need explanations of what gRPC, Protobuf, or message buses are. Keep only the Zerobus-specific constraints (at-least-once, single-AZ, no table management).

Integrate the 'Critical Learning: Timestamp Format Fix' into the relevant workflow step or the Python example rather than leaving it as a standalone callout.

Dimension	Reasoning	Score
Conciseness	The skill has significant redundancy: the 'Context Reuse Pattern' and 'Handling Failures' sections repeat nearly identical information, the documentation links appear twice (top and bottom), and the 'What Is Zerobus Ingest?' section explains concepts Claude doesn't need (what a message bus is). The 'Key Concepts' section also over-explains gRPC/Protobuf basics. However, the decision table and troubleshooting table are efficient.	2 / 3
Actionability	The skill provides a fully executable Python example with concrete imports, SDK initialization, stream creation, record ingestion, and cleanup. It includes specific package versions, exact pip install commands, and concrete tool invocation patterns (execute_code with file_path, cluster_id, context_id parameters). The decision table maps scenarios to specific files.	3 / 3
Workflow Clarity	The workflow has numbered steps with a clear sequence and includes a retry/fix loop (step 5). However, it lacks explicit validation checkpoints — there's no step to verify the ingestion succeeded (e.g., querying the target table to confirm records landed). The prerequisite validation instruction ('never execute without confirming') is vague about how to confirm. The timestamp fix is flagged as critical but not integrated into the workflow steps.	2 / 3
Progressive Disclosure	Excellent structure with a concise overview, quick decision table routing to specific sub-files, and a detailed guides table with clear 'When to Read' guidance. References are one level deep and well-signaled. Related skills are appropriately linked. Content is well-split between the overview and five detailed guide files.	3 / 3
	Total	10 / 12 Passed

Validation

100%

Warnings & errors only

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: databricks-solutions/ai-dev-kit
Commit: 02aac8c

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.