Skip to content

Set up Studio as a Claude and Codex marketplace for data-liberation#4011

Open
borkweb wants to merge 2 commits into
trunkfrom
fix/dla-marketplace
Open

Set up Studio as a Claude and Codex marketplace for data-liberation#4011
borkweb wants to merge 2 commits into
trunkfrom
fix/dla-marketplace

Conversation

@borkweb

@borkweb borkweb commented Jun 30, 2026

Copy link
Copy Markdown
Member

Related issues

How AI was used in this PR

Authored with Claude Code. The marketplace/plugin configs were written and then verified against the actual Claude Code plugin spec and the on-disk bork/vercel reference plugins to confirm path-resolution behavior (Claude vs. Codex both resolve a plugin source relative to the marketplace repo root). The MCP-registration, relative-path, and license corrections came out of that verification pass.

Proposed Changes

Promotes the Studio repo root to a plugin marketplace for both Claude (.claude-plugin/marketplace.json) and Codex (.agents/), and rehomes the data-liberation plugin metadata under the Studio identity. With this, the bundled packages/data-liberation-agent workspace installs as a first-class plugin in both Claude Code and Codex — surfacing its skills, commands, and the data-liberation MCP server — without consumers needing to add a separate marketplace.

Both marketplaces point their plugin source directly at ./packages/data-liberation-agent, resolved from the repo root, so no plugin-locating symlink is required. This also corrects configuration that would otherwise have broken installation:

  • The Claude plugin now registers its MCP server via the valid mcpServers key (pointing at the canonical ./.mcp.json) instead of an unrecognized mcp field.
  • The Codex plugin's skills/mcpServers paths are plugin-root-relative rather than double-prefixed with the package path.
  • Both plugin manifests declare GPL-2.0-or-later to match the host repo.

No application code changes; this is marketplace/plugin configuration only.

Testing Instructions

  1. Claude: From a checkout of this branch, add the local marketplace (/plugin marketplace add .) and install data-liberation. Confirm the plugin's skills/commands appear and the data-liberation MCP server registers and starts.
  2. Codex: Add the marketplace from .agents/ and install data-liberation; confirm the plugin resolves to packages/data-liberation-agent and its skills + MCP server load.
  3. Validate the JSON manifests parse (all four marketplace/plugin files are valid JSON).

nightnei and others added 2 commits June 30, 2026 10:46
Promotes the Studio repo root to a plugin marketplace for both Claude (.claude-plugin/marketplace.json) and Codex (.agents/) and rehomes the data-liberation plugin metadata under the Studio identity, so the bundled data-liberation-agent workspace installs as a first-class plugin in both tools.

Both marketplaces point their plugin source directly at ./packages/data-liberation-agent, resolved from the repo root, so no plugin-locating symlink is needed. Corrects the plugin configs that would otherwise have broken installation: the Claude plugin now registers its MCP server via the valid mcpServers key (pointing at the canonical ./.mcp.json) instead of an unrecognized mcp field, the Codex plugin's skills/mcpServers paths are plugin-root-relative rather than double-prefixed, and both declare GPL-2.0-or-later to match the host repo.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Claude-Session: https://claude.ai/code/session_01SqSer8WNQM5AVDqyrTUFcC
@borkweb borkweb requested a review from nightnei June 30, 2026 13:36
Base automatically changed from cloneDataLioberationAgentToPackagesFolder to trunk July 1, 2026 09:54
@nightnei nightnei requested a review from a team as a code owner July 1, 2026 09:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants