SkillMeat for Team Leads and Architects¶
Is this you?¶
Your team is standardizing agent skills, commands, agents, MCP servers, workflows, and rules across projects — a "Golden Path" that every repo should follow, whether it targets Claude Code, Codex, Gemini, or a mix. Without a shared source of truth, that path is a wiki page nobody keeps current, and there's no easy way to tell which projects have actually adopted it versus quietly drifted.
What you get¶
SkillMeat lets you bundle a Golden Path once and check, at any time, where reality has diverged from it:
- Bundles and composite artifacts package a curated set of skills, commands, agents, and other artifacts for reuse across projects — build once, deploy everywhere.
- Three-scope diff comparison — source vs. collection, collection vs. project, and source vs. project — shows exactly what changed and where, with a diff viewer built for large diffs.
- Scheduled artifact reconciliation — an hourly job compares deployed projects against your
collection and surfaces gated drift proposals you explicitly accept or reject. Nothing is ever
auto-written to a project. This capability ships today but is off by default — it's an
opt-in feature flag (
reconciliation_enabled), not the out-of-the-box behavior.
See it work¶
Three-Way Sync Workflow (Web) → is the real, shipped screen this proof point relies on — one tab showing drift across source, collection, and project, with always-labeled diff sides and a unified merge dialog.
Get started¶
There isn't a single "team mode" switch — you build the Golden Path from the same bundle, sync, and deploy primitives every SkillMeat user has, then decide how strictly to enforce it. Start with the guides below.
Go deeper¶
- Bundle & Composite Authoring — package artifacts for reuse across projects and teams.
- Bundle Build, Publish, and Deploy — the full build → publish → deploy workflow for bundles.
- Team Sharing Guide — share collections with teammates using signed bundles and vaults.
- Scheduled Artifact Reconciliation — enable and use the drift-detection and gated-proposal system (default off; here's how to turn it on).
- Sync Quick Reference — drift detection and merge strategy lookup tables.
- Team / Enterprise Admin Walkthrough — the full step-by-step setup path if you're also standing up enterprise-edition governance.
DAG branching is an Enterprise Edition extension
If your team needs isolated artifact branches with explicit merge-back, that's available in
Enterprise Edition behind the dvcs_branching_enabled flag — see
DAG Branching & Merge-Back. Local Edition uses linear version
history.