gws-docs
Read and write Google Docs.
61
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
22%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is too minimal to effectively guide skill selection. While it correctly identifies the platform (Google Docs), it fails to specify concrete capabilities beyond basic read/write operations and provides no guidance on when Claude should select this skill over others.
Suggestions
Add a 'Use when...' clause with trigger terms like 'Google Docs', 'gdocs', 'Google document', or when users mention creating/editing documents in Google Drive.
Expand the capabilities list with specific actions such as 'create documents, format text, insert tables, add comments, share and collaborate'.
Include file-related triggers like '.gdoc' or context clues like 'Google Drive document' to improve distinctiveness.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only mentions 'read and write' which are very generic actions. It lacks concrete specifics like 'create documents', 'format text', 'insert tables', 'add comments', or 'collaborate on edits'. | 1 / 3 |
Completeness | The description only weakly addresses 'what' (read and write) and completely lacks any 'when' guidance. There is no 'Use when...' clause or explicit trigger guidance. | 1 / 3 |
Trigger Term Quality | 'Google Docs' is a natural keyword users would say, but the description misses common variations like 'gdocs', 'Google documents', '.gdoc', or related terms like 'word processing' or 'document editing'. | 2 / 3 |
Distinctiveness Conflict Risk | 'Google Docs' provides some specificity that distinguishes it from generic document skills, but 'read and write' is so generic it could overlap with any document-handling skill. Without explicit triggers, conflict risk remains. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
87%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-crafted, concise skill that efficiently documents the Google Docs CLI interface. It excels at progressive disclosure by linking to prerequisites and helper commands, and provides actionable discovery commands. The main weakness is the lack of validation/verification guidance for batch operations, which could benefit from explicit error handling steps.
Suggestions
Add a brief note about validating batchUpdate results or handling failures, since the API description mentions requests can fail validation
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean content that assumes Claude's competence. No unnecessary explanations of what Google Docs is or how APIs work. Every line serves a purpose. | 3 / 3 |
Actionability | Provides concrete, executable bash commands with clear syntax. The discovery workflow (--help, gws schema) gives specific commands to explore further. Links to helper commands for common operations. | 3 / 3 |
Workflow Clarity | The discovery workflow is clear (browse -> inspect -> build params), but lacks validation checkpoints for document operations. For batch updates that could fail, there's no explicit error handling or verification guidance. | 2 / 3 |
Progressive Disclosure | Excellent structure with prerequisite reference to shared skill, helper command links, and clear sections. One-level-deep references are well-signaled. Content is appropriately split between this skill and related files. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
72%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 8 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
metadata_field | 'metadata' should map string keys to string values | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 8 / 11 Passed | |
- 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.