Skip to content

box tier detect

mrdulasolutions edited this page May 25, 2026 · 1 revision

box-tier-detect

Probe Box account capabilities and cache the result so other skills don't re-probe. Internal-first; called by box-init, box-status, and the AI skills. Can also be called directly.

Usage

/box-tier-detect [--refresh]

What it probes

  1. Cache — if tier_detected_at is within 30 days, return cached
  2. Box MCP identity via who_am_i — records box_mcp_official (true if mcp.box.com, false otherwise)
  3. Enterprise metadata-scope probe — Business+ check
  4. Template-create permission probe — admin vs non-admin
  5. Box AI tools availability — official MCP exposes them; community MCPs may not
  6. AI Units availability — best-effort
  7. Box Hubs support — Enterprise Plus check
  8. AI Studio agent eligibility — Enterprise Advanced check
  9. Storage / upload limits → tier inference
  10. Cross-check: if signals contradict, prefer "stale OAuth token after tier upgrade" diagnosis over "ambiguous tier"

Output

Writes to _box-memory.json.capabilities:

capabilities:
  custom_metadata_templates: <bool>
  body_search: <bool>
  max_file_size_mb: <int>
  retention_policies: <bool>
  legal_holds: <bool>
  box_ai_tools_available: <bool>
  ai_units_available: <bool>
  box_hubs: <bool>
  ai_studio_agents: <bool>
  box_mcp_official: <bool>
  compliance: [<user-declared>]

When to use

  • Called automatically by box-init on first setup
  • After a Box plan upgrade — run with --refresh
  • When troubleshooting "feature not available" errors

Stale OAuth detection

When signals contradict (e.g., max upload size suggests Business+ but enterprise scope rejected), the skill prefers the diagnosis "stale OAuth token after tier upgrade" — most common cause, concrete fix (disconnect + reconnect Box MCP). See Operational Notes Note 2.

See also

Clone this wiki locally