skills-to-vault-synclisted

# Skills-to-Vault Synchronization Pattern > When Hermes skills hold richer operational content than Obsidian vault files, other agents sharing the vault cannot access Hermes skills. This creates a knowledge asymmetry: Hermes works well, other agents work with stubs. ## When to Use This Skill - Setting up multi-agent Obsidian vault (Hermes + Codex + Claude Code) - Vault audit reveals thin/stub files in `02-Rules/` or other layers - User says "other agents should know this too" or "put this in the vault" - Content production quality differs between agents - After a migration that created minimal stub files ## The Problem During V7.1 migration (2026-06-06), profile files like `Profile-web-ops.md` and `Profile-social-ops.md` were migrated into `02-Rules/Content-Standards/`. The migration created **minimal stubs** (35-50 lines each). Meanwhile, Hermes skills retained **full operational detail** (500+ lines) from iterative refinement. **Result:** Skills = rich operational knowledge. Vault stubs = skeleton outlines. Other agents see only skeletons. ## Detection Compare vault `02-Rules/Content-Standards/` files against corresponding skills: | Vault File | Lines | Corresponding Skill | Lines | Gap | |---|---|---|---|---| | `Content-Rules.md` | 51 | `armor-content-writing` | 500+ | Missing: 10-step workflow, SEO audit (14 items), link verification, anti-fabrication, product writing patterns | | `Social-Media-Video.md` | 49 | `armor-social-media-workflow` + `armor-video-content