mcp-sync-verify

Verify the dotfiles MCP sync pipeline is healthy after editing master/overlay/override configs or sync code.

IndexedLicense unknown★ 1

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/stevencarpenter-mcp-sync-verify

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

About

Verify the dotfiles MCP sync pipeline is healthy after editing master/overlay/override configs or sync code. USE THIS SKILL whenever the user edits anything under `home/.config/mcp/` (mcp-master.json, machine/work.json, machine/personal.json, machine/lab.json, overrides/*.json, templates), edits anything under `mcp_sync/` (sync.py, cli.py, templates/*.base.json|.toml, tests), or asks any of "sync MCP configs", "verify MCP", "did the MCP sync break", "did mcp-master change anything", "what changed in opencode/cursor/claude.json", "preview the MCP fan-out", "dry run mcp_sync", "I edited mcp/machine/*.json: does it still apply cleanly", "is codex/cursor/junie/lmstudio still in sync". Bias toward triggering after edits to the MCP source-of-truth files even if the user does not explicitly ask: this skill never writes to deployed paths, so the cost of an unnecessary trigger is one tmpdir.

Use cases: data, writing, agent-building

Reviews

Write a review

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools: No tools found
Secrets: None asked for
Install scripts: None found
Runs as: Python package

Network hosts it talks to 1

codeload.github.com · found in install command

Files it touches

~/.claude/skills/mcp-sync-verify

What's inside

Skill name: mcp-sync-verify
Description: Verify the dotfiles MCP sync pipeline is healthy after editing master/overlay/override configs or sync code. USE THIS SKILL whenever the user edits anything under `home/.config/mcp/` (mcp-master.json, machine/work.json, machine/personal.json, machine/lab.json, overrides/*.json, templates), edits anything under `mcp_sync/` (sync.py, cli.py, templates/*.base.json|.toml, tests), or asks any of "sync MCP configs", "verify MCP", "did the MCP sync break", "did mcp-master change anything", "what changed in opencode/cursor/claude.json", "preview the MCP fan-out", "dry run mcp_sync", "I edited mcp/machine/*.json: does it still apply cleanly", "is codex/cursor/junie/lmstudio still in sync". Bias toward triggering after edits to the MCP source-of-truth files even if the user does not explicitly ask: this skill never writes to deployed paths, so the cost of an unnecessary trigger is one tmpdir.
License: unknown
Instructions: 123 lines in SKILL.md · view on GitHub

Before installing

Ships executable scripts
Instructions read files in your home folder (~/.ssh, ~/.aws…)

Agent Skills spec issues

files: referenced but missing: scripts/hooks-sync.sh
body: contains an absolute path from the author's machine

Files (3)

SKILL.md
dry_run_diff.sh · scripts/
print_target_paths.py · scripts/

The license isn't open source, so the instructions aren't shown here. Read SKILL.md on GitHub

Signals

Stars: 1
Forks: 0
Open issues: 0
Last commit (this folder): Oct 17, 2026 (11 days ago)

From GitHub (fetched Oct 24, 2026).

Details

License: License unknown
Repository: github.com/stevencarpenter/dotfiles
First seen: Oct 24, 2026
Last checked: Oct 24, 2026
Source: GitHub github-graphql

More from stevencarpenter

Cite this page

mcp-sync-verify skill. Agent Mart. https://agentmart.dev/skills/stevencarpenter-mcp-sync-verify (last updated 2026-10-24)