BOX-Onprem

Report the air-gap trust boundaries for the current session. Confirms Box Drive backend state, disk encryption posture, and identifies which LLM provider is handling agent prompts. Read-only. Use at the start of any sensitive workflow, or when an auditor asks what's closed vs open in the trust model.

Generate a paired companion markdown file for a binary in the local Box Drive workspace. Describes the file contents, key facts, hash-anchored to the current SHA256 of the binary. No chunking, no embedding - the binary stays whole, the companion describes it. FS-only, no Box API. Use when the user references a binary file (PDF, CAD, image, Office doc) and asks to describe, remember, or review it.

Probe the local Box Drive desktop-app mount to confirm the air-gapped backend is ready. Checks the mount path exists, is writable, Box Drive process is running, and reports the linked Box account email. Use when the user wants to verify Box Drive is set up, before running box-init for the first time, or when another skill needs the mount path. Never falls back to the network.

Rebuild a folder's _index.json (or the whole workspace's indexes) by walking the local Box Drive filesystem and re-reading every memory's frontmatter. Also resolves Box Drive .conflict files that arise when two clients write the same index, and detects stale companions whose binary changed. FS-only, no Box API.

Bootstrap a box-memory workspace on the local Box Drive mount. Creates folder structure, writes workspace config, seeds index files. FS-only - no Box API calls, no metadata template creation (the on-prem variant runs Personal-tier behavior; Business+ metadata templates are out of scope for air-gap mode). Use when the user wants to set up a Box-memory workspace under their local Box Drive folder.

Find memories in a local box-memory workspace by ID, wikilink, slug, structured filters, or free text. Reads only from local _index.json files - no Box Search, no Metadata Query API, no network. Use when the user asks what do I know about X, what did we decide, find memories tagged Y, recall, or search my Box memory.

Report the local box-memory workspace state - Box Drive backend health, teams, memory counts by kind/status, recent activity, index health. Read-only. Use when the user asks what's in their workspace, wants a status report, asks if Box Drive is syncing, or wants a sanity check before a heavy operation.

Manage team subtrees in a local box-memory workspace. Create, list, inspect, find cross-team conflicts, or remove a team from config. Folder ACLs are configured in Box (web UI or admin) - this skill creates filesystem structure only and cannot set permissions. FS-only, no Box API.

Save a memory to the local Box Drive workspace as a markdown file with YAML frontmatter and Obsidian-style wikilinks. Append-only - never overwrites. FS-only - no Box API calls; no metadata template instance application. Use when the user says remember, save, log a decision, record an observation, or note that something happened.