Skip to main content
Agent skill

Googledocs Automation

Automate Google Docs tasks via Rube MCP (Composio): create, edit, search, export, copy, and update documents. Always search tools first for current schemas.

Get started

Get the complete skill folder, including its scripts and reference files.

This workflow depends on an external MCP integration. Check the source for the server, account access and setup it requires.

When to use this skill

Use Googledocs Automation when an AI agent needs a reusable SKILL.md workflow for this job: Automate Google Docs tasks via Rube MCP (Composio): create, edit, search, export, copy, and update documents. Always search tools first for current schemas.

When not to use it

Skip Googledocs Automation when the task is outside the productivity category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.

How to install

Where will you use it?

Install scope
Claude Code folder setup
mkdir -p ~/.claude/skills/googledocs-automation
# Save SKILL.md to ~/.claude/skills/googledocs-automation/SKILL.md
  1. Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/googledocs-automation/SKILL.md. For a shared project, commit the folder at .claude/skills/googledocs-automation/ instead.
  2. Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
  3. For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.

Full install guide for Claude, Cursor, and Codex →

Try a starter prompt

After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.

Starter prompt
Use the Googledocs Automation skill for this task: Use Googledocs Automation when this documented workflow matches the task. Confirm any required inputs or files before making changes.

What supports this recommendation?

72/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.

Documentation
77/100
Practical detail
68/100
Source evidence
63/100
Source signals
80/100
Model compatibility evidence
  • claudeinferred

    The skill text mentions Claude or a closely associated term. This is keyword-derived compatibility; no hands-on model test is recorded.

  • chatgptuntested

    No model-specific signal or recorded compatibility test was found.

  • geminiuntested

    No model-specific signal or recorded compatibility test was found.

  • copilotuntested

    No model-specific signal or recorded compatibility test was found.

  • llamauntested

    No model-specific signal or recorded compatibility test was found.

  • perplexityuntested

    No model-specific signal or recorded compatibility test was found.

  • mistraluntested

    No model-specific signal or recorded compatibility test was found.

  • grokuntested

    No model-specific signal or recorded compatibility test was found.

Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.

What this skill does

# Google Docs Automation via Rube MCP

Create, edit, search, export, and manage Google Docs documents programmatically using Rube MCP (Composio).

