Skip to content

plugin: add marketplace.json + document CLI vs plugin install paths#92

Closed
jamesbroadhead wants to merge 2 commits into
databricks:mainfrom
jamesbroadhead:jb/marketplace-and-install-docs
Closed

plugin: add marketplace.json + document CLI vs plugin install paths#92
jamesbroadhead wants to merge 2 commits into
databricks:mainfrom
jamesbroadhead:jb/marketplace-and-install-docs

Conversation

@jamesbroadhead
Copy link
Copy Markdown
Contributor

Summary

  • Adds .claude-plugin/marketplace.json so users can install the d-a-s skills plugin directly from inside Claude Code:

    /plugin marketplace add databricks/databricks-agent-skills
    /plugin install databricks-skills
    

    Without this file the existing .claude-plugin/plugin.json is reachable only after cloning the repo.

  • README.md: documents both install paths (CLI canonical, plugin marketplace alternative for stable skills) and adds a short comparison table covering experimental skills, per-skill selection, and outside-agent prerequisites.

Background

databricks-solutions/ai-dev-kit is in the process of being retired as a skills-distribution mechanism (see a-d-k PRs #546, #547, #548 and the team's DECOMMISSION_PLAN.md on the experimental branch). Users will be redirected here for skills.

The migration banner that a-d-k will start showing pre-1.0.0 users tells them to run /plugin marketplace add databricks/databricks-agent-skills. Without this PR landing, that command fails to resolve.

The plugin marketplace path is intentionally scoped to stable skills (matches the existing "skills": "./skills/" in plugin.json). Experimental skills stay CLI-only — the README's comparison table calls that out so users know which knob to reach for.

Test plan

  • cat .claude-plugin/marketplace.json | python3 -m json.tool — valid JSON.
  • From a clean Claude Code session: /plugin marketplace add databricks/databricks-agent-skills resolves, then /plugin install databricks-skills lists the plugin and installs it; ~/.claude/skills/databricks-core/ appears.
  • README renders cleanly on GitHub; the comparison table is legible.

This PR was AI-assisted by Isaac.

@jamesbroadhead
Copy link
Copy Markdown
Contributor Author

Superseded by #93 (same branch, opened from the upstream repo per our fork-vs-upstream convention; also corrects the README claim that the plugin path writes to ~/.claude/skills/ — it actually caches under ~/.claude/plugins/cache/<marketplace>/<plugin>/). Closing.

simonfaltum pushed a commit that referenced this pull request May 27, 2026
)

## Summary

- Adds `.claude-plugin/marketplace.json` so users can install the d-a-s
skills plugin directly from inside Claude Code:

      /plugin marketplace add databricks/databricks-agent-skills
      /plugin install databricks-skills

Without this file the existing `.claude-plugin/plugin.json` is reachable
only after cloning the repo.

- `README.md`: documents both install paths (CLI canonical, plugin
marketplace alternative for stable skills) and adds a short comparison
table covering experimental skills, per-skill selection, and
outside-agent prerequisites. The two paths install to *different*
locations (CLI writes into `~/.claude/skills/`; plugin caches under
`~/.claude/plugins/cache/<marketplace>/<plugin>/`) — the README now
spells that out instead of pretending they share a target.

## Background

`databricks-solutions/ai-dev-kit` is in the process of being retired as
a skills-distribution mechanism (see a-d-k PRs
[#546](databricks-solutions/ai-dev-kit#546),
[#547](databricks-solutions/ai-dev-kit#547),
[#548](databricks-solutions/ai-dev-kit#548) and
the team's `DECOMMISSION_PLAN.md` on the experimental branch). Users
will be redirected here for skills.

The migration banner that a-d-k will start showing pre-1.0.0 users tells
them to run `/plugin marketplace add
databricks/databricks-agent-skills`. Without this PR landing, that
command fails to resolve.

The plugin marketplace path is intentionally scoped to stable skills
(matches the existing `"skills": "./skills/"` in `plugin.json`).
Experimental skills stay CLI-only — the README's comparison table calls
that out so users know which knob to reach for.

This supersedes #92 (which was opened from a personal fork).

## Test plan

- [x] `python3 -m json.tool .claude-plugin/marketplace.json` — valid
JSON.
- [x] `claude plugin validate --strict .` on the branch — marketplace
manifest passes strict validation.
- [x] From a clean Claude Code session, `claude plugin marketplace add
<path>` + `claude plugin install databricks-skills` succeeds; `claude
plugin details databricks-skills` registers exactly the 8 stable skills
(`databricks-apps`, `-core`, `-dabs`, `-jobs`, `-lakebase`,
`-model-serving`, `-pipelines`, `-serverless-migration`); experimental
skills correctly excluded from the registered set even though they're
present in the plugin cache.
- [x] Plugin files land at
`~/.claude/plugins/cache/databricks-skills/databricks-skills/0.1.0/skills/<skill>/SKILL.md`
(the plugin path; not `~/.claude/skills/`, which is the CLI path).
- [ ] README renders cleanly on GitHub; the comparison table is legible.

This PR was AI-assisted 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