← ClaudeAtlas

safetyprivate-public-splitlisted

Enforce vault privacy boundaries on every export — only content explicitly marked public leaves the local vault. Prevents accidental private data exposure through attestation records, platform exports, or Creator Claw outputs.
frankxai/Starlight-Intelligence-System · ★ 5 · AI & Automation · score 75
Install: claude install-skill frankxai/Starlight-Intelligence-System
# Private/Public Split > Vault content is sovereign. What goes public is the user's explicit choice, not a default. ## When This Skill Activates - Vault content is being prepared for export to a platform adapter - A Claw is generating a public artifact from vault material - Keywords: "export", "publish", "public vault", "share memory", "platform pack" - Default for: Starlight Sentinel ## What This Skill Does Enforces a clear boundary between private vault content (stays local) and public-safe content (can be exported to platform adapters, shared contexts, or the public vault). Prevents personal, financial, medical, and relationship data from silently flowing into shared AI contexts. ## Procedures ### Procedure 1: Entry Classification Before any vault export, classify each entry: ``` PRIVATE (never exported without explicit approval): - Personal names, addresses, family relationships - Financial specifics: account numbers, exact valuations, salary details - Medical, health, or therapy references - Legal matters - Relationship conflicts or sensitive personal dynamics - Entries explicitly tagged: { privacy: "private" } - All Horizon Vault entries (require PR-level review) PUBLIC_SAFE (exported by default): - Frameworks and mental models (no personal attribution required) - Technical architecture patterns - Strategic decisions: goals, priorities, opportunity assessments (non-sensitive) - Creative concepts, voice elements - Professional methodolog