plugin-manager
Plugin Manager
Maintain plugin packaging for both ecosystems in a single repository, using a shared plugins/ directory and a shared top-level skills/ source of truth.
Working Rules
- Keep each plugin self-contained in
plugins/<plugin-name>/. - Keep shared reusable skill content in top-level
skills/. - Expose shared skills per plugin via symlinks in
plugins/<plugin-name>/skills/. - Keep MCP config plugin-local at
plugins/<plugin-name>/mcp.json. - Keep both marketplace manifests at repo root:
.claude-plugin/marketplace.json.cursor-plugin/marketplace.json
Required Plugin Layout
For every plugin, ensure this layout exists:
More from neondatabase/agent-skills
neon-postgres
Guides and best practices for working with Neon Serverless Postgres. Covers getting started, local development with Neon, choosing a connection method, Neon features, authentication (@neondatabase/auth), PostgREST-style data API (@neondatabase/neon-js), Neon CLI, and Neon's Platform API/SDKs. Use for any Neon-related questions.
33.0Kclaimable-postgres
>-
736neon-postgres-egress-optimizer
>-
705neon-postgres-branches
>-
47skill-creator
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
28