experimental: backfill metadata.version + parent + compatibility frontmatter#105
Merged
Conversation
jamesbroadhead
requested review from
a team,
dustinvannoy-db,
lennartkats-db and
simonfaltum
as code owners
…tmatter Adds three frontmatter fields to 17 experimental SKILL.md files that stable skills already carry but the imported a-d-k snapshot does not: - `compatibility: Requires databricks CLI (>= v0.294.0)` - `metadata.version: "0.1.0"` (was the `0.0.1` script floor) - `parent: databricks-core` `experimental/databricks-vector-search` is intentionally skipped to avoid conflict with #87 (promotion to stable, which adds the same fields as part of the move). Manifest deltas: every experimental skill's `version` flips from `0.0.1` (scripts/skills.py fallback floor) to `0.1.0`. No other consumer-visible fields move — `compatibility` and `parent` are SKILL.md-only and not surfaced in manifest.json today. ## Test plan - `python3 scripts/skills.py generate` clean - `python3 scripts/skills.py validate` passes (`Everything is up to date.`) This PR was prepared by Claude.
jamesbroadhead
force-pushed
the
jb/experimental-metadata-backfill
branch
from
c62b465 to
e89c4ee
Compare
6 tasks
… skills - compatibility floor bumped from v0.294.0 to v1.0.0 across all 17 experimental SKILL.md files. Several skills depend on the top-level 'databricks aitools install' surface promoted in cli#4917 (v1.0.0+); v0.294.0 understated the actual floor. - parent: databricks-core removed from spark-python-data-source (OSS Spark, not Databricks-specific) and databricks-zerobus-ingest (gRPC, different auth model). Over-couples the hierarchy otherwise. Co-authored-by: Isaac
jralfonsog
added a commit
to jralfonsog/databricks-agent-skills
that referenced
this pull request
May 30, 2026
Per @dustinvannoy-db review: - Add frontmatter parent / compatibility / metadata.version (aligns with databricks#105) - Drop channel from GA examples; GA connectors default to CURRENT (docs: ServiceNow/Salesforce GA omit channel, Confluence Beta uses PREVIEW). Reframe guidance to PREVIEW-only-for-Public-Preview/Beta. - Cross-skill references use plain bold names (stable-skill convention) - Remove the GA target date column and other specific dates (avoid maintenance churn) - Drop Zerobus from the connector catalog (separate skill; kept as a related-skill and decision-tree cross-reference) - Consolidate the SKILL.md Common Issues table into a pointer to the troubleshooting reference - Remove the top Documentation block (duplicated in Resources) - Fix openai.yaml default_prompt grammar and casing Signed-off-by: Jose Alfonso <jralfonsog@gmail.com>
…manifest Resolves the stale-branch conflicts so the experimental metadata backfill applies on current main. - experimental/databricks-execution-compute/SKILL.md: kept main's updated description and re-applied the backfilled compatibility/metadata.version/parent frontmatter. - manifest.json: regenerated with the current generator (canonical sort + frontmatter-derived metadata from #95/#100) rather than hand-merging. Kept the v1.0.0 CLI floor and the dropped parent on the two non-core skills (both deliberate in 624bc07). Co-authored-by: Isaac Signed-off-by: simon <simon.faltum@databricks.com>
simonfaltum
approved these changes
Jun 2, 2026
simonfaltum
added a commit
that referenced
this pull request
Jun 2, 2026
Resolve frontmatter conflict in databricks-unstructured-pdf-generation/SKILL.md: keep the reframed RAG/eval description (PR) plus the compatibility, metadata.version, and parent fields backfilled on main (#105). Regenerate manifest.json. Co-authored-by: Isaac
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Backfills three frontmatter fields on 17
experimental/SKILL.md files that stable skills already carry but the imported a-d-k snapshot does not:compatibility: Requires databricks CLI (>= v0.294.0)metadata.version: "0.1.0"(was the0.0.1scripts/skills.pyfallback floor)parent: databricks-coreCloses the frontmatter-version / parent-skill / CLI-compatibility gaps in one mechanical pass — they all touch the same files.
Why
The stable-side standard is documented in CLAUDE.md and consistently applied across
skills/. Experimental skills carry none of these fields because #73 imported the a-d-k snapshot verbatim. PR #73 TODO #7 explicitly leaves the version backfill open ("when upstream a-d-k eventually adds version fields, those win; until then, the manifest reports the floor"). With a-d-k now deprecated, this repo is source of truth forexperimental/and the backfill lands here.The promotion-time pattern (cf. #87 vector-search) adds these fields on the way out of
experimental/. This PR closes the gap for the remaining skills that haven't been promoted yet.Changes
17 SKILL.md files in
experimental/, plus manifest regeneration.experimental/databricks-vector-search/SKILL.mdis intentionally skipped — #87 promotes it toskills/and adds the same fields as part of the move; including it here would create fake conflicts. Whichever lands first, the other rebases cleanly.Manifest deltas
Every experimental skill's
versionflips from0.0.1(theextract_version_from_skillfallback floor) to0.1.0.compatibilityandparentare SKILL.md-only — not surfaced in manifest.json today.Test plan
python3 scripts/skills.py generatecleanpython3 scripts/skills.py validatepasses (Everything is up to date.)This pull request and its description were written by Claude.