gdrive-access_skill

This skill lets you list, download, and sync Google Drive files from CLI using 1Password OAuth, securely.
  • TypeScript

14

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill terrylica/cc-skills --skill gdrive-access

  • SKILL.md7.4 KB

Overview

This skill provides CLI access to Google Drive using 1Password OAuth so you can list, search, download, and sync Drive folders from your terminal. It enforces a mandatory preflight to ensure the helper binary, 1Password credentials, and environment variables are configured before any operation. The tool exports Google Docs/Sheets/Slides to common formats and stores OAuth tokens securely per 1Password UUID.

How this skill works

Before running commands the skill verifies the gdrive binary exists, GDRIVE_OP_UUID is set, and you are signed into the 1Password CLI. A guided setup flow helps discover or create Google OAuth credentials in 1Password, writes a local mise config if requested, and tests the OAuth flow. Drive commands (list, search, info, download, sync) call the local gdrive binary which uses stored tokens under ~/.claude/tools/gdrive-tokens/<uuid>.json.

When to use it

  • You need to list or search files inside a Google Drive folder from the CLI.
  • You want to download single files or export Google Docs/Sheets/Slides to local formats.
  • You need to sync a Drive folder (recursively or not) to a local directory.
  • You prefer centralizing OAuth credentials in 1Password and secure token storage.
  • You want JSON output for automation or piping into other tools.

Best practices

  • Always run the mandatory preflight checklist before any drive command to avoid auth or binary errors.
  • Keep OAuth credentials in a dedicated 1Password item and set GDRIVE_OP_UUID in a gitignored .mise.local.toml.
  • Use the skill’s JSON output option for scripts or CI integration.
  • Confirm your shell has reloaded environment variables after setup (restart shell or source your rc file).
  • Restrict file writes to intended output directories and verify token file permissions (chmod 600).

Example use cases

  • List detailed files in a shared training folder for auditing: gdrive list <folder_id> --verbose.
  • Download a single report: gdrive download <file_id> -o ./report.pdf.
  • Sync a project folder to local disk for offline work: gdrive sync <folder_id> -o ./project_dir -r.
  • Search for all PDFs modified after a date: gdrive search "mimeType = 'application/pdf' and modifiedTime > '2026-01-01'".
  • Automate exports of Google Docs to docx as part of a CI job using --json output to capture IDs.

FAQ

Build it by running the provided install/build steps in the scripts directory (bun install && bun run build) before using the skill.

Where are OAuth tokens stored and are they secure?

Tokens are stored at ~/.claude/tools/gdrive-tokens/<uuid>.json with chmod 600; they are organized by 1Password UUID for multi-account support.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational
gdrive-access skill by terrylica/cc-skills | VeilStrat