Append plain text to the end of a Google Docs document.
Automate repetitive workflows and reduce manual effort
Example: Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example: Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example: Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
Time estimate: 15-45 minutes depending on use case complexity
Prerequisites
Submit your Claude Code skill and start earning
epx add googleworkspace/cli --skill gws-docs-writeCompatible with
Supported agents
Requires a document ID and text string; inserts content at the end of the document body
Write operation that should be confirmed with the user before execution
For rich text formatting, use the raw batchUpdate API instead
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versiongws-docs-writeExecute the skills CLI command in your project's root directory to begin installation:
epx add googleworkspace/cli --skill gws-docs-writeFetches gws-docs-write from googleworkspace/cli and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
.cursor/skills/gws-docs-write
Restart Cursor to activate gws-docs-write. Access via /gws-docs-writein your agent's command palette.
Learn more:View source on GitHubSkills CLI docsAbout CursorWhat are agent skills?
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
gws-people
googleworkspace/cli · Productivity · same repo
docs-cleaner
daymade/claude-code-skills · Documents · tag: docs
backend-to-frontend-handoff-docs
davila7/claude-code-templates · Frontend · tag: docs
openai-docs-skill
am-will/codex-skills · AI/ML · tag: docs
typescript-write
metabase/metabase · Backend · tag: write
pdf-ocr
yejinlei/pdf-ocr-skill · Documents · same category
gws-docs-write has been reliable in day-to-day use. Documentation quality is above average for community skills.
gws-docs-write fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Solid pick for teams standardizing on skills: gws-docs-write is focused, and the summary matches what you get after install.
I recommend gws-docs-write for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Solid pick for teams standardizing on skills: gws-docs-write is focused, and the summary matches what you get after install.
I recommend gws-docs-write for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Useful defaults in gws-docs-write — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Solid pick for teams standardizing on skills: gws-docs-write is focused, and the summary matches what you get after install.
Registry listing for gws-docs-write matched our evaluation — installs cleanly and behaves as described in the markdown.
I recommend gws-docs-write for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
showing 1-10 of 25