crm-synclisted

Keep the CRM-Engine knowledge layer in Anton's vault in sync with the live CRM code on GitLab. Trigger on “/crm-sync“, “обнови знания по CRM“, “пересними CRM“, “что изменилось в CRM коде“, “re-decompose the CRM“, “sync crm knowledge“, “resync crm“
tonydzi/second-brain-starter-kit · ★ 8 · AI & Automation · score 76

Install: claude install-skill tonydzi/second-brain-starter-kit

## ⚖️ ШАГ 0 — СНАЧАЛА БИБЛИЯ (обязательно, origin: anton 2026-07-26) Перед ЛЮБЫМ действием этого скилла подними выстраданные правила Библии по лидам: ```bash python3 ~/.claude/scripts/bible_leads.py # карта (0 токенов) python3 ~/.claude/scripts/bible_leads.py --grep <тема> # срез ``` Идёт РАНЬШЕ `outreach_log.py check` и раньше RECALL по человеку. Нет правила в Библии → это находка, после работы занести через `/intake`, а не импровизировать молча. Канон: `reglament-lyubaya-rabota-s-lidami-snachala-bibliya` · `_Bible-Outreach-MOC` · CLAUDE.md §9.5 # /crm-sync - keep the CRM knowledge layer fresh The CRM (CHARM) is Anton's proven engine on GitLab. We reverse-engineered it once (2026-06-19) into a linked vault layer so his digital twin can `/ask` how the CRM works. Code keeps changing; this skill stops that knowledge from going stale silently. It is the recurring half of the standing rule `evaluate-recurring-into-routine`. **What this is NOT:** not a re-decompose-from-scratch. It is a DIFF-DRIVEN refresh: pull, see what changed, update only the notes that map to the changed code. ## Where everything lives - **Code (read-only clone, 16 repos):** `[путь владельца]` (memory `crm-gitlab`). - **Decomposition audit (HTML, source of the notes):** `[путь владельца]` (`Functional-Map.html`, `Know-How-Decomposition.html`, `Architecture-Deep.html`). - **Vault knowledge layer:** `$OBSIDIAN_VAULT/05-Resources/CRM-Engine/` - `_CHARM-CRM-Engine-MOC.md` (hub) - `crm-ar