Files and skills

OneMind Mind updates can include Markdown, JSON, YAML, TOML, and plain-text files (UTF-8, max 512 KiB each) that are reviewed and delivered alongside the Mind's instructions.

Review the selected files and their Project/tool scope before submitting them with a Mind update. Uploading a file into a draft does not approve or apply it.

After approved native sync, the tool-specific receipt at .one-mind/mind-content/<tool>.json lists the exact approved files and hashes. Skills are delivered under .agents/skills/onemind-<tool>/; hooks and resources live under .one-mind/tools/<tool>/. If only the legacy .one-mind/mind-content.json exists, use it only when its toolKey matches the tool. Other tools' sections and receipts are outside that tool's scope.

The CLI also has explicit onemind files and onemind skills workflows; see CLI command reference. Governed file replacement, direct file download, Project-skill installation, and host-plugin installation have separate permissions. A plugin update does not update your Project skills.

Automatic analysis is off by default. Explicit proposals work without enabling it. Opt-in analysis uses bounded supported evidence; it does not read proprietary host chat databases or automatically turn arbitrary files into approved memory. The Automation mode setting in Settings > Preferences controls whether onemind may generate Minds and how it syncs approved Minds; see Notifications and settings.