gws-docs-write
Google Docs: Append text to a document.
72
66%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/gws-docs-write/SKILL.mdQuality
Discovery
32%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 very terse—it identifies the platform and a single action but lacks trigger guidance, user-facing keywords, and breadth of capability description. It would benefit significantly from a 'Use when...' clause and additional natural language trigger terms to help Claude select it appropriately.
Suggestions
Add a 'Use when...' clause with trigger terms like 'add text to Google Doc', 'append content', 'write to a Google document', 'update doc with text'.
Include common keyword variations users might say, such as 'add', 'insert', 'write', 'Google document', '.gdoc'.
Expand the capability description to clarify scope—e.g., whether it supports appending paragraphs, formatted text, or only plain text—to reduce overlap with other Google Docs skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Google Docs) and one specific action (append text to a document), but only describes a single capability rather than listing multiple concrete actions. | 2 / 3 |
Completeness | Describes what it does (append text to a Google Doc) but has no 'Use when...' clause or equivalent explicit trigger guidance, which per the rubric caps completeness at 2, and the 'what' is also minimal—so this scores at 1. | 1 / 3 |
Trigger Term Quality | Includes 'Google Docs' and 'append text' which are relevant keywords, but misses common variations users might say like 'add text', 'write to doc', 'insert content', or 'Google document'. | 2 / 3 |
Distinctiveness Conflict Risk | Specifying 'Google Docs' and 'append text' provides some distinctiveness, but could overlap with other Google Docs skills (editing, formatting, inserting) since the scope is narrowly but vaguely defined. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an excellent, concise skill that does exactly what it needs to do. It provides clear, actionable CLI usage for a single-purpose command, includes appropriate safety warnings for write operations, and properly delegates shared concerns to referenced files. No improvements needed.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every token earns its place. No unnecessary explanations of what Google Docs is or how APIs work. The content is lean, assumes Claude's competence, and focuses only on what's needed to use the command. | 3 / 3 |
Actionability | Provides exact CLI syntax, a complete flag table with required/default info, and a concrete copy-paste-ready example. The tip about rich formatting points to the alternative approach without over-explaining. | 3 / 3 |
Workflow Clarity | This is a simple single-command skill, and the single action is unambiguous. It includes a clear caution about confirming with the user before executing a write operation, which serves as a validation checkpoint for this destructive action. | 3 / 3 |
Progressive Disclosure | Clean overview with well-signaled one-level-deep references to shared auth/flags skill and the parent docs skill. The prerequisite callout at the top clearly directs to shared configuration without inlining it. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
90%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 |
|---|---|---|
metadata_field | 'metadata' should map string keys to string values | Warning |
Total | 10 / 11 Passed | |
- Repository
- googleworkspace/cli
- Commit
c7c6646
- Reviewed
Table of Contents
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.