Google Docs Update Document

v1.0.2

Atomic node skill to update a Google Doc using the gog CLI.

0· 78·1 current·1 all-time

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for zvirb/google-docs-update-document.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Google Docs Update Document" (zvirb/google-docs-update-document) from ClawHub.
Skill page: https://clawhub.ai/zvirb/google-docs-update-document
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Required binaries: gog
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install google-docs-update-document

ClawHub CLI

Package manager switcher

npx clawhub@latest install google-docs-update-document
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
The skill's name and description match the SKILL.md instructions: it expects the gog CLI and instructs using `gog docs write` / `gog docs edit` to update a document. There are no unrelated binaries, env vars, or config paths declared.
Instruction Scope
Instructions are narrowly scoped to issuing gog commands to write or edit a Google Doc. The SKILL.md does not direct the agent to read unrelated files, environment variables, or exfiltrate data. It is somewhat terse (no explicit error-handling/auth guidance), but stays within the stated task.
Install Mechanism
This is an instruction-only skill with no install spec or downloads — lowest-risk install profile. It assumes the gog binary already exists on PATH.
Credentials
No env vars are requested, which is consistent with an instruction-only CLI wrapper. However, the gog CLI itself will use whatever local Google authentication is configured (user's gog/gcloud credentials or config files). That implicit use of the user's Google account is expected but worth noting because the skill will perform write operations with those credentials.
Persistence & Privilege
The skill is not always-enabled and is user-invocable; autonomous invocation is allowed (platform default). It does not request system-wide configuration changes or persistent installation steps.
Assessment
This skill simply runs the gog CLI to edit Google Docs. Before installing: 1) Verify you trust the gog CLI binary on the system (is it an official tool and properly installed?). 2) Confirm which Google account the gog CLI is authenticated as, since the skill will use those credentials to modify documents. 3) Limit the account's permissions where possible (use a service account or account with only the needed Drive permissions). 4) Because the SKILL.md is terse, review how errors are reported and test the commands manually first to ensure behavior matches your expectations.

Like a lobster shell, security has layers — review code before you run it.

Runtime requirements

Binsgog
latestvk97egcy4v0wx1fwb7yymd40sbn85ns1g
78downloads
0stars
3versions
Updated 1d ago
v1.0.2
MIT-0

Lean Philosophy (Principles)

  • Kaizen (改善): This skill is an atomic node, broken down into its simplest, smallest component to eliminate waste and ensure perfection.
  • Standardized Work (Hyojun Sagyo): This node represents the most efficient, standardized path for this specific task before automation.
  • Jidoka (自働化): This node includes autonomous defect detection. It relies on the CLI's self-healing loop and will report errors if the update fails.

Google Docs Update Document

This skill allows the agent to write or insert text into an existing Google Document using the native CLI.

Cognitive Directives

WHEN [Text needs to be added, written, or updated in a Google Doc] THEN [Execute the native terminal command gog docs write <docId> --text "..." or gog docs edit <docId> <find> <replace>]

Schema Example

{
  "command": "gog docs edit doc_id_123 \"old text\" \"new text\""
}

Expected Output

A JSON object or confirmation string indicating the update was successful.

Comments

Loading comments...