Box
ReviewAudited by ClawScan on May 10, 2026.
Overview
This is a coherent Box CLI integration, but it uses Box service credentials and can change cloud files, so users should use least-privilege credentials and review mutating actions.
Before installing, make sure you trust the Box CLI package, store Box credential JSON files outside the workspace with restrictive permissions, use a least-privilege Box app or service account, and require confirmation before the agent uploads, downloads, or changes Box files or metadata.
Findings (3)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
If the Box app or service account has broad permissions, the agent may be able to access or modify many Box files through the CLI.
The skill requires user-supplied Box service credentials. This is expected for a Box CLI integration, but those credentials may grant broad Box account or enterprise access depending on how the Box app is configured.
Instead, it expects Bring Your Own Credentials using: - Client Credentials Grant (CCG) --- recommended - JWT Server Auth --- optional
Use a dedicated Box app or service account with the minimum required scopes and folder access, and avoid enterprise-wide permissions unless truly needed.
A mistaken or overly broad command could upload content to the wrong folder or alter metadata on Box files.
The documented Box CLI operations include uploading files and changing metadata. These actions are aligned with the skill purpose, but they can mutate cloud-hosted business data.
box files:upload ./report.pdf --parent-id 0 ... box files:metadata:add 123456789 --template-key employeeRecord --data "department=Sales"
Require explicit user approval for mutating Box commands and verify file IDs, folder IDs, and metadata templates before execution.
Installing a CLI globally gives that package code execution ability in the user's environment.
The skill points to a global npm installation of the Box CLI. This is central to the skill's purpose, but users should still verify package provenance because no pinned package version is shown in the provided artifacts.
kind: npm ... package: "@box/cli" ... global: true
Install only the official Box CLI from trusted sources, consider pinning a known-good version, and keep it updated through normal package-management practices.