Duplicative paths in marketplace.json?

[sjnims]

Hi! I'm still learning and playing around with Claude Code plugins, and came across your repository as a reference. Something I'm not fully understanding is the pluginRoot key and the inclusion of the same path in the plugin source key. Wouldn't that mean the plugin source, in this case, becomes ./plugins/plugins/productivity/000-jeremy-content-consistency-validator?

https://github.com/jeremylongshore/claude-code-plugins-plus/blob/b2ab000401b9849db44bd7af0025608af2d80d6a/.claude-plugin/marketplace.json#L12

https://github.com/jeremylongshore/claude-code-plugins-plus/blob/b2ab000401b9849db44bd7af0025608af2d80d6a/.claude-plugin/marketplace.json#L20

[jeremylongshore]

Hey there! Great question - this definitely looks confusing at first glance.

The short answer: No, they don't concatenate. The paths work differently than you might expect.

How It Actually Works

• pluginRoot: This is metadata about the marketplace structure. It tells tools "hey, plugins generally live in the ./plugins directory." Think of it as documentation.

• source: This is the absolute path from the repository root to the specific plugin. It's not relative to pluginRoot.

So when Claude Code processes this:

{
  "pluginRoot": "./plugins",
  "source": "./plugins/productivity/000-jeremy-content-consistency-validator"
}

It uses the source path directly: ./plugins/productivity/000-jeremy-content-consistency-validator

It does not concatenate them into ./plugins/plugins/...

Why Have Both?

Good question! The pluginRoot is mostly for:

1. Marketplace metadata - Helps tools understand the repo structure
2. Documentation - Makes it clear where plugins live
3. Future tooling - Could be used for validation scripts, etc.

You're right that it looks redundant since every source path starts with ./plugins anyway. This is a quirk of the schema design.

For Your Own Marketplace

If you're building your own plugin marketplace, you can safely use:

• pluginRoot: Set it to where your plugins live (./my-plugins, etc.)
• source: Always use the full path from repo root

Hope this clears it up! Let me know if you have other questions - happy to help as you're building your own plugins.

— Jeremy