Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

Since the marketplace name is now wrenai (org-level branding), it might be worth splitting the marketplace into its own repo (e.g., Canner/wrenai-marketplace). Right now the marketplace catalog lives inside wren-engine, but if we want to add plugins from other Wren AI products in the future (e.g., WrenAI, wren-ui), they'd all need to PR into this repo — which doesn't fit ownership-wise.

A dedicated marketplace repo would look like:

Canner/wrenai-marketplace — catalog only, no plugin code:

wrenai-marketplace/
└── .claude-plugin/
    └── marketplace.json

{
  "name": "wrenai",
  "owner": {
    "name": "Wren AI",
    "email": "[email protected]"
  },
  "metadata": {
    "description": "GenBI — queries any database in natural language with AI-powered business intelligence."
  },
  "plugins": [
    {
      "name": "wren-engine",
      "source": {
        "source": "git-subdir",
        "url": "https://github.com/Canner/wren-engine.git",
        "path": "skills"
      },
      "description": "The open context engine for AI agents. 20+ data sources. MCP-native.",
      "version": "1.0.0",
      "keywords": ["wrenai", "sql", "mdl", "mcp", "semantic-layer",
                    "bigquery", "postgres", "snowflake", "clickhouse", "mysql"],
      "category": "data"
    }
  ]
}

Canner/wren-engine — keeps plugin.json + skills content as-is, drops marketplace.json:

wren-engine/
└── skills/
    ├── .claude-plugin/
    │   └── plugin.json        # plugin metadata only
    ├── generate-mdl/
    │   └── SKILL.md
    ├── wren-sql/
    │   └── SKILL.md
    └── ...

The marketplace uses git-subdir source to point at each product repo's skills/ directory — so each repo owns its own plugin content, and the marketplace repo is purely a catalog for discovery and installation:

/plugin marketplace add Canner/wrenai-marketplace
/plugin install wren-engine@wrenai

Later, adding a new plugin from another repo is just a new entry in marketplace.json — no changes needed in wren-engine.

This doesn't have to block this PR, but worth considering before we publish the marketplace name wrenai with a structure that's harder to change later.