Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
From marketplace-builder
Generate the gated SessionStart install hook plus cloud-setup.sh and a "use skills directly" fallback so the marketplace is usable in Claude Code web/cloud sessions. Use to make a marketplace cloud-aware.
How this skill is triggered — by the user, by Claude, or both
Slash command
/marketplace-builder:cloud-setupThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Make the marketplace usable in cloud/web sessions: install prerequisites at
Make the marketplace usable in cloud/web sessions: install prerequisites at session start, gated so local sessions are unaffected, with a skill-file fallback when the hook can't run.
Read ${CLAUDE_PLUGIN_ROOT}/knowledge/marketplace-conventions.md (§5, cloud-aware).
cloud-setup.sh. Copy
${CLAUDE_PLUGIN_ROOT}/templates/cloud/cloud-setup.sh to
.claude/cloud-setup.sh; replace __NAME__ with the marketplace handle.
It self-gates (acts only in cloud/CI sessions) and runs once per session,
delegating to scripts/dev-setup.sh.
SessionStart hook. Merge the SessionStart block from
${CLAUDE_PLUGIN_ROOT}/templates/cloud/settings.json into
.claude/settings.json (create it if absent). The command is
bash .claude/cloud-setup.sh.
Fallback. In the root CLAUDE.md, add a short "Cloud sessions" note: if the
hook did not run (e.g. settings not loaded), the user can invoke the
marketplace's skills directly and run bash scripts/dev-setup.sh by hand.
Verify + report. Run bash -n .claude/cloud-setup.sh, validate
.claude/settings.json with jq, and report what was wired.
Guides completion of development work by verifying tests, detecting environment, and presenting structured options for merge, PR, or cleanup.
Enforces test-driven development: write failing test first, then minimal code to pass. Use when implementing features or bugfixes.
Guides creation and editing of skills using test-driven development with pressure scenarios and subagents to verify agent compliance.
npx claudepluginhub bdfinst/plugin-builder --plugin marketplace-builder