**Toolkit docs**: [composio.dev/toolkits/googledocs](https://composio.dev/toolkits/googledocs)

## Prerequisites - Rube MCP must be connected (RUBE_SEARCH_TOOLS available) - Active connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `googledocs` - Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas

## Setup **Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.

1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds 2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `googledocs` 3. If connection is not ACTIVE, follow the returned auth link to complete setup 4. Confirm connection status shows ACTIVE before running any workflows

## Core Workflows

### 1. Create a New Document Use `GOOGLEDOCS_CREATE_DOCUMENT` to create a new Google Doc with a title and initial text content. ``` Tool: GOOGLEDOCS_CREATE_DOCUMENT Parameters: - title (required): Document filename/title - text (required): Initial text content to insert into the document ```

### 2. Search for Documents Use `GOOGLEDOCS_SEARCH_DOCUMENTS` to find Google Docs by name, content, date, or sharing status. ``` Tool: GOOGLEDOCS_SEARCH_DOCUMENTS Parameters: - query: Search query string - max_results: Limit number of results - modified_after / created_after: Filter by date - shared_with_me: Filter shared documents - starred_only: Filter starred documents - include_shared_drives: Search shared drives - order_by: Sort results - page_token: Pagination token ```

### 3. Update Document Content with Markdown Use `GOOGLEDOCS_UPDATE_DOCUMENT_MARKDOWN` to replace the entire content of a document with Markdown-formatted text. ``` Tool: GOOGLEDOCS_UPDATE_DOCUMENT_MARKDOWN Parameters: - id (required): Document ID - markdown (required): Markdown content to replace entire document body ```

### 4. Find and Replace Text Use `GOOGLEDOCS_REPLACE_ALL_TEXT` to replace all occurrences of a string in a document. ``` Tool: GOOGLEDOCS_REPLACE_ALL_TEXT Parameters: - document_id (required): Target document ID - find_text (required): Text to search for - replace_text (required): Replacement text - match_case: Case-sensitive matching (boolean) - search_by_regex: Use regex for find_text - tab_ids: Specific tabs to search ```

### 5. Export Document as PDF Use `GOOGLEDOCS_EXPORT_DOCUMENT_AS_PDF` to export a Google Doc to PDF format. ``` Tool: GOOGLEDOCS_EXPORT_DOCUMENT_AS_PDF Parameters: - file_id (required): Document file ID - filename: Output PDF filename ```

### 6. Copy a Document Use `GOOGLEDOCS_COPY_DOCUMENT` to duplicate an existing Google Doc. ``` Tool: GOOGLEDOCS_COPY_DOCUMENT Parameters: - document_id (required): Source document ID to copy - title: Title for the new copy - include_shared_drives: Search shared drives for the source ```

## Common Patterns

- **Search then edit**: Use `GOOGLEDOCS_SEARCH_DOCUMENTS` to find a document by name, then use the returned document ID with `GOOGLEDOCS_UPDATE_DOCUMENT_MARKDOWN` or `GOOGLEDOCS_REPLACE_ALL_TEXT` to modify it. - **Create from template**: Use `GOOGLEDOCS_COPY_DOCUMENT` to duplicate a template, then `GOOGLEDOCS_REPLACE_ALL_TEXT` to fill in placeholder text. - **Retrieve then update**: Use `GOOGLEDOCS_GET_DOCUMENT_BY_ID` to read current content, then apply edits with `GOOGLEDOCS_UPDATE_EXISTING_DOCUMENT`. - **Batch text insertion**: Use `GOOGLEDOCS_INSERT_TEXT_ACTION` to insert text at specific positions (by index) or append to the end of a document. - **Share documents**: Combine with `GOOGLEDRIVE_ADD_FILE_SHARING_PREFERENCE` (googledrive toolkit) to share documents after creation.

## Known Pitfalls

- `GOOGLEDOCS_UPDATE_DOCUMENT_MARKDOWN` replaces the **entire** document content -- it does not append. Use it for full rewrites only. - `GOOGLEDOCS_INSERT_TEXT_ACTION` requires a precise `insertion_index` (character position). Set `append_to_end: true` to safely add text at the end. - `GOOGLEDOCS_UPDATE_EXISTING_DOCUMENT` requires constructing an `editDocs` request body with raw Google Docs API batch update requests -- consult the API documentation for the correct structure. - Document IDs and file IDs are the same value for Google Docs, but parameter names differ across tools (`id`, `document_id`, `file_id`). - `GOOGLEDOCS_SEARCH_DOCUMENTS` uses Google Drive search syntax for the `query` parameter (e.g., `name contains 'report'`).

## Quick Reference | Action | Tool | Key Parameters | |--------|------|----------------| | Create document | `GOOGLEDOCS_CREATE_DOCUMENT` | `title`, `text` | | Search documents | `GOOGLEDOCS_SEARCH_DOCUMENTS` | `query`, `max_results`, `modified_after` | | Get document by ID | `GOOGLEDOCS_GET_DOCUMENT_BY_ID` | `id` | | Update with Markdown | `GOOGLEDOCS_UPDATE_DOCUMENT_MARKDOWN` | `id`, `markdown` | | Programmatic edits | `GOOGLEDOCS_UPDATE_EXISTING_DOCUMENT` | `document_id`, `editDocs` | | Insert text | `GOOGLEDOCS_INSERT_TEXT_ACTION` | `document_id`, `text_to_insert`, `insertion_index` | | Find and replace | `GOOGLEDOCS_REPLACE_ALL_TEXT` | `document_id`, `find_text`, `replace_text` | | Export as PDF | `GOOGLEDOCS_EXPORT_DOCUMENT_AS_PDF` | `file_id`, `filename` | | Copy document | `GOOGLEDOCS_COPY_DOCUMENT` | `document_id`, `title` |

--- *Powered by [Composio](https://composio.dev)*

Intended uses

  • Use Googledocs Automation when this documented workflow matches the task.

Implementation notes

  • Review the source instructions and adapt inputs before running the workflow.

Try it, then tell us how it went

A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.