Skip to content

experimental: backfill metadata.version + parent + compatibility frontmatter#105

Open
jamesbroadhead wants to merge 2 commits into
mainfrom
jb/experimental-metadata-backfill
Open

experimental: backfill metadata.version + parent + compatibility frontmatter#105
jamesbroadhead wants to merge 2 commits into
mainfrom
jb/experimental-metadata-backfill

Conversation

@jamesbroadhead
Copy link
Copy Markdown
Contributor

@jamesbroadhead jamesbroadhead commented May 27, 2026

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 the 0.0.1 scripts/skills.py fallback floor)
  • parent: databricks-core

Closes 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 for experimental/ 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.md is intentionally skipped#87 promotes it to skills/ 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 version flips from 0.0.1 (the extract_version_from_skill fallback floor) to 0.1.0. compatibility and parent are SKILL.md-only — 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.)
  • CI green on this branch.

This pull request and its description were written by Claude.

…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.
… 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant