Setup Marketplace Sync

Synchronize Claude Code plugins from multiple marketplaces into a centralized repository.

5|3|Updated Nov 6, 2025
One-click install
npx skills add https://github.com/ralphbean/claude-marketplace-sync --skill setup-marketplace-sync
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Setup Marketplace Sync
Source: https://github.com/ralphbean/claude-marketplace-sync/tree/main/skills/setup-marketplace-sync
Command: npx skills add https://github.com/ralphbean/claude-marketplace-sync --skill setup-marketplace-sync

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Organizations and individuals often need to aggregate Claude Skills from various sources (teams, departments, public repositories) into a single, curated marketplace. Manually managing this can be time-consuming, error-prone, and difficult to keep up-to-date. This skill automates the entire synchronization process, ensuring your marketplace is always current and correctly structured.

Core Features & Use Cases

  • Automated Marketplace Aggregation: Seamlessly pull skills from multiple GitHub or GitLab repositories into one central marketplace.
  • CI/CD Integration: Automatically sets up GitHub Actions or GitLab CI/CD pipelines to run syncs on a schedule or trigger.
  • Origin Tracking & Denylisting: Maintain clear provenance for all skills and exclude unwanted plugins from child marketplaces.
  • Use Case: An enterprise wants to create a master marketplace for all its internal Claude Skills, combining contributions from engineering, operations, and product teams, while also including a few approved public skills. This skill sets up the automated system to build and maintain that master marketplace.

Quick Start

Set up automated marketplace synchronization for my repository. I'm using GitHub. I want to sync from 'https://github.com/my-org/engineering-skills' with tag prefix 'engineering' and 'https://github.com/my-org/operations-skills' with tag prefix 'operations'.

Frequently Asked Questions about Setup Marketplace Sync

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate syncing Claude Skills from multiple GitHub and GitLab repositories?

Marketplace sync automates aggregating Claude Skills from multiple GitHub or GitLab repositories into a centralized marketplace. Set up a .sync-config.json file with your marketplace sources, define exclude patterns, and configure GitHub Actions or GitLab CI/CD pipelines to run syncs on schedule or trigger.

Can I sync Claude Skills from both GitHub and GitLab into one marketplace?

Yes, marketplace sync supports both GitHub and GitLab as sources simultaneously. Configure multiple marketplace sources in your .sync-config.json, assign tag prefixes to each source for origin tracking, and the CI/CD pipeline aggregates them into a single repository.

What do I need to set up before running an automated marketplace sync?

You need a .sync-config.json file defining marketplace metadata and sources array, CI/CD pipeline setup for GitHub Actions or GitLab CI, repository URLs for each source, tag prefixes for origin tracking, and exclude patterns to filter unwanted skills from child marketplaces.

How do I exclude specific skills when syncing from multiple marketplace sources?

Define exclude patterns in your .sync-config.json to filter out unwanted plugins from child marketplaces during sync. Patterns are evaluated against each source, allowing you to maintain a curated marketplace while aggregating from multiple teams or repositories.

Does marketplace sync maintain the origin of each skill when aggregating from multiple sources?

Yes, marketplace sync maintains clear provenance for all skills using tag prefixes assigned to each source. Origin tracking ensures you can identify which team or repository contributed each skill, supporting enterprise governance and skill attribution.