# Append Plain Text to Google Docs

Adding a short update to an existing document can interrupt a larger workflow. This skill prepares and runs a confirmed Google Workspace CLI append operation.

## Install

```bash
npx skillstore add googleworkspace/gws-docs-write
```

## Metadata

- Status: approved
- Slug: googleworkspace-gws-docs-write
- Version: 0.23.0
- Author version: 0.23.0
- Skillstore revision: r2
- Version status: valid
- Tree hash: 194fa70857d44e75c9770e409c241ebc340ae784069c9cbb0dd0f06ef70e51ce
- Author: googleworkspace
- GitHub username: googleworkspace
- License: MIT
- Repository: https://github.com/googleworkspace/cli/tree/main/skills/gws-docs-write/
- Ref: 286d37c9c189ddd1aafd3548415fb031d1df79d5
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands, filesystem
- Quality score: 80
- Quality tier: silver
- Public page: https://skillstore.pages.dev/skills/googleworkspace-gws-docs-write
- Manifest: https://skillstore.pages.dev/api/skills/googleworkspace-gws-docs-write/manifest

## Capabilities

- Appends supplied plain text to the end of an existing Google Docs document.
- Targets a document by its required Google Docs document ID.
- Uses the gws docs \+write command with document and text parameters.
- Requests user confirmation before performing the document write.
- Directs rich-formatting tasks to the raw batchUpdate API.

## Use Cases

- Record project updates: Append a confirmed plain-text status update to a shared project document.
- Add support notes: Place an approved case summary at the end of a team reference document.
- Publish operational logs: Append concise deployment or maintenance notes to an existing operations document.

## Prompt Templates

### Append a short note

```
Append the exact text "{text}" to Google Docs document {document_id}. Show the planned action and request confirmation before execution.
```

### Add a meeting summary

```
Append this plain-text meeting summary to document {document_id}: {summary}. Preserve the supplied wording and request confirmation before writing.
```

### Prepare an audited update

```
Prepare an append operation for document {document_id} using {text}. Verify the document ID is present, then request confirmation before execution.
```

### Append generated release notes

```
Convert {release_details} into concise plain-text release notes. Present the final text, then request confirmation before appending it to document {document_id}.
```

## Limitations

- It appends plain text only and does not apply rich formatting.
- It requires the gws CLI, authentication, and access to the target document.
- It does not create documents, replace existing text, or insert text at a chosen position.
- It requires both a document ID and the exact text to append.

## Best Practices

- Confirm the exact document ID and final text before every write.
- Use plain text here, and use the raw batchUpdate API when formatting is required.
- Authenticate with the least privilege needed and verify access to the target document.

## Anti Patterns

- Do not execute a document write without explicit user confirmation.
- Do not append secrets or sensitive content without clear authorization.
- Do not use this skill for text replacement, positioned insertion, or rich formatting.

## Security Audit

- Audited at: 2026-08-05T10:52:40.868\+00:00
- Summary: Six findings mistake Markdown code delimiters for shell execution, and three mistake fixed sibling documentation links for uncontrolled traversal. SKILL.md shows expected gws usage, requires confirmation before writing, and contains no semantic evidence of malicious intent.

## Stats

- Views: 66
- Downloads: 9
- Favorites: 0
- Popularity score: 0