gws-docs-write▌
googleworkspace/cli · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Append plain text to the end of a Google Docs document.
- ›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
docs +write
PREREQUISITE: Read
../gws-shared/SKILL.mdfor auth, global flags, and security rules. If missing, rungws generate-skillsto create it.
Append text to a document
Usage
gws docs +write --document <ID> --text <TEXT>
Flags
| Flag | Required | Default | Description |
|---|---|---|---|
--document |
✓ | — | Document ID |
--text |
✓ | — | Text to append (plain text) |
Examples
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 — Global flags and auth
- gws-docs — All read and write google docs commands
How to use gws-docs-write on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add gws-docs-write
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches gws-docs-write from GitHub repository googleworkspace/cli and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate gws-docs-write. Access the skill through slash commands (e.g., /gws-docs-write) or your agent's skill management interface.
Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
Task Automation & Efficiency
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Knowledge Enhancement
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Quality Improvement
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client with skill support
- ›Clear understanding of task or problem to solve
- ›Willingness to iterate and refine outputs
Time Estimate
15-45 minutes depending on use case complexity
Installation Steps
- 1.Install skill using provided installation command
- 2.Test with simple use case relevant to your work
- 3.Evaluate output quality and relevance
- 4.Iterate on prompts to improve results
- 5.Integrate into regular workflow if valuable
Common Pitfalls
- ⚠Expecting perfect results without iteration
- ⚠Not providing enough context in prompts
- ⚠Using skill for tasks outside its intended scope
- ⚠Accepting outputs without review and validation
Best Practices▌
✓ Do
- +Start with clear, specific prompts
- +Provide relevant context and constraints
- +Review and refine all outputs before using
- +Iterate to improve output quality
- +Document successful prompt patterns
✗ Don't
- −Don't use without understanding skill limitations
- −Don't skip validation of outputs
- −Don't share sensitive information in prompts
- −Don't expect skill to replace human judgment
💡 Pro Tips
- ★Be specific about desired format and style
- ★Ask for multiple options to choose from
- ★Request explanations to understand reasoning
- ★Combine AI efficiency with human expertise
When to Use This▌
✓ 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.
Learning Path▌
- 1Familiarize yourself with skill capabilities and limitations
- 2Start with low-risk, non-critical tasks
- 3Progress to more complex and valuable use cases
- 4Build expertise through regular use and experimentation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.6★★★★★25 reviews- ★★★★★Benjamin Robinson· Dec 20, 2024
gws-docs-write has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Mia Menon· Dec 12, 2024
gws-docs-write fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Michael Singh· Nov 11, 2024
Solid pick for teams standardizing on skills: gws-docs-write is focused, and the summary matches what you get after install.
- ★★★★★Henry Rao· Nov 3, 2024
I recommend gws-docs-write for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Kofi Mehta· Oct 22, 2024
Solid pick for teams standardizing on skills: gws-docs-write is focused, and the summary matches what you get after install.
- ★★★★★Evelyn Mehta· Oct 2, 2024
I recommend gws-docs-write for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Evelyn Singh· Sep 9, 2024
Useful defaults in gws-docs-write — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Yash Thakker· Sep 1, 2024
Solid pick for teams standardizing on skills: gws-docs-write is focused, and the summary matches what you get after install.
- ★★★★★Henry Gill· Sep 1, 2024
Registry listing for gws-docs-write matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Dhruvi Jain· Aug 20, 2024
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