marketplace-dev
An agent skill by daymade, from daymade/claude-code-skills. Tags: distribution, github, integration, marketplace, setup.
What it does
Creates and maintains Claude Code plugin marketplaces, consolidates standalone skills into a new or existing suite, and moves skills between suites. Converts any Claude Code skills repository into an official plugin marketplace, generates spec-conforming .claude-plugin/marketplace.json, validates with `claude plugin validate`, tests real installation and cache boundaries, and PRs the upstream repo, encoding hard-won schema/version/description anti-patterns. Use when the user mentions marketplace, plugin support, one-click install, marketplace.json, plugin distribution, auto-update, suite-only migration, "put these skills in a suite", "move this skill into daymade-*", or wants a skills repo installable via `claude plugin install`.
Install
With the skills CLI, which installs into Claude Code, Codex, Cursor and other agents:
npx skills add daymade/claude-code-skills --skill marketplace-devOr copy the skill folder into Claude Code's skills directory by hand (~/.claude/skills for every project, or .claude/skills inside one):
git clone --depth 1 https://github.com/daymade/claude-code-skills
cp -r claude-code-skills/daymade-claude-code/marketplace-dev ~/.claude/skills/marketplace-devSafety box score
Not rated yet. A safety box score grades what a skill and its scripts can reach on the machine of whoever installs it, across eight categories from shell execution to secrets access. Anyone can request one from this page; it is saved for everyone. How the score works.
Source
- Repository
- daymade/claude-code-skills (all skills from this repository)
- Path
- daymade-claude-code/marketplace-dev/SKILL.md
- Branch
- main
- Updated
- 2026-09-20
Related skills
- gangtise-copilot — Gangtise (岗底斯投研) OpenAPI skill suite installer and diagnostic tool.
- skills-search — This skill should be used when users want to search, discover, install, or manage Claude Code skills from the CCPM registry.
- agents-build — Use to extend an existing agent project with memory, app integration, VPC, multi-agent, migration, model, browser, code interpreter, payments.
- agents-connect — Use when connecting your agent to external APIs, tools, or services via Gateway, or restricting tool access with Cedar policies.
- agents-get-started — Use when a developer wants to create a new agent project or get started with AgentCore.
- analyzing-release-readiness — Trigger a pre-merge release readiness review on a GitHub PR, GitLab MR, or local branch.