Claude Code plugin marketplace

[DanielPohlmann]

What this does

Ships this repository as a Claude Code plugin marketplace, so users can register it and install Oracle skills directly from within Claude Code — complementing the existing npx skills add flow.

Changes

• .claude-plugin/marketplace.json (new): defines the oracle-skills marketplace and publishes each top-level domain folder as its own plugin:
  • apex, db, fusion, graal, oci — each with a description, oracle category, and keywords.
• README.md: adds an "Install in Claude Code" section documenting how to register the marketplace and install domain plugins, alongside the existing npx instructions.

How to validate

1. Register the marketplace:
   • From GitHub: /plugin marketplace add oracle/skills
   • From a local clone: /plugin marketplace add ./
2. Install a domain plugin: /plugin install db@oracle-skills
3. Run /plugin to list and toggle installed plugins.

The marketplace file validates against the official schema (https://json.schemastore.org/claude-code-plugin-marketplace.json).

Closes #66

[DanielPohlmann]

Additional validation — declarative consumption via project-level .claude/settings.json

I validated this marketplace through a second, non-interactive path that complements the /plugin marketplace add + /plugin install flow described in the PR. Instead of registering and enabling plugins interactively, the marketplace and all of its plugins can be wired up declaratively by committing a project-scoped .claude/settings.json. This is useful for onboarding, CI, and shared repos, because the configuration becomes version-controlled and reproducible — every contributor who opens the project gets the exact same set of Oracle skills auto-loaded, with no manual steps.

What I tested

I created a .claude/settings.json at the project root with the following content:

{
  "enabledPlugins": {
    "apex@oracle-skills": true,
    "db@oracle-skills": true,
    "fusion@oracle-skills": true,
    "graal@oracle-skills": true,
    "oci@oracle-skills": true
  },
  "extraKnownMarketplaces": {
    "oracle-skills": {
      "source": {
        "source": "github",
        "repo": "DanielPohlmann/skills",
        "ref": "66-claude-code-marketplace"
      },
      "autoUpdate": true
    }
  }
}

How it maps to the marketplace defined in this PR

• extraKnownMarketplaces.oracle-skills registers the marketplace declaratively, equivalent to running /plugin marketplace add. The source block points Claude Code at the GitHub repo and the branch/ref where .claude-plugin/marketplace.json lives, so it resolves the same oracle-skills marketplace shipped in this PR. autoUpdate: true keeps the local copy in sync with the ref.
• enabledPlugins turns on each plugin published by marketplace.json using the <plugin>@<marketplace> identifier scheme (apex@oracle-skills, db@oracle-skills, fusion@oracle-skills, graal@oracle-skills, oci@oracle-skills). This is the declarative equivalent of /plugin install <plugin>@oracle-skills for all five domain plugins at once.

Note: in the example above the repo/ref point at the fork branch (DanielPohlmann/skills @ 66-claude-code-marketplace) used for testing before merge. Once this PR is merged, the canonical values are "repo": "oracle/skills" with the default branch (no ref needed).

Evidence

After opening the project, Claude Code picked up the configuration automatically — no interactive commands required. The /plugins → Installed panel lists all five domain plugins under the oracle-skills marketplace, each marked ✓ enabled, confirming that the marketplace resolves correctly and every plugin from marketplace.json is discoverable and loadable:

Project
  apex   Plugin · oracle-skills · ✓ enabled
  db     Plugin · oracle-skills · ✓ enabled
  fusion Plugin · oracle-skills · ✓ enabled
  graal  Plugin · oracle-skills · ✓ enabled
  oci    Plugin · oracle-skills · ✓ enabled

This matches the captured evidence screenshot, which shows the .claude/settings.json open in the editor on the left and the /plugins → Installed panel on the right with all five oracle-skills plugins enabled.

Takeaway

This confirms the marketplace works both interactively (/plugin ...) and declaratively (committed .claude/settings.json). It might be worth documenting the settings.json approach in the README as the recommended option for teams that want the Oracle skills enabled automatically and reproducibly across a shared repository, rather than relying on each user running the install commands manually.