sync-docs

Update marketplace documentation files to match the plugins directory.

Updated Feb 22, 2026
One-click install
npx skills add https://github.com/mikersays/mikersays-plugins --skill sync-docs-mikersays
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sync-docs
Source: https://github.com/mikersays/mikersays-plugins/tree/main/plugins/maintenance/skills/sync-docs
Command: npx skills add https://github.com/mikersays/mikersays-plugins --skill sync-docs-mikersays

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Ensures that all marketplace documentation is up-to-date with the plugin directory, eliminating discrepancies and ensuring accurate information.

Core Features & Use Cases

  • Automatic Syncing: Updates README.md, INSTALL.md, UNINSTALL.md, docs/index.html, and marketplace.json files to match the plugins/ directory.
  • Plugin Management: Handles the addition, removal, and renaming of plugins, propagating changes across all relevant documentation.
  • Consistency Verification: Provides a mechanism to verify the consistency of the documentation after running the skill.

Quick Start

Run the sync-docs skill to update all marketplace documentation to match the current plugin directory.

Frequently Asked Questions about sync-docs

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

FAQPage Schema
How do I keep marketplace documentation in sync with a plugin directory?

To keep marketplace documentation in sync with a plugin directory, you can use an automated syncing skill that reads directory changes and propagates additions, removals, and renames across all relevant documentation files.

What is the best way to update README and marketplace.json after changing plugins?

The best way to update README.md and marketplace.json after changing plugins is to run an automated documentation synchronization process that directly matches these files to your current plugin directory structure.

How does documentation consistency verification work for plugin management?

Documentation consistency verification for plugin management works by checking that files like INSTALL.md, UNINSTALL.md, and marketplace.json accurately reflect the current state of the plugin directory after applying updates.

Can I automatically propagate plugin renaming across all documentation files?

Yes, you can automatically propagate plugin renaming across all documentation files by running a syncing operation that updates README.md, docs/index.html, and marketplace.json to match the renamed entries in the plugin directory.

Does syncing marketplace documentation require manual file editing?

Syncing marketplace documentation does not require manual file editing, as the process uses file reading, editing, and globbing operations to automatically apply plugin directory changes to the relevant documentation files.

Why does my marketplace.json have discrepancies with my plugins folder?

Marketplace.json discrepancies with your plugins folder occur when plugins are added, removed, or renamed without a corresponding documentation update, which requires a synchronization process to eliminate the inconsistencies.