← ClaudeAtlas

memory-promotelisted

Promote a personal-scope session learning into team scope through curated review. Strips private-tagged content and secret-shaped strings, then produces a reviewable artifact (PR-style proposal) instead of writing shared memory directly. Use when a personal memory note is worth sharing with the team. Enforces .harness/memory-scopes.json promotion rules.
LucasSantana-Dev/sharekit-profile · ★ 1 · Data & Documents · score 70
Install: claude install-skill LucasSantana-Dev/sharekit-profile
# Memory Promote Extends cooperative-mode memory isolation from "never leak" to "curated sharing". Personal memory stays private by default; sharing is an explicit, reviewable act. Policy: `.harness/memory-scopes.json` (promotion requires review; private tags never promote). ## Flow 1. **Select.** Identify the personal-scope note to promote (`~/.claude/projects/<slug>/memory/` or `.agents/memory/personal/`). If the user gave no path, list recent personal notes and let them pick. 2. **Strip.** Remove, in order: - `<private>...</private>` tagged spans entirely (never promoted, per policy) - secret-shaped strings (tokens, keys, emails, internal hostnames, personal paths) — replace with a `[redacted: <kind>]` placeholder - names of people not on the team, unless the user confirms 3. **Propose.** Write the stripped note to a review artifact, never directly to shared memory: - target: `.agents/memory/proposals/<YYYY-MM-DD>-<slug>.md` - include a header: source scope, author, date, what was stripped 4. **Review gate.** Run `hooks/memory-scope-gate.sh` semantics against the proposal: if any `<private>` tag or personal-scope path reference survives, stop and report — do not submit. Present the diff to the user for explicit approval. 5. **Submit.** Only after user approval: push the proposal through the team vault — `bash scripts/team-memory-sync.sh push <proposal.md>` (requires `.harness/team-vault.json`; the transport re-checks for `<pri