Agent skill · Audited from source
gws-docs-write
skill · googleworkspace/cliApache-2.0 licenceAudited 31 Oct 2026 · source d6cca85ff77c
Is it safe? Yes — SAFE, grade B (89/100). We read this skill's source at commit d6cca85ff77c and found no filesystem, network or shell access and no hard-coded secrets. What it does: Google Docs: Append text to a document.
Cite
Cite this page
ModelsAtlas. “gws-docs-write (googleworkspace/cli)”. Retrieved 31 Oct 2026. https://modelsatlas.com/skills/googleworkspace/gws-docs-write
Trust audit
Audit 0.4.1 · source read 31 Oct 2026
SAFE means nothing in the source contradicts what the skill says it does. Grade B is shared by 16,667 of 17,602 audited skills.
What the source does
- FilesystemNone observedNo reads or writes in the source
- NetworkNone observedNo outbound calls in the source
- ShellNone observedNo commands run in the source
- DependenciesPinnedNothing floats
- SecretsNone foundNo keys in source
Five audit layers
| Layer | What we check | Result | Findings |
|---|---|---|---|
L0 Provenance | Repo owner, licence, archive status, activity | PASS | 0 |
L1 Static source | Secrets, path traversal, supply chain, hidden code | NA | 0 |
L2 Instructions | Prompt injection, authority framing, hidden directives | PASS | 0 |
L3 Inventory | The files and declarations match the source | PASS | 0 |
L4 Sandbox | Run in isolation and watch behaviour | SKIPPED why | 0 |
Gates applied: no behavioural pass.
Findings (0)
No findings at any severity. We re-audit when the source changes.
Audit 0.4.1 · source sha d6cca85ff77c · 31 Oct 2026Report an issue or request a re-scan
Provenance
Who published it, and what the verdict is pinned to
- Publishergoogleworkspace GitHub organizationOwner of the repository this skill is read from
- Source foldergoogleworkspace/cli/skills/gws-docs-writeThe exact folder we audited
- LicenceApache-2.0As the repository states it
- Commit pinned for this verdictd6cca85ff77cA new audit runs when the source changes
- Repository statusNot archivedPushed today
- Sandboxed runNot runSkills are read, not executed; layer L4 is skipped
What it tells the agent
Full source on GitHub ↗Its description: Google Docs: Append text to a document.
---
name: gws-docs-write
description: "Google Docs: Append text to a document."
metadata:
version: 0.22.5
openclaw:
category: "productivity"
requires:
bins:
- gws
cliHelp: "gws docs +write --help"
---
# 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
```bash
gws docs +write --document <ID> --text <TEXT>
```
## Flags
| Flag | Required | Default | Description |
|------|----------|---------|-------------|
| `--document` | ✓ | — | Document ID |
| `--text` | ✓ | — | Text to append (plain text) |
## Examples
```bash
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](../gws-shared/SKILL.md) — Global flags and auth
- [gws-docs](../gws-docs/SKILL.md) — All read and write google docs commandsExcerpt, first 1,122 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.
Install
Pinned to the audited commit d6cca85
git clone https://github.com/googleworkspace/cli git -C cli checkout d6cca85ff77c
The author documents no install command, so this uses the repository directly. Our verdict covers commit d6cca85ff77c only.
Works in which agents?
What its own text says, not a test
| Agent | Status | More |
|---|---|---|
| OpenClaw | Mentioned in its text, not tested | Skills for OpenClaw · About OpenClaw |
Audit history
Every audit, every source change
- ✓SAFE B 89 / 100
first audit · source
d6cca85ff77c
README badge
For maintainers · shows the latest audit
[](https://modelsatlas.com/skills/googleworkspace/gws-docs-write/)
The badge shows our verdict and grade for this skill, and links back to this page. It changes when the audit does.
Similar skills
All automation skills →googleworkspace/cli
Google Workspace Events: Renew/reactivate Workspace Events subscriptions.
googleworkspace/cli
Google Workspace Events: Subscribe to Workspace events and stream them as NDJSON.
googleworkspace/cli
Google Drive: Upload a file with automatic metadata.
googleworkspace/cli
Subscribe to Google Workspace events.
googleworkspace/cli
Google Drive: Manage files, folders, and shared drives.
googleworkspace/cli
Read and write Google Docs.
Add this badge to your README
[](https://modelsatlas.com/skills/googleworkspace/gws-docs-write/)
<a href="https://modelsatlas.com/skills/googleworkspace/gws-docs-write/"><img src="https://modelsatlas.com/skills/googleworkspace/gws-docs-write/badge.svg" alt="ModelsAtlas: SAFE B"></a>
Questions about gws-docs-write
What does the gws-docs-write skill do?
Is gws-docs-write safe to install?
What can gws-docs-write access on my machine?
Which assistants does gws-docs-write work with?
How current is this page?
Sources
- github.com/googleworkspace/cli/tree/main/skills/gws-docs-write — the audited source at commit d6cca85ff77c and every finding aboveObserved · 31 Oct 2026
Spotted something wrong? Report a correction · Methodology
Keep going in your AI
Opens with this page as the source. We add nothing else to the prompt.
- What does the gws-docs-write skill do?
- Is gws-docs-write safe to install?
- What can gws-docs-write access on my machine?