Google Drive Upload File

Atomic node skill to upload a file to Google Drive using the gog CLI.

Security Scan

The skill is internally consistent with its stated purpose (it simply instructs the agent to run the gog CLI to upload a local file), but it relies on the user's local gog configuration and can upload any file the agent is allowed to read — review for sensitive-file/exfiltration risk.

Purpose & Capability

Name, description, required binary (gog), and runtime instruction (gog drive upload <localPath>) are aligned. There are no unrelated binaries, packages, or environment variables requested.

Instruction Scope

The SKILL.md gives a single, focused instruction to run the gog CLI to upload a specified local path. It does not attempt to read unrelated files or environment variables, but it also does not constrain which local paths may be uploaded or describe authentication — so an agent using this skill could upload any file it has filesystem access to.

Install Mechanism

There is no install spec (instruction-only), so nothing is written to disk by the skill itself. This is low-risk and consistent with the skill's simplicity.

Credentials

No environment variables are declared or requested, which is coherent. However, the skill implicitly depends on the user's gog CLI being configured (OAuth tokens/credentials stored on the host). That means the skill will use whatever Drive access the local gog configuration grants — a potential exfiltration vector if the agent is allowed to pick arbitrary local files.

Persistence & Privilege

The skill is not always: true and does not request persistent or elevated platform privileges. It is user-invocable and can be invoked autonomously by the agent (platform default), which is expected behavior for a CLI wrapper skill.

Assessment

This skill is coherent and does what it says: it runs your local gog CLI to upload a specified file to Google Drive. Before installing or enabling it, verify that (1) you trust the agent and the environment because the skill can upload any local file the agent can read, (2) your gog CLI is configured and has Drive access (the skill will use those stored credentials), and (3) you limit the agent's permissions or test in a safe environment if you have sensitive files. If you want tighter controls, require the agent to explicitly name allowed paths or add checks that prevent uploading sensitive directories.}

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

This skill allows the agent to upload a local file to Google Drive using the native CLI.

Cognitive Directives

WHEN [A local file needs to be uploaded to Google Drive] THEN [Execute the native terminal command gog drive upload <localPath>]

Schema Example

{
  "command": "gog drive upload /path/to/local/file.txt --json"
}

Expected Output

A JSON object confirming the uploaded file and its Drive ID.