Skillv0.1.4

ClawScan security

drivectl - your command-line tool for interacting with Google Drive · ClawHub's context-aware review of the artifact, metadata, and declared behavior.

Scanner verdict

BenignApr 30, 2026, 1:56 AM

Verdict: benign
Confidence: medium
Model: gpt-5-mini
Summary: The skill's requirements and instructions align with its stated purpose (controlling Google Drive via a CLI); the included install script downloads a prebuilt binary from a GitHub release which is coherent but carries the usual supply-chain caveats.
Guidance: This skill is internally coherent for controlling Google Drive via a CLI, but before installing: 1) verify the upstream project (ghchinoy/drivectl) and inspect its releases/source so you trust the binary you’ll download; 2) note the installer verifies a checksum hosted in the same release, but checksum validation can be skipped on systems without sha256sum/shasum—avoid installing if you can't validate integrity; 3) prefer running the binary in an isolated environment (container or limited-permission account) if you have doubts; 4) when authenticating, grant only the minimal OAuth scopes needed (avoid broad scopes like full drive unless required) and prefer service-account or limited credentials where appropriate; 5) be mindful that the tool's 'call' subcommand can invoke arbitrary Google APIs (including changing permissions), so avoid using high-privilege credentials in untrusted agent environments.

Review Dimensions

Purpose & Capability: okName/description (Google Drive CLI) match the instructions: all runtime steps and examples are about listing, downloading, Docs/Sheets operations, and calling Google APIs via Discovery. The need for a client_secret.json / OAuth tokens is expected for Google API access.
Instruction Scope: noteSKILL.md stays on-topic (how to run drivectl, authenticate, examples for Drive/Docs/Sheets). It documents a powerful 'drivectl call' that can hit any Google Workspace API via Discovery — functionally appropriate for a discovery-capable CLI but increases the range of actions the tool can perform (including changing permissions). It does not instruct reading unrelated system files or exfiltrating data to unknown endpoints.
Install Mechanism: noteThe only install artifact is scripts/install.sh which downloads a release tarball from GitHub (ghchinoy/drivectl) and verifies a checksum file hosted on the same release. This is a common pattern but carries supply-chain risk: the binary is fetched from an external release and checksum verification may be skipped if the host lacks sha256sum/shasum (the script warns and proceeds).
Credentials: okThe skill does not request environment variables or unrelated credentials. It requires the user to provide Google OAuth client secrets / authenticate with Google, which is proportionate for accessing Drive/Docs/Sheets. No unrelated secrets are requested.
Persistence & Privilege: okThe skill is not marked always:true, does not request system-level persistence, and contains no instructions to modify other skills or global agent configuration. The only persistence referenced is the CLI's local token cache (behavior of drivectl itself), which is expected.