About skill-marketplace-creator
A skill for planning a skill ecosystem and its marketplace, aimed at teams preparing skills for distribution. It covers marketplace shape, supply strategy, governance, and machine-checkable publication gates, starting with a repository-first approach.
Key features
- 01Marketplace model selection
- 02Skill supply strategy planning
- 03Publication validation gates
- 04Repository structure and governance
- 05Catalog generation guidance
Use cases
- 01Planning a repository-based skill catalog
- 02Defining review gates for community submissions
- 03Preparing launch channels and near-term actions
Install
Copy the command and run it in a terminal.
$
npx skills add https:/ / github.com/ sylphxai/ skills --skill skill-marketplace-creatorAfter installing, type/skill-marketplace-creatorin Claude Code to confirm it loaded.
Bundled files
References and scripts installed along with SKILL.md.
agents/openai.yamlreferences/catalog-generation-patterns.mdmarketplace-playbook.mdscripts/check_skill_folder.pyDetails
From the project READMESkill Marketplace Creator
Use this skill to build a skill ecosystem that is useful, trustworthy, and distribution-ready.
Workflow
- Identify marketplace shape: repo-only, static catalog, API-backed registry, private enterprise registry, or full community marketplace.
- Read
references/marketplace-playbook.mdfor architecture and quality gates; loadreferences/catalog-generation-patterns.mdonly when implementing the derived catalog surface. - Define the skill supply strategy: internal flagship skills, curated third-party skills, community submissions, or agent-generated drafts.
- Require validation before publication: schema, trigger quality, safety, license, examples, and evals.
- Produce concrete repo structure, governance, launch channels, and next 48-hour actions.
Guardrails
- Start repository-first. GitHub is the first marketplace, trust surface, and contribution flow.
- Curate before scaling. A small set of excellent skills beats a huge undifferentiated directory.
- Keep content original. Distill workflows into Sylphx-owned structure, examples, and wording; do not copy or lightly paraphrase third-party writing.
- Make quality machine-checkable where possible.
- Separate skills from MCP tools: skills teach behavior; MCP servers provide capabilities.
Output format
Recommended shape: <repo-only | static catalog | API registry | full marketplace>
Repository layout:
<tree>
Quality gates:
- <gate>
Launch plan:
1. <action>
2. <action>
3. <action>
Risks:
- <risk and mitigation>
For repo validation scripts, inspect or run scripts/check_skill_folder.py if present.
When not to use
- Use
source-to-skill-distillerto convert one bounded source into one skill package. - Use
skill-eval-designerto design the evaluation for one skill or workflow. - Do not use this skill to build a runtime tool/MCP marketplace; executable capabilities and permissioned side effects need typed runtime contracts, not
SKILL.mdpackages.
Comments
Markdown supported