google-docs

Interact with Google Docs - create documents, search by title, read content, and edit text. Use when user asks to: create a Google Doc, find a document, read doc content, add text to a doc, or replace text in a document. Lightweight alternative to full Google Workspace MCP server with standalone OAuth authentication.

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

76%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is an efficient, highly actionable CLI reference with clear setup and usage sections. Its main weakness is workflow clarity: mutating commands (replace-text, append-text, insert-text) lack any verification step to confirm the edit succeeded.

Suggestions

Add a verification step after mutating commands — e.g. suggest re-running 'get-text <id>' to confirm a replace-text/append-text/insert-text change landed correctly.

Remove the redundant opening line that repeats the frontmatter description to tighten conciseness toward a 5.

Consider noting how to preview or undo an edit (or that operations are immediate) so the workflow for document modification is fully closed.

Dimension	Reasoning	Score
Conciseness	The body is a lean command reference with no over-explanation of concepts Claude already knows; the only padding is the opening line 'Lightweight Google Docs integration with standalone OAuth authentication. No MCP server required.' which repeats the frontmatter, so it sits above the score-3 anchor but not at fully lean 5.	4 / 5
Actionability	Provides copy-paste-ready, fully executable commands for every operation (e.g. 'python scripts/docs.py create "Meeting Notes"', 'python scripts/docs.py replace-text <id> "old text" "new text"'), covering the common cases with concrete arguments.	5 / 5
Workflow Clarity	The First-Time Setup flow (login/status/logout) and command catalog are sequenced, but document-editing operations like replace-text and append-text have no validation or verify-after-edit checkpoint; per the rubric cap for document-manipulation operations without validation, this cannot exceed 3.	3 / 5
Progressive Disclosure	Content is well-organized into First-Time Setup, Commands, Document ID Format, and Token Management sections with real, one-level-deep script references (scripts/auth.py, scripts/docs.py) and no nested references; minor gaps keep it just below the ideal 5.	4 / 5
	Total	16 / 20 Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is exemplary: it states concrete capabilities, pairs them with natural trigger phrases, explicitly covers both what and when, and distinguishes itself from the broader Google Workspace MCP. No changes needed.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'create documents, search by title, read content, and edit text' — covering the skill's scope comprehensively, matching the score-5 anchor rather than the minor-gaps anchor at 4.	5 / 5
Completeness	Explicitly answers both 'what' ('Interact with Google Docs - create documents, search by title, read content, and edit text') and 'when' (the 'Use when user asks to:' clause with concrete triggers), satisfying the score-5 anchor.	5 / 5
Trigger Term Quality	The 'Use when user asks to: create a Google Doc, find a document, read doc content, add text to a doc, or replace text in a document' clause gives natural phrasings a user would actually say, with synonyms (find/search, doc/document), matching comprehensive coverage.	5 / 5
Distinctiveness Conflict Risk	'Lightweight alternative to full Google Workspace MCP server with standalone OAuth authentication' carves a clear niche scoped to Google Docs with distinct triggers, minimizing conflict with adjacent skills.	5 / 5
	Total	20 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: sanjay3290/ai-skills
Path: skills/google-docs/SKILL.md
Commit: 281d88d

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.