box status

box-status

Read-only snapshot of the workspace state. Use as pre-flight before heavy operations, audit summary, or sanity check.

Usage

/box-status [--refresh-tier] [--check-indexes] [--team=<name>]

Reports

• Workspace name, root ID, created/updated timestamps, plugin version
• Account: tier, custom metadata templates available?, body search?, Box AI tools?, AI Units?, Box Hubs?, AI Studio?, retention/legal-hold?, compliance declared
• Box MCP variant (official mcp.box.com or community/deprecated — runs box-mcp-check for detail)
• Routing per skill: which path each will take (box-recall → index files? Metadata Query? AI Ask?)
• Workspace contents: total memories, by status, by kind, total binary files, companions count
• Per-team stats: counts + access status
• Most recent memories (top 5)
• Top tags (top 5)
• Settings + AI opt-in flags
• Index drift suspicions (only with --check-indexes)
• Actionable issues with concrete next steps

When to use

• Session start (especially for sensitive workflows)
• Before a box-index-rebuild
• For audit reports
• When the user asks "what's in my Box workspace?"

Don't

• Don't modify anything — this is read-only by design
• Don't auto-refresh tier unless asked (--refresh-tier)

See also

• box-tier-detect — what tier-detect itself reports (subset of box-status)
• box-mcp-check — what box-status calls for the MCP section
• Source: skills/box-status/SKILL.md