Gmail Draft Update Subject

Atomic node skill to update the subject of an existing Gmail draft.

Security Scan

The skill is an instruction-only, single-purpose node that tells the agent to run a specific gog CLI command to update a Gmail draft subject — its requests and instructions are proportionate to that purpose, though it omits details about authentication and the provenance of the gog binary.

Purpose & Capability

Name/description match the actual behavior: the SKILL.md instructs running a gog CLI command to update a Gmail draft subject. Requiring a gog binary is consistent with using a native CLI to talk to Gmail.

Instruction Scope

Instructions are narrowly scoped to executing `gog gmail drafts update <draftId> --subject ... --json` with a 3-retry loop and JSON validation. The SKILL.md does not instruct the agent to read unrelated files or env vars. It does not explain how authentication is obtained; it implicitly assumes the gog CLI is already authenticated.

Install Mechanism

No install spec and no code files (instruction-only) — nothing is written to disk by the skill itself, which is the lowest-risk install model.

Credentials

The skill requires no environment variables and lists only the gog binary. That is minimal and proportional — however, real Gmail access will depend on the gog CLI's own auth/config (not declared here), so the user should verify where gog stores credentials and which account it uses.

Persistence & Privilege

The skill is not always-enabled and does not request elevated or persistent platform privileges. It can be invoked autonomously (platform default), which is expected for skills, but that is not itself a red flag here.

Assessment

This skill is narrowly focused and internally consistent, but before installing: (1) confirm what the 'gog' binary is, where it came from, and that you trust its publisher; (2) verify that gog is already installed and configured for the correct Gmail account (it likely performs its own OAuth/auth flow and stores credentials on disk); (3) test the example command manually to see what permissions and credentials are used and what the CLI does; (4) be aware that although the skill requests no env vars, the CLI may read local credentials/config files — ensure those are acceptable for the agent to use. If you can't verify gog's provenance or account configuration, treat the skill as higher risk.

Lean Philosophy (Principles)

• Kaizen (改善): This skill is an atomic node, strictly limited to updating the subject of a draft, preventing complex multi-field string constructions.
• 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.

This skill allows the agent to update the subject of an existing Gmail draft using the native CLI.

Cognitive Directives

WHEN [The subject of a Gmail draft needs to be set or updated] THEN [Execute the native terminal command gog gmail drafts update <draftId> --subject "..." --json]

Schema Example

{
  "command": "gog gmail drafts update draft_id_123 --subject \"Invoice\" --json"
}

Jidoka Validation Loop

1. Try: Execute the command.
2. Evaluate: Check the JSON response to confirm the subject was updated.
3. Correct/Fail: If it failed or hallucinated parameters, retry up to 3 times (max_retries=3).
4. Proceed: Return the confirmation.

Expected Output

A JSON object confirming the draft was updated.