Help us improve
Share bugs, ideas, or general feedback.
From google-workspace-cli
Use this skill when the user asks about creating, reading, or editing Google Docs via the Google Workspace CLI. Trigger on tasks involving document content, formatting, or collaboration on Google Docs.
npx claudepluginhub nsheaps/ai-mktpl --plugin google-workspace-cliHow this skill is triggered — by the user, by Claude, or both
Slash command
/google-workspace-cli:docsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use `gws docs` to create and manage Google Docs from the command line.
Automates Google Docs tasks via Rube MCP (Composio): create, edit, search, export, copy, and update documents. Always searches tools first for current schemas.
Automates Google Docs tasks like creating, searching, reading, appending, inserting, and replacing text via Python CLI scripts with standalone OAuth. For local Workspace automation without MCP server.
Operates Google Drive, Docs, Sheets, and Slides as a unified workflow surface for finding, summarizing, editing, migrating, and cleaning up shared documents without raw tool calls.
Share bugs, ideas, or general feedback.
Use gws docs to create and manage Google Docs from the command line.
# Create a new document
gws docs create --title "Meeting Notes"
# Create with initial content
gws docs create --title "Project Plan" --body "Initial project outline"
# Get document content
gws docs get <document-id>
# Get as JSON
gws docs get <document-id> --format json
# Get document metadata
gws docs get <document-id> --metadata
# Append text to a document
gws docs update <document-id> --append "New section content"
# Insert text at a specific index
gws docs update <document-id> --insert "Header text" --index 1
The Docs API supports batch updates for complex document modifications:
# Apply batch updates via JSON
gws docs batchUpdate <document-id> --requests '[
{
"insertText": {
"location": {"index": 1},
"text": "New Title\n"
}
},
{
"updateTextStyle": {
"range": {"startIndex": 1, "endIndex": 10},
"textStyle": {"bold": true},
"fields": "bold"
}
}
]'
# Export via Drive API as PDF
gws drive files export <document-id> --mime-type "application/pdf" --output ./doc.pdf
# Export as plain text
gws drive files export <document-id> --mime-type "text/plain" --output ./doc.txt
# Export as DOCX
gws drive files export <document-id> --mime-type "application/vnd.openxmlformats-officedocument.wordprocessingml.document" --output ./doc.docx
Google Docs uses a structured model with:
Use --format json to inspect document structure:
gws docs get <document-id> --format json | jq '.body.content'
docs.google.com/document/d/<DOCUMENT_ID>/editgws drive files list to find documents by namegws drive for file management (move, share, delete)