Dvlin Dev Claude Code Marketplace
dvlin-dev-claude-code-marketplace is a Claude Code plugin for the Build phase that provides an internal plugin marketplace standard for consistent team installs.
by dvlin-dev · github.com/dvlin-dev/claude-code-marketplace
Adopt an internal Claude Code plugin marketplace standard (wegic-oriented) so teams install and govern plugins consistently.
Add it to Claude Code
Install the plugin in Claude Code. One command, paste-ready.
/plugin install dvlin-dev-claude-code-marketplace@dvlin-dev/claude-code-marketplaceBuilt to be called by your agent
Skillselion is itself an MCP server. Your agent can pull this entry and a paste-ready install config straight from the API - no copy-paste.
Retrieve this entry with skillselion.get_details("plugin:dvlin-dev/claude-code-marketplace") and the paste-ready config with skillselion.get_install_config("plugin:dvlin-dev/claude-code-marketplace").
What it does
dvlin-dev-claude-code-marketplace is a one-plugin Claude Code bundle from dvlin-dev that encodes how an internal marketplace should expose plugins to Claude Code, with wegic and standardization called out in its metadata. Solo builders on small teams—or indie devs aligning with a larger org template—install it when they need a consistent way to register internal plugins instead of copying ad-hoc manifests from chat threads. It does not replace public Skillselion-style discovery; it complements build-phase integrations by giving you a governed plugin source your agent can trust. Expect documentation-oriented setup around internal channels and naming standards rather than autonomous coding or memory runtimes. Use it when you are standardizing Claude Code across contributors and want one canonical marketplace entry point before you layer skills, MCP servers, and workflows on top.
Highlights
- Single-plugin bundle packaging an internal Claude Code marketplace convention
- Oriented toward wegic and standardized internal plugin distribution
- Community-listed repo (dvlin-dev/claude-code-marketplace) for repeatable team installs
- Focus on plugin standardization, not custom skill authoring or runtime orchestration
- Lightweight keyword set: claude, internal, plugin, standard, wegic
Why builders use it
Teams paste one-off plugin instructions into docs and every developer ends up with a different Claude Code extension setup.
After you add the marketplace plugin, internal Claude extensions follow one wegic-oriented standard so agents load the same approved plugins across machines.
At a glance
- Type - Plugin in Productivity.
- Adoption - 0 installs, 0 stars, 0 votes.
FAQ
Who is dvlin-dev-claude-code-marketplace for?
It is for Claude Code users who want an internal, standardized plugin marketplace pattern—especially teams referencing wegic-style conventions.
When should I use dvlin-dev-claude-code-marketplace?
Use it at the start of build when you are wiring Claude Code to shared internal plugins before everyone installs different unofficial bundles.
How do I add dvlin-dev-claude-code-marketplace to my agent?
Install the plugin from the dvlin-dev/claude-code-marketplace repository via Claude Code’s plugin flow, then point your team docs at the bundled marketplace standard for subsequent plugin adds.
Comments
Share how you use dvlin-dev-claude-code-marketplace, gotchas, or tips for other indie builders.
No comments yet - be the first to share how you use it.