[alexshapalov]

Summary

PGX becomes installable inside Claude Code through its native plugin manager, without leaving the session:

/plugin marketplace add pgrundev/pgx
/plugin install pgx@pgrundev
/pgx:pgx Set up isolated Postgres databases for this project.

• Marketplace pgrundev at .claude-plugin/marketplace.json (one plugin today, reusable for more PostgreSQL tools).
• Plugin pgx at plugins/pgx/: .claude-plugin/plugin.json (version 0.1.1), README.md, and skills/pgx/, a verbatim copy of the canonical Skill. plugins/sync.sh regenerates the copy; plugins/sync.sh --check fails CI on drift. 84 KB installed, 16 files, ~190–270 tokens of always-on context. No hooks, MCP servers, commands or binaries.
• Skill (skills/pgx/SKILL.md): adds the plugin install path for its helper scripts (${CLAUDE_PLUGIN_ROOT}/skills/pgx/scripts/…, substituted by Claude Code when loaded from the plugin); metadata.version → 0.1.1 to match the plugin. references/claude-code.md documents both install routes and running them side by side.
• No duplicate hooks: hooks keep coming from pgx agent setup only. Installing, updating, disabling or removing the plugin never touches .claude/settings.json (tested). A user-scope install does nothing in projects without .pgx.toml.
• Skills CLI unchanged: npx skills add pgrundev/pgx --skill pgx still installs the plain skill /pgx; with both installed Claude Code lists /pgx and /pgx:pgx.
• Tests/CI: plugins/tests/pgx/run.sh (validate --strict on plugin + marketplace, directory profile, drift, hygiene, isolated install → list → details → disable → enable → update → project/local scope → uninstall → reinstall → marketplace remove, hooks untouched, Skills-CLI copy alongside); new CI job plugin with a pinned Claude Code CLI (2.1.310) and gitleaks over the package.
• Docs: README install block, docs/pgx/local-dev/claude-plugin.md, agents.md, validation note.

Validation

• claude plugin validate --strict plugins/pgx and --strict .: passed (Claude Code 2.1.310). --profile directory: no refusals (icon recommended).
• Local marketplace install cycle: all plugin tests pass; Skill contract tests and skills-ref validate pass.
• Public install from this branch (pgrundev/pgx#feat/claude-plugin-marketplace): full clone 53 s / 2.2 GB on disk (192 MB fetch); --sparse .claude-plugin plugins 8 s / 72 MB; plugin installs, claude plugin details pgx → Skills (1) pgx, Hooks (0), MCP servers (0); cache holds only the 84 KB package.
• Interactive session (pty-driven, screens recorded): /plugin marketplace add, /plugin install pgx@pgrundev → scope dialog → "Plugin is now active", Installed tab lists it, /pgx: autocompletes /pgx:pgx, invoking it loads the skill from the plugin cache.
• Live Rails run through the plugin (3 sessions, $1.87): setup via /pgx:pgx (schema-only template, pgx agent setup, hooks once), feature work in a hook-provided branch (migration + tests green; column only in the branch), third session with its own branch; developer PostgreSQL schema byte-identical; all branches cleaned up by the supervisor after the grace period. Uninstall leaves databases, templates, .pgx.toml and hooks intact. Details: docs/pgx/local-dev/validation/2026-10-26-claude-plugin-live.md.

Known cost

/plugin marketplace add pgrundev/pgx clones the repository (fuzz corpora and benchmark logs): 192 MB fetch, 2.2 GB on disk, about a minute. The installed plugin is 84 KB. The in-session command has no sparse option; documented in claude-plugin.md. PGX is not submitted to Anthropic's directory; the submission material is in the doc.

Not merged: awaiting review and authorization.

🤖 Generated with Claude Code