---
title: "claude code: ship your skills as a plugin marketplace"
url: https://perrotta.dev/2026/06/claude-code-ship-your-skills-as-a-plugin-marketplace/
last_updated: 2026-07-29
---


**Problem statement**: my Claude Code
[skills](https://code.claude.com/docs/en/skills) lived in my
[.dotfiles](https://github.com/thiagowfx/.dotfiles), usable only on the machine
that cloned them. I wanted them to be installable anywhere with one command, so
that (for example) my teammates could easily adopt them.

Claude Code reads skills from a marketplace, which is essentially a git repo
with a manifest. So I turned `github.com/thiagowfx/skills` into one. The layout:

```
.claude-plugin/marketplace.json    # marketplace manifest
plugins/thiagowfx/                 # one plugin
  .claude-plugin/plugin.json       # plugin manifest
  skills/<name>/SKILL.md           # one dir per skill (auto-discovered)
```

The marketplace lists plugins; a plugin bundles skills. I have one plugin
holding all ten. I do not find it necessary to have multiple plug-ins at this
point. `marketplace.json` points at it with a relative `source`:

```json
{
  "name": "thiagowfx",
  "owner": { "name": "Thiago Perrotta", "url": "https://github.com/thiagowfx" },
  "plugins": [
    {
      "name": "thiagowfx",
      "source": "./plugins/thiagowfx",
      "description": "Thiago's personal Gen-AI / Claude Code skills."
    }
  ]
}
```

The plugin manifest is just metadata — there's no need to enumerate skills.
Anything under `skills/<name>/SKILL.md` is discovered automatically:

```json
{
  "name": "thiagowfx",
  "version": "0.2.2",
  "license": "MIT"
}
```

The docs are explicit about why I keep that `version`:

> Setting `version` means users only receive updates when you change this field, so
> bump it on every release. If you omit `version` and host this marketplace in git,
> every commit automatically counts as a new version.

I'll go with version pinning for now.

Install from any machine:

```shell
/plugin marketplace add thiagowfx/skills
/plugin install thiagowfx@thiagowfx
```

`/plugin marketplace update thiagowfx` pulls future changes.

Outside Claude:

```shell
claude plugins update thiagowfx@thiagowfx
```

The whole thing — manifests, nine seeded skills, README, license — was
scaffolded by Claude Code itself, which felt appropriately recursive: one of the
skills I was packaging interviews me about a plan before any code gets written,
so it [grilled
me](https://github.com/thiagowfx/skills/blob/bb5c0d6ef60b7873d8df907a668db833674a0849/plugins/thiagowfx/skills/grill-me/SKILL.md)
about how to package the skills. Quite meta, eh?

**Next up**: point the dotfiles at the repo so there's a single source of truth.

- - -

🤖 *Drafted with [`/bloggify`](https://github.com/thiagowfx/skills/blob/master/plugins/thiagowfx/skills/bloggify/SKILL.md).*