# pdego-marketplace
PDEGO Marketplace is a catalog of Claude Code/Github Copilot Plugins to accelerate your development application_family: devops

## Using the pdego-marketplace from your Claude Code / Github Copilot CLI

```sh
/plugin marketplace add theorchard/pdego-marketplace
```

You can either use your CLI to navigate through the available plugins to choose which to install, or if you know precisely which plugin to install:

```sh
/plugin install pp-pilot@pdego-marketplace
```

There are a few ways to get your marketplace and plugins updated. The surest way is to exit out of your CLI and restart it.

In addition, you can directly call to update a plugin:

```sh
/plugin update pp-pilot@pdego-marketplace
```

You may also choose to alter your user settings for Claude (`~/.claude/settings.json`)to ensure the marketplace is configured to `autoUpdate`:

```json
...
    "pdego-marketplace": {
      "source": {
        "source": "directory",
        "path": "/Users/jchung/code/pdego-marketplace"
      },
      "autoUpdate": true
    }
...
```

## Adding a new plugin to pdego-marketplace

(Note - configuring a Claude Code Plugin is compatible with Github Copilot CLI - you don't have to do anything extra)

We advise two mechanisms for providing the plugin source to the `pdego-marketplace`:

- Relative path from this repo
- Separate Github repo as the source - useful if your team is creating/maintaining an extensive set of skills, germane to your team's domain

In order to share the plugin on the marketplace, add another entry to the list of plugins in this repo's `.claude-plugin/marketplace.json`. Be sure to follow the [spec for the marketplace.json file](https://code.claude.com/docs/en/plugin-marketplaces#marketplace-schema). There are examples for adding plugins where the source is either relative path or separate Github repo.

The instructions below advise how to configure skills, but keep in mind you can provide `agents`, `hooks`, `scripts`, MCP server configs, and more by following the [plugin directory structure](https://code.claude.com/docs/en/plugins-reference#plugin-directory-structure).

### This repo (relative path) as the source

To create a new plugin `new-plugin` within this repo (relative path as the source):

1. Under `plugins` create a new directory: `mkdir -p plugins/new-plugin`
1. Under `plugins/new-plugin`, create `.claude-plugin` directory: `mkdir -p plugins/new-plugin/.claude-plugin`
1. Add `plugins/new-plugin/.claude-plugin/plugin.json` file. Be sure to follow the [spec for the plugin.json file](https://code.claude.com/docs/en/plugins-reference#plugin-manifest-schema).
1. Add a new skill `new-skill` under the `new-plugin`:

```sh
mkdir -p plugins/new-plugin/new-skill
touch plugins/new-plugin/new-skill/SKILL.md  # Update this file
```

### Separate Github repo as the source

If your team is intending to create/maintain an extensive set of skills, germane to your team's domain, creating the plugin with a separate Github repo as the source may be helpful

1. Setup a Github repo for your plugin.
1. Create a `.claude-plugin` directory at the root of the repo, with a `plugin.json` file. Be sure to follow the [spec for the plugin.json file](https://code.claude.com/docs/en/plugins-reference#plugin-manifest-schema).
1. Create your `skills` directory at the root of the repo. If you've already been creating skills under `.github/skills` you may opt to just create a symlink:

    ```sh
    ln -s .github/skills skills
    ```

    (Utilizing `.github/skills` may be a good pattern if you want to support folks using Github Copilot with IDE, which does not support installing plugins from Marketplace as of March 2026.)