Google Docs Review Skill
Use this Skill to review Google Docs and add anchored comments directly in the document using MCP browser automation.
Prerequisites
- •Google Doc must be open in a Chrome tab
- •Claude in Chrome MCP browser tools must be available
Workflow
Step 1: Get Document Context
- •Use
mcp__claude-in-chrome__tabs_context_mcpto get available tabs - •Look for a Google Doc tab (URL contains
docs.google.com/document/) - •If user named a specific document:
- •Check if that doc is already open (match by title in tab or page)
- •If NOT open, open it:
a. Create new tab:
mcp__claude-in-chrome__tabs_create_mcpb. Navigate to Google Drive search:mcp__claude-in-chrome__navigateurl="https://drive.google.com/drive/search?q=[doc name]" c. Wait for results to load, take screenshot d. Find and click the matching document to open it e. Wait for doc to load, take screenshot to confirm
- •If no doc specified and no Google Doc tab found:
- •Ask user which document to review
- •Take a screenshot to see the current document state
- •Determine review scope:
- •If user specified criteria, use those
- •If user did NOT specify criteria, review for ALL of the following:
- •Spelling/grammar errors
- •Factual accuracy
- •Clarity and readability
- •Technical accuracy
- •Structure and organization
- •Potential edits (wording improvements, conciseness)
- •Rhetorical effectiveness (argument strength, persuasiveness, flow)
Step 2: Read Document Content
Use one of these approaches to get the document text:
- •Scroll and screenshot - Take multiple screenshots while scrolling to read all content visually
- •Select all and copy - Ctrl+A, then read the selection
Step 3: Analyze and Identify Issues
Based on the user's requested review type, identify specific issues to comment on. For each issue, note:
- •The exact text or phrase to find (for anchoring the comment)
- •The comment to add (description of issue + suggestion)
Step 4: Add Comments (for each issue)
Use MCP automation to add anchored comments:
- •Open Find:
mcp__claude-in-chrome__computeraction="key" text="ctrl+f" - •Type search text:
mcp__claude-in-chrome__computeraction="type" text="[phrase to find]" - •Find it:
mcp__claude-in-chrome__computeraction="key" text="Return" - •Take screenshot to see where it is
- •Close Find:
mcp__claude-in-chrome__computeraction="key" text="Escape" - •Triple-click to select paragraph:
mcp__claude-in-chrome__computeraction="triple_click" coordinate=[x,y] - •Find Add Comment button:
mcp__claude-in-chrome__findquery="Add comment button" - •Click it:
mcp__claude-in-chrome__computeraction="left_click" ref="ref_xxx" - •Type comment:
mcp__claude-in-chrome__computeraction="type" text="[comment text]" - •Find submit button:
mcp__claude-in-chrome__findquery="Comment submit button" - •Submit:
mcp__claude-in-chrome__computeraction="left_click" ref="ref_xxx"
Step 5: Report Results
After processing all issues, report:
- •Total issues found
- •Comments successfully added
- •Any issues that couldn't be commented (e.g., text not found)
Usage Triggers
Claude will automatically use this Skill when you ask things like:
- •"Review my Google Doc" (reviews open doc for ALL criteria)
- •"Review 'My Draft Post'" (opens doc by name if not already open)
- •"Check the Google Doc for spelling errors" (specific criterion)
- •"Add comments to the Google Doc about factual accuracy"
- •"Review this doc for clarity"
- •"Check the structure and flow"
- •"Suggest edits for this doc"
- •"Review 'Weekly Update' for rhetorical effectiveness"
- •"Comment on the open Google Doc"
Important Notes
- •Comments anchor to paragraphs, not specific words (Google Docs limitation via this method)
- •Each comment requires ~10 MCP tool calls, so large reviews take time
- •If Find can't locate exact text, try a shorter unique phrase from that paragraph
- •The Google Doc must be in a Chrome tab that's part of the MCP tab group