Batch syncs session learnings, campaign history, and insights to persistent memory. Use before ending productive sessions to preserve knowledge across chats.
How this skill is triggered — by the user, by Claude, or both
Slash command
/digital-marketing-pro:sync-memoryThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Batch sync current session learnings, insights.json entries, and campaign history to the persistent memory layer. Ensures valuable knowledge from this session is preserved for future sessions without requiring the user to manually save each item via `/digital-marketing-pro:save-knowledge`. Syncs incrementally — only new items since the last sync checkpoint — so repeated syncs are fast, idempote...
Batch sync current session learnings, insights.json entries, and campaign history to the persistent memory layer. Ensures valuable knowledge from this session is preserved for future sessions without requiring the user to manually save each item via /digital-marketing-pro:save-knowledge. Syncs incrementally — only new items since the last sync checkpoint — so repeated syncs are fast, idempotent, and safe. Handles the full pipeline from diff detection through storage to checkpoint update, with detailed reporting on what was synced, skipped, or failed. Run this before ending a productive session to capture everything worth remembering.
The user must provide (or will be prompted for):
all (insights + campaigns + session learnings), insights-only (only insights.json entries — performance data, metric snapshots, and automated learnings), or campaigns-only (only campaign data, retrospective learnings, and strategy decisions). Default is alltrue to ignore the last sync checkpoint and re-sync everything regardless of previous sync state. Useful after data corruption, vector DB migration, index rebuild, or when the local index and persistent storage may be out of alignment. Default is false (incremental sync from last checkpoint)true to preview what would be synced without actually storing anything. Shows the full diff, payload previews, and estimated storage impact for review before committing. Useful for auditing what has accumulated since the last sync~/.claude-marketing/brands/_active-brand.json for the active slug, then load ~/.claude-marketing/brands/{slug}/profile.json. Apply brand voice, compliance rules for target markets (skills/context-engine/compliance-rules.md), and industry context. Also check for guidelines at ~/.claude-marketing/brands/{slug}/guidelines/_manifest.json — if present, load restrictions. Check for agency SOPs at ~/.claude-marketing/sops/. If no brand exists, ask: "Set up a brand first (/digital-marketing-pro:brand-setup)?" — or proceed with defaults.memory-manager.py --action sync-insights to load the last sync checkpoint from ~/.claude-marketing/brands/{slug}/memory/sync-state.json. Identify the last sync timestamp, items previously synced (by content hash), and any partial sync that needs resuming from its failure point. If force sync is requested, reset the checkpoint to epoch zero.campaigns/, and session learnings accumulated in the current working context. Apply sync scope filter (all, insights-only, campaigns-only) and exclude patterns to build the candidate set.memory-manager.py --action prepare-store to structure the metadata payload — auto-detect content_type based on source (insight entries become performance-insight, campaign retrospectives become campaign-learning, strategy decisions become campaign-learning, guidelines become guideline), apply auto-detected tags plus any user-specified batch tags, and set source to sync.memory-manager.py --action get-memory-status to verify which vector database is available and confirm it has capacity for the sync batch. Report estimated storage impact (items to add, storage utilization after sync). If no persistent storage is connected, store locally and recommend setup.sync-state.json with the new checkpoint timestamp, cumulative items synced, items skipped, items failed (with content hashes for retry), and per-layer storage status. If any items failed, their hashes are queued for automatic retry on the next sync run.A structured sync report containing:
/digital-marketing-pro:sync-memory before ending a session ensures no learnings are lostnpx claudepluginhub indranilbanerjee/digital-marketing-proSaves brand knowledge to persistent vector memory (Pinecone or Qdrant) with metadata tagging for semantic retrieval across sessions.
Manages a three-tier HOT/WARM/COLD memory system for SEO/GEO projects. Automatically loads hot cache (80 lines) each session, promotes/demotes entries, archives stale data, and supports cross-session memory queries.
Persistent intelligence layer that accumulates deal knowledge, competitive intel, product context, and team patterns over time — making every other skill smarter with use. This skill should ALWAYS be checked at the start of any GTM-related task. It reads from and writes to a structured knowledge base so that insights from one conversation carry into the next. Use this skill on every interaction that involves sales, marketing, CS, partnerships, or RevOps context. Also trigger proactively when the user shares deal outcomes, competitive intel, product updates, rep feedback, or customer insights — capture it even if they didn't ask you to.