Skip to content
Get packs

Guide · Agent skill

How to use the Google Docs Append Writer agent skill

Updated · written with AI from the project's own documentation and checked against our catalogue data

The Google Docs Append Writer is an agent skill, a packaged set of instructions that teaches an AI agent how to do one specific task. This one teaches the agent to add plain text to the end of an existing Google Doc by running the gws command-line tool. This guide explains what the skill does, how to install it, how to ask for it, and what to check before you rely on it.

Google Docs Append Writergoogleworkspace/cli · Apache-2.0

Quick start

  1. 1Install gws. Install the gws command-line tool and confirm it is on your PATH.
  2. 2Configure authentication. Set up Google authentication through the gws shared setup described in the gws-shared skill.
  3. 3Get the document ID. Copy the ID of the Google Doc you want to append to.
  4. 4Download and unzip the skill. Download the ZIP from this page and unzip it into ~/.claude/skills/ or a project's .claude/skills/ folder.
  5. 5Or upload in the Claude apps. In the Claude apps, go to Settings → Capabilities → Skills and upload the ZIP.
  6. 6Make a request. Ask the agent in plain language to add text to your named document, including the document ID.
  7. 7Confirm the change. Read the text the agent plans to add, then approve it before the write runs.

What the skill makes the agent do

Without this skill, an agent has no reliable knowledge of how to write to Google Docs. With it installed, when you ask the agent to add a line or paragraph to a Google Doc, it knows the exact command and flags to use: gws docs +write with a document ID and the text to add.

The skill is limited on purpose. It only appends plain text at the end of the document body. It does not format text, add headings or tables, create new documents, or edit and delete existing content. The skill notes that rich formatting requires the raw batchUpdate API instead. The skill also tells the agent to confirm with you before running the write command.

  • Appends plain text to the end of a document body
  • Needs a document ID and the text to add
  • Asks for your confirmation before writing
  • Does not format text, create documents, or edit or delete content
gws docs +write --document <ID> --text <TEXT>

Install the skill (ZIP download or Claude apps upload)

Download the skill as a ZIP file from this page. The package contains one file, SKILL.md. You can install it in one of three places, depending on how you work.

For Claude Code, unzip the file into your personal skills folder at ~/.claude/skills/, or into a project's .claude/skills/ folder if you want the skill available only in that project. For the Claude apps, go to Settings → Capabilities → Skills and upload the ZIP.

  • Personal use with Claude Code: unzip into ~/.claude/skills/
  • Single project: unzip into the project's .claude/skills/ folder
  • Claude apps: Settings → Capabilities → Skills, then upload the ZIP

Set up the requirements before you start

The skill does not do the Google setup itself. You need three things in place: the gws command-line tool installed and available on your PATH, Google authentication configured through the shared gws setup, and the Google Docs document ID of the target document.

The skill refers to a gws-shared skill for authentication, global flags and security rules. If that file is missing, the source says to run gws generate-skills to create it. The skill's metadata lists gws as the required binary and gws docs +write --help as the command help to check.

  • gws installed and on the PATH
  • Google auth configured through the gws shared setup (gws-shared skill)
  • The document ID of the Google Doc you want to write to
  • If the gws-shared file is missing, run gws generate-skills
gws docs +write --help

How to trigger the skill with a natural request

You do not need to type the command yourself. Describe the change in plain language and name the document. The agent should recognise the request as an append task and use this skill. Include the document ID, since the command requires it, or make sure the agent can find it.

Because the skill requires confirmation, expect the agent to show you the planned change and wait for approval before it writes anything. Read the text it plans to add before you say yes.

  • "Add a new line to my meeting notes doc, ID 1AbC...: Decided to move launch to May."
  • "Append today's checklist items to the end of the Ops log document."
  • "Put this paragraph at the bottom of doc DOC_ID."

Examples of what the command does

The source's example appends a single greeting to a document. Replace DOC_ID with your real document ID and put your own text in quotes. Because the flag is --text, keep the text to plain characters; for anything styled, the source points you to the batchUpdate API.

Each run adds the text at the end of the document body. Running the command twice adds the text twice, so check before repeating a request.

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

Safety notes: scripts and network access

This skill runs scripts and uses the network. It calls the gws tool, which sends requests to Google on your behalf using the authentication you configured. Only install the skill if you trust the gws tool and the account it is signed in to, and review the commands the agent proposes.

The skill's own safety guidance is the confirmation rule: the command is a write, so the agent should confirm with you before executing it. Keep that step in place, especially when the agent runs without you watching.

  • Runs scripts and uses the network
  • Writes to a real Google Doc, so changes are not undone by this skill
  • Review the planned text and document ID before approving

Tips for reliable results

Keep requests specific: name the document ID and give the exact text. Text is always inserted at the end of the document body, so plan entries in the order you want them to appear.

For logs, meeting notes or checklists, plain text is usually enough. If you need headings, bold text, lists or tables, this skill is the wrong tool; use the raw batchUpdate API from the gws-docs skill's reference instead.

  • Give the document ID and exact text in each request
  • Remember that entries always go at the end of the body
  • Use the gws-docs skill (linked from the source) for all read and write commands
  • Use the raw batchUpdate API for any formatting

What people use it for

  • Adding dated entries to a running project log or changelog kept in a Google Doc.
  • Appending meeting notes or action items to the end of a shared notes document.
  • Adding checklist lines to a team document from a script or agent workflow that already uses gws.
  • Automating simple, plain-text updates to a document as part of a larger agent task.

Frequently asked questions

How do I install the Google Docs Append Writer skill?

Download the ZIP from this page and unzip it into ~/.claude/skills/ for personal use, or into a project's .claude/skills/ folder. In the Claude apps, go to Settings → Capabilities → Skills and upload the ZIP. You also need the gws tool and Google authentication set up.

What do I need to use the gws-docs-write skill?

You need the gws command-line tool installed and on your PATH, Google authentication configured through the gws shared setup, and the Google Docs document ID of the target document. If the gws-shared skill file is missing, the source says to run gws generate-skills.

Is this skill free to use?

The skill is licensed under Apache-2.0, as listed on this page. Check the licence file in the source repository for the full terms. This page does not state any price for the skill.

Can the skill format text, add headings or create documents?

No. The skill only appends plain text to the end of a document body. For rich formatting, the source says to use the raw batchUpdate API instead. It does not describe creating new documents or editing existing content.

What should I do if the agent cannot write to my document?

Check that gws is on your PATH, that Google authentication is configured through the gws-shared setup, and that the document ID is correct. The source's CLI help command, gws docs +write --help, shows the flags and is a good first check.

How does this compare with other ways to add text to Google Docs?

This skill is a narrow option: it adds plain text to the end of a document through the gws CLI. If you need editing, deletion, formatting or document creation, the source points to the raw batchUpdate API and the wider gws-docs skill, which covers all read and write commands.

New agent skills, repos and AI tools — every week

The best new skills and open-source projects, the fastest-growing repos, and one free prompt. Five minutes to read. Unsubscribe anytime.

Our verdict

Use this skill if you keep logs, notes or checklists in a Google Doc and want an agent to add plain-text entries at the end, or if you already automate with the gws CLI. Pick something else if you need formatting, headings, tables, editing or deletion, or if you cannot set up gws authentication.

Download the skill