mcs-sync Skill
Use this skill to detect changes across all external dependencies (knowledge cache, upstream repos, Elevate, eval-guide plugin, MCP servers, om-cli binary, MS Learn docs, Claude Code plugins) and produce a triage board so a human can decide TAKE or REJECT per change. Never auto-applies. Use when the user asks to 'refre Published by microsoft in MCS-Agent-Builder.
What is mcs-sync Skill?
Use this skill to detect changes across all external dependencies (knowledge cache, upstream repos, Elevate, eval-guide plugin, MCP servers, om-cli binary, MS Learn docs, Claude Code plugins) and produce a triage board so a human can decide TAKE or REJECT per change. Never auto-applies. Use when the user asks to 'refre Published by microsoft in MCS-Agent-Builder. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Documentation
- Writing
- Documentation use cases
- Writing use cases
Technical details
- Install or run with Copy skill directory
When to use mcs-sync Skill
- Use it for documentation.
- Use it for writing.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/MCS-Agent-Builder
- Skill file: .claude/skills/mcs-sync/SKILL.md
What it does
Use this skill to detect changes across all external dependencies (knowledge cache, upstream repos, Elevate, eval-guide plugin, MCP servers, om-cli binary, MS Learn docs, Claude Code plugins) and produce a triage board so a human can decide TAKE or REJECT per change. Never auto-applies. Use when the user asks to 'refre
Skill instructions
MCS Sync — Detect, Understand, Decide Single manifest-driven pipeline for every external dependency. Replaces the deleted /mcs-refresh + tools/refresh-everything.js auto-apply path. The key invariants: 1. Two decisions only — TAKE or REJECT. No middle ground. 2. Never auto-applies — taking a change prints the impacted artifacts and writes an action plan markdown for the user; the orchestrator never edits a downstream file itself. 3. Manual cadence — there is no auto-cron, no session-start auto-fetch. The user runs sync weekly (or on demand). The session-start hook only warns about staleness; it does not invoke sync. Invocation bash Default: detect + understand on all 8 sources, write triage bundle node tools/sync-orchestrator.js npm run sync Single source node tools/sync-orchestrator.js run --source knowledge-cache node tools/sync-orchestrator.js run --source upstream-repos node tools/sync-orchestrator.js run --source elevate node tools/sync-orchestrator.js run --source eval-guide node
Explore related resources
Frequently asked questions
What is mcs-sync?
mcs-sync is a open-source AI agent skill with Copy skill directory. Use this skill to detect changes across all external dependencies (knowledge cache, upstream repos, Elevate, eval-guide plugin, MCP servers, om-cli binary, MS Learn docs, Claude Code plugins) and produce a.
Who is mcs-sync best for?
mcs-sync is best for reusing agent instructions, scripts, and references, documentation workflows, writing workflows.
How do I install mcs-sync?
Install or run mcs-sync using Copy skill directory. Check mcs-sync for the latest setup command.
Is mcs-sync actively maintained?
mcs-sync may need a closer maintenance check before production use.
Auto-fetched from GitHub.
