databricks-ci-integration

Configure Databricks CI/CD integration with GitHub Actions and Asset Bundles. Use when setting up automated testing, configuring CI pipelines, or integrating Databricks deployments into your build process. Trigger with phrases like "databricks CI", "databricks GitHub Actions", "databricks automated tests", "CI databricks", "databricks pipeline".

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Quality

Content

92%

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

A dense, highly actionable CI/CD guide with executable workflows, validation checkpoints, and a useful error table. Its main weakness is monolithic structure with no progressive disclosure via reference files.

Suggestions

Extract the full workflow YAML for Step 1 and Step 3 into separate reference files (e.g. references/databricks-ci.yml, references/databricks-deploy.yml) and link to them from concise inline summaries.

Consider moving the unit-test example and branch-based dev target into a references/ or examples file so SKILL.md stays a focused overview.

Add a one-line navigation pointer near the top listing the bundled reference files so the structure is discoverable at a glance.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence — no padding explaining what Databricks or CI is; nearly every line is executable config, code, or a focused table. Length is justified by real, copy-paste-ready artifacts rather than verbosity.	3 / 3
Actionability	Provides fully executable GitHub Actions YAML and pytest code with specific commands (e.g. 'databricks bundle validate -t staging', 'pytest tests/unit/ -v --tb=short') that are copy-paste ready.	3 / 3
Workflow Clarity	Steps are clearly sequenced (validate-and-test on PR, deploy-staging with integration tests, deploy-production on merge, OIDC keyless auth), and each deploy is gated by a preceding 'bundle validate' checkpoint; production also has concurrency control and an environment approval gate, plus an error-handling table for recovery.	3 / 3
Progressive Disclosure	Well-organized into clear sections, but it is a ~240-line monolithic SKILL.md with no bundle files; the large inline workflow YAML blocks could be split into one-level-deep reference files to ease navigation.	2 / 3
	Total	11 / 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 concise, well-structured description that clearly states capabilities, usage triggers, and natural trigger phrases. Third-person voice is maintained and it avoids vague fluff or over-claims.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ('Configure Databricks CI/CD integration with GitHub Actions and Asset Bundles') plus a Use-when clause enumerating 'setting up automated testing, configuring CI pipelines, or integrating Databricks deployments into your build process'.	3 / 3
Completeness	Explicitly answers both what (configure Databricks CI/CD integration) and when ('Use when setting up automated testing, configuring CI pipelines...'), with explicit trigger guidance.	3 / 3
Trigger Term Quality	Provides natural trigger phrases a user would actually say: 'databricks CI', 'databricks GitHub Actions', 'databricks automated tests', 'CI databricks', 'databricks pipeline', giving good coverage of common variations.	3 / 3
Distinctiveness Conflict Risk	Occupies a clear niche (Databricks + GitHub Actions + Asset Bundles) with distinct, domain-specific triggers unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 12 Passed

Validation

87%

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 — 14 / 16 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	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Commit: 6e3a65f

Reviewed: 5 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.