google-docs-automation

Lightweight Google Docs integration with standalone OAuth authentication. No MCP server required.

Quality

54%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/google-docs-automation/SKILL.md

The canonical home for this skill is google-docs in sanjay3290/ai-skills

Quality

Content

72%Scale 1-5

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

This is a well-structured, highly actionable CLI reference skill with concrete, copy-paste ready examples for all operations. Its main weaknesses are the lack of validation/verification steps after document modifications (read-back confirmation, error handling guidance) and some minor verbosity in informational sections that don't contribute to actionability.

Suggestions

Add a verification step after modification commands (e.g., 'After replace-text, verify with get-text to confirm changes were applied correctly')

Add error handling guidance — what happens if auth expires mid-operation, if a document ID is invalid, or if replace-text finds no matches

Trim or remove the Token Management section — the storage mechanism details aren't actionable for Claude and consume tokens without adding value

Dimension	Reasoning	Score
Conciseness	Generally efficient with minimal unnecessary explanation. The 'Document ID Format' section is slightly over-explained (Claude would understand URL vs ID extraction), and the 'Token Management' section explains system keyring details that aren't actionable. But overall it's lean.	4 / 5
Actionability	Every command is copy-paste ready with concrete examples including realistic document IDs and URLs. The full CLI interface is demonstrated with clear flags and arguments covering all common operations.	5 / 5
Workflow Clarity	The setup flow (auth → commands) is clear, and individual commands are well-documented. However, there's no validation or verification guidance — e.g., after replace-text, no suggestion to verify the change with get-text. For document modification operations, missing feedback loops cap this at 3.	3 / 5
Progressive Disclosure	The content is reasonably structured with clear sections, but no bundle files are provided despite references to scripts/auth.py and scripts/docs.py. For a skill of this size (~60 lines), the structure is adequate but the Token Management and Document ID sections could be separated or trimmed. No external references are provided for deeper details.	3 / 5
	Total	15 / 20 Passed

Description

36%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 identifies the domain (Google Docs) and highlights an architectural distinction (standalone OAuth, no MCP), but fails to describe any concrete capabilities or provide trigger guidance for when Claude should select this skill. It reads more like a technical implementation note than a functional skill description.

Suggestions

Add concrete actions the skill performs, e.g., 'Creates, reads, edits, and shares Google Docs documents'.

Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to create, edit, or read Google Docs, or mentions gdocs, Google documents, or Google Drive documents'.

Replace the architecture-focused language ('Lightweight', 'No MCP server required') with user-facing capability descriptions that help Claude understand what tasks this skill can accomplish.

Dimension	Reasoning	Score
Specificity	Names the domain (Google Docs) and mentions OAuth authentication, but describes no concrete actions like creating, editing, reading, or sharing documents. 'Integration' is vague.	2 / 5
Completeness	The 'what' is vague ('integration' with no specific actions), and there is no 'when' clause or trigger guidance at all. The description focuses more on architecture (no MCP server, standalone OAuth) than on what the skill does or when to use it.	2 / 5
Trigger Term Quality	'Google Docs' is a strong natural keyword users would say, and 'OAuth' is relevant for technical users. However, it misses common user phrases like 'document editing', 'Google Drive', 'gdocs', or action-oriented terms like 'create doc', 'share document'.	3 / 5
Distinctiveness Conflict Risk	'Google Docs' provides some specificity, and 'no MCP server required' differentiates it from MCP-based alternatives. However, 'integration' is broad enough that it could overlap with other Google Workspace or document-related skills.	3 / 5
	Total	10 / 20 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: skills/google-docs-automation/SKILL.md
Commit: 57c135b

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.