Gws Docs Write

Google Docs: Append text to a document.

Security Scan

The skill's behavior (a gws CLI call to append to Google Docs) matches its description, but it hides its authentication and global flags in an external SKILL.md (../gws-shared) that isn't included — the missing auth/credential details and external dependency make the package incomplete and potentially risky.

Purpose & Capability

The declared requirement of the 'gws' binary matches the skill's stated purpose (calling a gws CLI to append text to Google Docs). However, the skill does not declare any credentials or env vars itself and instead refers to ../gws-shared/SKILL.md for auth and global flags; that external dependency is required for the skill to function but is not included or documented here.

Instruction Scope

SKILL.md only instructs running 'gws docs +write --document <ID> --text <TEXT>' which is in-scope. But it explicitly requires reading ../gws-shared/SKILL.md for auth and security rules; because that file is missing from this package, runtime behavior (including how credentials are loaded, what scopes are used, and whether additional files or commands are read) is unknown. The instruction to run 'gws generate-skills' if missing could cause the agent to create or modify files — this external-step increases the skill's effective scope without being transparent.

Install Mechanism

No install spec (instruction-only) — nothing is written to disk by the skill itself. This is low-risk from an install-mechanism perspective. The only runtime dependency is the 'gws' binary, which is plausible but should be provenance-checked by the user.

Credentials

The skill requests no env vars or credentials directly, yet it defers auth to ../gws-shared/SKILL.md. That implies the real credential requirements (OAuth tokens, service account keys, or env vars) are defined elsewhere — but they are not declared here for review. This omission prevents assessing whether requested credentials are proportionate.

Persistence & Privilege

The skill does not request persistent/always-on presence and does not indicate modifying other skills or system-wide settings. Autonomy (model invocation) is allowed by default, which is normal; there is no 'always: true' privilege.

What to consider before installing

This skill itself is instruction-only and simply calls a 'gws' CLI to append text to a Google Doc, which is reasonable. However, it explicitly defers authentication and global flags to ../gws-shared/SKILL.md, which is not included here — so you can't review what credentials or scopes will be used. Before installing or enabling this skill: 1) Locate and inspect the referenced gws-shared/SKILL.md to see exactly how auth is performed and what env vars or files are accessed. 2) Verify the provenance of the 'gws' binary (who distributed it, what it does, and whether it requires broad Google scopes or service-account keys). 3) Confirm the skill will only receive the minimal scopes/credentials needed (document write only) and won't access unrelated files or secrets. 4) Test with a disposable Google account or a non-sensitive test document first. If you cannot review the gws-shared file or determine the gws binary's behavior, treat the skill as untrusted.

docs +write

PREREQUISITE: Read ../gws-shared/SKILL.md for auth, global flags, and security rules. If missing, run gws generate-skills to create it.

Append text to a document

Usage

gws docs +write --document <ID> --text <TEXT>

Flags

Flag	Required	Default	Description
--document	✓	—	Document ID
--text	✓	—	Text to append (plain text)

Examples

gws docs +write --document DOC_ID --text 'Hello, world!'

Tips

• Text is inserted at the end of the document body.
• For rich formatting, use the raw batchUpdate API instead.

[!CAUTION] This is a write command — confirm with the user before executing.

See Also

• gws-shared — Global flags and auth
• gws-docs — All read and write google docs commands