three-source-model-for-skills-creates-drift-risk

Maintaining three copies of skills (live runtime at /root/.claude/skills/, local repo at /root/helix/, and GitHub remote) creates the same drift failure mode as the dual ~/.claude.json divergence pattern. Two authoritative sources maximum: live runtime (what Claude Code reads) + remote GitHub backup (disaster recovery). A local intermediate clone is pure duplicity — fully reconstructable from either authoritative source and should be removed.

Related

• three-way-file-duplicity-creates-unacceptable-drift-risk
• docker
• helix-skill-deployed-vs-backup-path-distinction
• ephemeral-tmp-pattern-for-zero-drift-github-sync
• salesforce
• docker-build-cache-accumulates-without-cron-prune
• helix-skills-live-outside-aj-workspace-git
• deferred-queue-path-inode-equivalence-home-root
• helix-backup-vs-live-audit-method
• helix-backup-audit-methodology-via-temp-clone
• flush-log-grows-unbounded-without-rotation