Skip to content
skillsafebeta
← Report library
Purpose / Documents

Gws Docs Write Skill Security Audit

What the author says it does (original text)

Google Docs: Append text to a document.

Independent security check

No obvious risks found in this check

Files checked
1
Risks found
0
Could it run dangerous commands?Looks for programs run straight after downloading, remote control of your computer, and hidden commands.No risks found
Could it expose your files or keys?Looks for uploads of files containing passwords or keys, and keys written directly in the code.No risks found
Could it delete files or keep running?Looks for broad file deletion, disk overwrites, and programs set to start automatically.No risks found
Could it bypass safety checks?Looks for skipped website security checks, excessive file access, or actions that skip your approval.No risks found
Could it mislead the AI or hide text?Checks the skill instructions for requests to ignore you, influence the report, or hide text in invisible characters.No risks found
Could it change links or payment recipients without asking?Looks for forced referral or payment changes combined with instructions to hide the change.No risks found

Inside this skill

5 instruction sections

The Skill calls `gws docs +write` to append user-provided plain text to a Google document selected by document ID.

View source
SKILL.md:23In the instructionsOpen original file
```bashgws docs +write --document <ID> --text <TEXT>```
SKILL.md:30In the instructionsOpen original file
|------|----------|---------|-------------|| `--document` | ✓ | — | Document ID || `--text` | ✓ | — | Text to append (plain text) |

The appended content is inserted at the end of the document body, changing the remote Google document. The Skill explicitly requires user confirmation before execution.

View source
SKILL.md:41In the instructionsOpen original file
- 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.

The Skill depends on the local `gws` program and requires a shared authentication, security, and global-flags guide that was not included in the evidence; if it is missing, it suggests running a generation command. Because that shared file is not visible, this audit cannot verify its authentication scope or security rules.

View source
SKILL.md:8In the instructionsOpen original file
    category: "productivity"    requires:      bins:        - gws    cliHelp: "gws docs +write --help"---
SKILL.md:16In the instructionsOpen original file
> **PREREQUISITE:** Read `../gws-shared/SKILL.md` for auth, global flags, and security rules. If missing, run `gws generate-skills` to create it.
Start here · InstructionsSKILL.md
gws-docs-write
Lines connect the instruction file to its sections, not an observed execution order. Select a section to read the source.
Files and check records1 files

Coverage and gaps

Content covered in each file

These are the source ranges included in this check, not a guarantee that every issue has been resolved.

  • SKILL.mdFull text included

This report is for the version above. We read the available code and instructions without running the skill or checking extra packages it installs. This is not a promise of safety: a different version or setup may behave differently.

  • SKILL.mdInstructions

Operations mentioned in code and instructions

Run commands
SKILL.md:22In the instructionsOpen original file
```bashgws docs +write --document <ID> --text <TEXT>
SKILL.md:35In the instructionsOpen original file
```bashgws docs +write --document DOC_ID --text 'Hello, world!'
Lines read
51
File checksum (to compare versions)
8012b9cc08805f24d9c59a1a02e81c21eb0e162950feb672a4b57a9ff3256508