sync-configs

Audit cross-platform configurations and detect drift across Claude, Cursor, Gemini, and Codex.

1|Updated Aug 16, 2025
One-click install
npx skills add https://github.com/ReefBytes/Manifest --skill sync-configs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sync-configs
Source: https://github.com/ReefBytes/Manifest/tree/main/configs/claude/skills/sync-configs
Command: npx skills add https://github.com/ReefBytes/Manifest --skill sync-configs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Align and verify cross-platform configurations across Claude, Cursor, Gemini, and Codex by detecting drift, validating symlink targets, and surfacing inconsistencies that impede reliable automation.

Core Features & Use Cases

  • Symlink integrity checks across platforms to ensure all per-platform paths point to canonical sources.
  • Cross-platform config drift detection with automated reporting and guidance for remediation.
  • Canonical config validation against canonical sources and per-platform settings to prevent divergence in deployment environments.
  • Remediation guidance for drift scenarios, including when to re-symlink, refresh canonical files, or reconcile MCP entries.

Quick Start

Run the drift check workflow to identify mismatches and prepare remediation steps.

Frequently Asked Questions about sync-configs

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

FAQPage Schema
How do I detect config drift across Claude, Cursor, Gemini, and Codex deployments?

Config drift detection across Claude, Cursor, Gemini, and Codex is handled by auditing per-platform MCP settings against canonical sources. The workflow validates cross-platform configurations and generates reporting with actionable guidance for resolving any divergence.

What is cross-platform config drift and when do I need to validate it?

Cross-platform config drift happens when per-platform settings diverge from canonical sources across different deployment environments. You need to validate it when broken symlinks or misaligned MCP entries impede reliable automation across Claude, Cursor, Gemini, and Codex.

How do I verify symlink integrity and fix broken links in my MCP settings?

Symlink integrity verification checks that per-platform paths point to canonical sources to prevent broken links. When drift is detected, remediation guidance indicates whether you should re-symlink targets, refresh canonical files, or reconcile MCP entries.

Does this config validation approach work without external dependencies?

Yes, this config validation approach works without external dependencies, relying entirely on its internal advanced logic to enforce cross-platform validation. It independently audits canonical config alignment and MCP settings to identify broken links and deployment divergence.

What is the best way to reconcile MCP entries across multiple platforms?

The best way to reconcile MCP entries is by running a drift check workflow that compares per-platform settings against canonical sources. This identifies exact divergence points and outputs actionable remediation guidance for reconciling the configurations.

Why does my cross-platform configuration drift after updating canonical files?

Cross-platform configuration drifts after updating canonical files when per-platform symlinks break or local MCP settings are not refreshed. The drift detection audit surfaces these inconsistencies and provides remediation guidance to re-symlink or reconcile local deployments.