slm-switch-profile

Switch between isolated memory profiles with independent databases and graphs.

206|34|Updated Feb 5, 2026
One-click install
npx skills add https://github.com/qualixar/superlocalmemory --skill slm-switch-profile
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: slm-switch-profile
Source: https://github.com/qualixar/superlocalmemory/tree/main/ide/skills/slm-switch-profile
Command: npx skills add https://github.com/qualixar/superlocalmemory --skill slm-switch-profile

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Isolate contexts by switching between memory profiles to prevent cross-contamination of memories, graphs, and patterns across projects.

Core Features & Use Cases

  • Profile switching: quickly move between isolated memory spaces for work, personal, or client projects.
  • Profile management: create, list, and activate multiple profiles with independent databases and knowledge graphs.
  • Use case: maintain separate knowledge bases for different clients, teams, or initiatives to avoid data leakage.

Quick Start

Switch to the work profile to begin using its isolated memory space.

Frequently Asked Questions about slm-switch-profile

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I isolate memory contexts for different projects to prevent data leakage?

You can isolate memory contexts by switching between memory profiles, which maintains separate knowledge bases with independent databases and graphs for different projects. This prevents cross-contamination of memories, graphs, and patterns across work or client environments.

What's the best way to manage multiple isolated memory spaces for different clients?

Managing multiple isolated memory spaces involves creating, listing, and activating separate memory profiles for each client or team. Each activated profile maintains its own independent database and knowledge graph to ensure strict context isolation.

Do I need a local SuperLocalMemory installation to switch memory profiles?

Yes, switching memory profiles requires a local SuperLocalMemory V3 installation. This local setup provides the foundational environment needed to execute profile management commands and maintain strict isolation guarantees across separate memory spaces.

How does profile switching work when moving between work and personal projects?

Profile switching works by activating a specific memory profile, which instantly transitions your active memory space to an isolated environment with its own database. This allows you to quickly move between work, personal, or client contexts without mixing stored knowledge graphs.

What commands are available for memory profile creation and listing?

Available commands include switch-profile to activate a specific memory space, --create to generate a new isolated profile, and list-profiles to view all existing contexts. These commands enable full lifecycle management of your isolated memory databases.

When should I use separate memory profiles instead of a single shared context?

You should use separate memory profiles in multi-profile scenarios like consulting for different clients, separating work and personal tasks, or managing distinct team initiatives. This prevents cross-contamination of patterns and knowledge graphs across unrelated project contexts.