You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When the DevOps Toolbox runs on a repo (via wip-release or wip-install), it should detect the repo's interfaces and offer to generate a .claude-plugin/plugin.json manifest. This makes any tool discoverable as a Claude Code plugin.
How it works
Run Universal Installer interface detection on the repo
If the repo has skills, hooks, MCP servers, or agents... ask: "Want to make this a Claude Code plugin?"
If yes, generate .claude-plugin/plugin.json with the right fields (name, version, description from package.json)
Generate the directory structure CC expects (skills/, hooks/, .mcp.json as needed)
Commit it to the repo
Important
This is for anyone using the toolbox, not just us. The prompt should be aware that the user might have their own marketplace or might just want local plugin support. Don't assume wipcomputer.
For our pipeline
For wipcomputer repos, this should be automatic as part of wip-release. No prompt needed. Generate the manifest, update the marketplace repo.
Related
LDM OS SKILL.md now mentions the Claude Code marketplace
What
When the DevOps Toolbox runs on a repo (via wip-release or wip-install), it should detect the repo's interfaces and offer to generate a
.claude-plugin/plugin.jsonmanifest. This makes any tool discoverable as a Claude Code plugin.How it works
.claude-plugin/plugin.jsonwith the right fields (name, version, description from package.json)Important
This is for anyone using the toolbox, not just us. The prompt should be aware that the user might have their own marketplace or might just want local plugin support. Don't assume wipcomputer.
For our pipeline
For wipcomputer repos, this should be automatic as part of
wip-release. No prompt needed. Generate the manifest, update the marketplace repo.Related