Name: google-docs
Rating: 55.2 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

google-docs

Google Docs integration. Manage Documents. Use when the user wants to interact with Google Docs data.

Quality

62%

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

Fix and improve this skill with Tessl

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

Quality

Content

67%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 delivers concrete, executable Membrane commands with a well-sequenced, checkpoint-driven connection workflow, but it opens with unnecessary background on Google Docs and inlines all content rather than splitting the larger reference material into separate files.

Suggestions

Remove or trim the introductory paragraph explaining what Google Docs is, since Claude already knows this.

Add a verification/validation checkpoint before destructive or batch document operations (e.g. get-document to confirm state before delete-content or batch-update-document).

Consider moving the full proxy flag table and clientAction field breakdown into a reference file to keep SKILL.md a lean overview.

Dimension	Reasoning	Score
Conciseness	Most content is efficient executable commands, but the opening paragraph explaining what Google Docs is ('web-based word processor... collaborative writing, document sharing, real-time editing') pads concepts Claude already knows, matching the score-3 anchor.	3 / 5
Actionability	Concrete, copy-paste-ready commands (npm install, membrane login, connection ensure, action list/run, request) plus parameterized examples and flag tables give mostly executable guidance with only minor substitution gaps.	4 / 5
Workflow Clarity	The connection workflow is clearly sequenced with explicit state checkpoints (READY, CLIENT_ACTION_REQUIRED, CONFIGURATION_ERROR) and a poll-then-retry feedback loop, leaving only minor validation gaps around the destructive/batch document actions themselves.	4 / 5
Progressive Disclosure	Content is organized into clear, well-labeled sections (Overview, Working with Google Docs, Popular actions, Best practices) with everything inline and no external references, giving good structure with minor organization gaps for a ~150-line file.	4 / 5
	Total	15 / 20 Passed

Description

57%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 correctly pairs a 'what' with an explicit 'Use when' trigger and targets a clear niche, but its capabilities are vague ('Manage Documents') and the trigger phrasing is generic rather than concrete.

Suggestions

Replace the generic 'Manage Documents' with concrete actions, e.g. 'Create, edit, read, and update Google Docs documents'.

Tighten the trigger clause with natural phrases users say, e.g. 'Use when the user wants to create or edit a Google Doc, read document content, or insert text/tables/images'.

Add common term variations (e.g. 'Google Doc', 'Docs') to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	It names the domain ('Google Docs integration') but the only action is the generic 'Manage Documents', which is minimal and non-specific like the score-2 anchor 'Processes PDF files'.	2 / 5
Completeness	Both a 'what' ('Google Docs integration. Manage Documents.') and an explicit 'when' ('Use when the user wants to interact with Google Docs data') are present, though the trigger clause is generic and could be more specific.	4 / 5
Trigger Term Quality	Relevant keywords ('Google Docs', 'Documents', 'interact with Google Docs data') are present but common variations/synonyms are missing, matching the score-3 anchor of some-but-incomplete keyword coverage.	3 / 5
Distinctiveness Conflict Risk	'Google Docs integration' is a clear niche with distinct triggers and only minor overlap risk with adjacent Google Workspace/document skills.	4 / 5
	Total	13 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

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

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/google-docs/SKILL.md
Commit: f484c82

Reviewed: 5 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.