sync-plugin

Synchronize private plugin assets to a public repository with frontmatter validation.

15|4|Updated Mar 7, 2026
One-click install
npx skills add https://github.com/vzco/arc-probe --skill sync-plugin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sync-plugin
Source: https://github.com/vzco/arc-probe/tree/main/plugins/arc-probe/skills/sync-plugin
Command: npx skills add https://github.com/vzco/arc-probe --skill sync-plugin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Sync plugin components from a private repository to a public distribution repository to streamline publishing and ensure consistency.

Core Features & Use Cases

  • Frontmatter validation: ensures every skill's SKILL.md contains valid YAML frontmatter with a name and description.
  • Safe publishing: copies plugin directories to the public repo while preserving structure and avoiding leakage of private sources.
  • Release coordination: aligns versions and automates commit and push steps for reproducible releases.

Quick Start

Run the sync-plugin workflow to copy private plugin files to the public repository, validate frontmatter, and push updates.

Frequently Asked Questions about sync-plugin

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

FAQPage Schema
How do I sync private plugin development changes to a public repository?

To sync private plugin development changes to a public repository, you can automate the process by copying plugin directories, validating SKILL.md YAML frontmatter, and executing commit and push steps for reproducible releases.

What does frontmatter validation check when publishing plugin assets?

Frontmatter validation checks that every skill's SKILL.md file contains valid YAML frontmatter with a required name and description before copying plugin assets to the public distribution repository.

How can I coordinate version synchronization between private and public repositories?

You can coordinate version synchronization between private and public repositories by automating repository copy operations and aligning versions during the commit and push steps for reproducible releases.

Does this plugin synchronization method prevent leaking private source code?

Yes, safe publishing prevents leaking private source code by copying only the designated plugin directories to the public repository while preserving the required structural integrity.

What is the best way to automate releasing plugin updates across different environments?

The best way to automate releasing plugin updates across environments is using a workflow that performs frontmatter validation, repository copy operations, version synchronization, and automated commit and push steps.

Why do I need to validate SKILL.md files before pushing plugin updates?

You need to validate SKILL.md files before pushing plugin updates to ensure every skill contains valid YAML frontmatter with a name and description, preventing invalid configurations from reaching the public repository.