From claude-code-harness
Automates Google Workspace file operations (Drive, Sheets, Docs, Slides) using gogcli: parse URLs, select auth accounts, run read-only checks before writes.
How this skill is triggered — by the user, by Claude, or both
Slash command
/claude-code-harness:gogcli-opsThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Standardize gogcli usage: verify auth, resolve IDs from URLs, default to read-only checks, then run the minimum command needed.
Standardize gogcli usage: verify auth, resolve IDs from URLs, default to read-only checks, then run the minimum command needed.
gog --versiongog auth listpython3 scripts/gog_parse_url.py "<url-or-id>"sheet | doc | slide | file | folder | id | unknown via scripts/gog_parse_url.py.gog sheets metadata <spreadsheetId>gog docs info <docId>gog slides info <presentationId>gog drive get <fileId> or gog drive permissions <fileId>gog auth listgog auth statusgog auth add <email>--account <email> when multiple accounts exist.python3 scripts/gog_parse_url.py "<url-or-id>"unknown, ask for a direct ID or a different URL.gog drive lsgog drive search "<query>"gog drive get <fileId>gog drive download <fileId>gog drive permissions <fileId>gog sheets metadata <spreadsheetId>gog sheets get <spreadsheetId> <range>gog sheets export <spreadsheetId>gog docs info <docId>gog docs cat <docId>gog docs export <docId>gog slides info <presentationId>gog slides export <presentationId>--plain for stable TSV output.--json when a caller wants structured output.--no-input in non-interactive flows to avoid hanging.gog auth list), check permissions (gog drive permissions <fileId>), and confirm the ID.${CLAUDE_SKILL_DIR}/references/gogcli-cheatsheet.md for a compact command list.scripts/gog_parse_url.py to normalize URLs into IDs before running commands.npx claudepluginhub chachamaru127/claude-code-harness --plugin claude-code-harnessIntegrates Claude Code with Google Workspace (Sheets, Docs, Slides, Gmail, Calendar, Tasks) for read/write operations, file/event management, comments, and multi-account auth via CLI tools.
Automates Google Docs tasks like creating, searching, reading, appending, inserting, and replacing text via Python CLI scripts with standalone OAuth. For local Workspace automation without MCP server.
Creates bite-sized, testable implementation plans from specs or requirements, with file structure and task decomposition. Activates before coding multi-step tasks.