Identity Manager

Before installing or enabling this skill, consider the following: - It will scan every conversation turn and create/update persistent identity files (identity/<slug>/entry.md), a central memory index (memory/identities.json), and an append-only 'soul' file. Expect data to be stored on-disk and retained long-term. - The metadata does not list the config paths or workspace files it reads/writes; ask the author which filesystem paths are used and where data is stored/backed up. Verify storage location and permissions in your environment. - The skill may persist mentions and contact details (email, phone) if they appear in chats. If you handle sensitive or regulated data, do not enable this skill without confirming retention/delete policies and access controls. - The skill enforces mandatory writes and append-only critical logs before every reply. In shared or audited environments this may be acceptable, but it can leak context into long-lived logs. Confirm who can read the created files and whether they are included in backups or external syncs. - If you want to proceed: test in a sandboxed workspace first, review the templates and memory/schema.json to confirm what fields will be recorded, and request the author add explicit metadata declaring required config paths and a data-retention/deletion policy. Consider disabling autonomous invocation or limiting the skill to user-invoked only until you are confident about its storage behavior.