Google Docs Create Document

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

Security Scan

The skill's requirements and instructions are consistent with its stated purpose (running the gog CLI to create a Google Doc); it is small and instruction-only, but you should verify the gog binary and where it stores credentials before installing.

Purpose & Capability

The skill is an atomic wrapper around the gog CLI to create a Google Doc. Requiring the 'gog' binary matches the stated purpose and there are no unrelated binaries or env vars declared.

Instruction Scope

SKILL.md directs a single, narrowly-scoped action: run `gog docs create <title> --json`. The instructions do not ask the agent to read unrelated files, environment variables, or transmit data to external endpoints beyond the CLI call.

Install Mechanism

There is no install spec (instruction-only), so nothing is downloaded or written by the skill itself. This is the lowest-risk installation model.

Credentials

The skill declares no required environment variables or credentials. This is not inconsistent because the gog CLI commonly uses its own local OAuth/config files. However, the skill implicitly depends on whatever credentials/config the gog CLI needs (OAuth tokens, config files) — the SKILL.md does not document that or where those credentials live.

Persistence & Privilege

The skill is not always-enabled and uses default model invocation behavior. It does not request persistent system presence or modify other skills/configurations.

Assessment

This skill is narrowly scoped and appears coherent, but before installing: 1) Verify the 'gog' binary on your system is the legitimate CLI you expect (check its provenance/version and source). 2) Understand that gog will need Google credentials (OAuth tokens or saved config) stored on the machine — confirm where those are stored and whether you are comfortable allowing an agent to invoke the CLI using them. 3) If you run agents in shared or automated environments, consider whether creating documents via the gog CLI could expose tokens or create documents unintentionally. 4) If you need stronger assurance, run the `gog` command manually first to confirm behavior and error handling, or request the skill author to document authentication and error cases.

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 creation fails.

This skill allows the agent to create a new Google Document using the native CLI.

Cognitive Directives

WHEN [A new Google Doc needs to be created] THEN [Execute the native terminal command gog docs create <title> --json]

Schema Example

{
  "command": "gog docs create \"My New Document\" --json"
}

Expected Output

A JSON object with the new document ID and details.