demo-mode-isolation

Enforce strict data isolation between demo sessions and live tenant data.

1|Updated Mar 13, 2026
One-click install
npx skills add https://github.com/Seth-arc/myelin-platform --skill demo-mode-isolation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: demo-mode-isolation
Source: https://github.com/Seth-arc/myelin-platform/tree/main/primary_build_source/docs/skills/1/mnt/user-data/outputs/demo-mode-isolation
Command: npx skills add https://github.com/Seth-arc/myelin-platform --skill demo-mode-isolation

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures that prospect demo environments are completely isolated from live user data and operational systems, preventing any co-mingling of sensitive information while maintaining a realistic user experience.

Core Features & Use Cases

  • Data Isolation: Guarantees demo data is never written to or read from live namespaces.
  • UI Fidelity: Ensures the demo interface and interactions mirror live sessions.
  • Deterministic Walkthrough: Provides a fixed, non-branching narrative path for demos.
  • Use Case: When preparing for a sales demo, use this skill to configure the environment so that all interactions and data displayed are synthetic and cannot affect real user accounts or performance metrics.

Quick Start

Load this skill before writing any demo-mode logic to enforce data isolation.

Frequently Asked Questions about demo-mode-isolation

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

FAQPage Schema
How do I isolate demo data from live tenant environments during a prospect demo?

Isolating demo data from live tenant environments requires defining data contracts and boundary rules that prevent co-mingling. This Skill enforces strict session isolation by requiring a specific demo dataset and boundary rules for initialization.

How does demo mode session initialization work to prevent data co-mingling?

Demo mode session initialization works by requiring a `demoMode: true` flag propagation and specific demo dataset loading. This mechanism ensures synthetic data is loaded exclusively, preventing any reads from or writes to live namespaces.

Can I use synthetic data to maintain UI fidelity during sales demos without affecting live metrics?

Yes, using synthetic data with strict boundary rules ensures the demo interface mirrors live sessions perfectly. This isolation guarantees that prospect demo interactions cannot affect real user accounts or operational performance metrics.

What is the best way to create a deterministic walkthrough sequence for prospect demos?

Creating a deterministic walkthrough sequence involves defining a fixed, non-branching narrative path for demos. This ensures a consistent presentation experience by loading specific demo datasets isolated from live tenant data.

When should I enforce data isolation rules for prospect demo sessions?

You should enforce data isolation rules before writing any demo-mode logic to prepare the sales environment. This ensures all subsequent interactions display strictly synthetic data, preventing sensitive live information from co-mingling during demos.