gws-docs

What This Skill Does

The gws-docs skill provides a powerful interface for interacting with Google Docs directly from your OpenClaw environment. It acts as an automated bridge to the Google Docs API, enabling agents to create, retrieve, and modify document content programmatically. Whether you are generating reports, maintaining logs, or updating collaborative documentation, this skill simplifies the process of document management without requiring manual browser interaction.

Installation

To integrate this skill into your environment, use the following command: clawhub install openclaw/skills/skills/googleworkspace-bot/gws-docs

Ensure you have reviewed ../gws-shared/SKILL.md for necessary authentication configurations. If the shared configuration is missing, execute gws generate-skills to initialize the directory structure. Always verify your permissions within the Google Cloud console to ensure the service account or user token has the appropriate scopes for Google Drive and Docs.

Use Cases

This skill is ideal for tasks requiring structured document generation and data persistence. Common use cases include:

• Automated Reporting: Generate daily summary documents by pulling data from other skills and writing it into a formatted Google Doc.
• Content Management: Create templates for meeting notes or project briefs and auto-populating them with specific metadata.
• Batch Updates: Use the batchUpdate method to perform complex formatting, such as finding and replacing text or inserting new sections across multiple documents.
• Documentation Synchronization: Periodically sync technical documentation or changelogs to a shared workspace, ensuring team members have the latest information without manual copy-pasting.

Example Prompts

1. "Create a new Google Doc titled 'Project Alpha Weekly Brief' and share the ID with me."
2. "Get the content of the document with ID '1abc-123' and summarize the key action items for me."
3. "Append a new section to my 'Q4 Strategy' document detailing the latest performance metrics retrieved from the database."

Tips & Limitations

• Safety First: Always use gws schema docs.<resource>.<method> to check parameter structures before executing requests.
• Atomicity: The batchUpdate method is atomic. If a single request within the batch fails, the entire operation is rolled back. Use this to ensure your documents do not end up in a corrupted state.
• API Limits: Be mindful of Google API rate limits. For large-scale updates, consider batching requests to optimize performance.
• Read-Only Mode: If you are only retrieving information, prefer the get method to minimize the risk of accidental document alteration.