tdg-personal/google-workspace-ops
Operate across Google Drive, Docs, Sheets, and Slides as one workflow surface for plans, trackers, decks, and shared documents. Use when the user needs to find, summarize, edit, migrate, or clean up Google Workspace assets without dropping to raw tool calls.
70
70%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
Discovery
92%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 is a strong description that clearly communicates both capabilities and trigger conditions across the Google Workspace suite. It uses natural language with good trigger terms and an explicit 'Use when' clause. The main weakness is its broad scope covering four products, which could create overlap with more specialized Google Workspace skills if they exist.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple concrete actions ('find, summarize, edit, migrate, clean up') across specific Google Workspace products (Drive, Docs, Sheets, Slides) and names concrete artifact types ('plans, trackers, decks, shared documents'). | 3 / 3 |
Completeness | Clearly answers both 'what' (operate across Google Drive/Docs/Sheets/Slides for plans, trackers, decks, shared documents) and 'when' (explicit 'Use when' clause specifying find, summarize, edit, migrate, or clean up Google Workspace assets). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Google Drive', 'Docs', 'Sheets', 'Slides', 'Google Workspace', 'find', 'summarize', 'edit', 'migrate', 'clean up', 'plans', 'trackers', 'decks', 'shared documents'. These cover a good range of natural user language. | 3 / 3 |
Distinctiveness Conflict Risk | While it targets Google Workspace specifically, the breadth of covering four products (Drive, Docs, Sheets, Slides) and generic actions like 'edit' and 'find' could overlap with individual product-specific skills. The phrase 'without dropping to raw tool calls' adds some distinction but the scope is quite broad. | 2 / 3 |
Total | 11 / 12 Passed |
Implementation
35%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a reasonable high-level workflow framework for Google Workspace operations but lacks the concrete, actionable guidance needed to be truly useful. The instructions describe what to do conceptually but never show how—there are no API calls, tool invocations, or executable examples. The workflow structure is decent but missing post-edit verification steps.
Suggestions
Add concrete, executable examples for each tool surface (e.g., specific Drive search queries, Docs edit operations with index parameters, Sheets range operations with actual cell references)
Include explicit verification steps after edits—e.g., re-inspect the document after changes to confirm structure matches expectations before reporting success
Replace vague directives like 'use index-aware edits' and 'operate on explicit tabs and ranges' with actual tool call examples or at minimum specific parameter patterns
Consider splitting tool-specific guidance (Docs editing patterns, Sheets range operations, Slides migration steps) into referenced sub-files to keep the overview lean while providing depth
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably efficient but includes some unnecessary elaboration. Phrases like 'not just editing one file in isolation' and the 'Good Use Cases' section add modest value but could be trimmed. The workflow steps are somewhat verbose for what amounts to general guidance. | 2 / 3 |
Actionability | The skill provides no concrete code, commands, API calls, or executable examples. Instructions like 'use index-aware edits' and 'operate on explicit tabs and ranges' are vague directives without showing how to actually do them. There are no tool-specific invocations, function signatures, or copy-paste ready snippets. | 1 / 3 |
Workflow Clarity | The four-step workflow (Find → Inspect → Edit → Clean) provides a clear sequence, and the 'Inspect before editing' step is a good validation checkpoint. However, there are no explicit verification steps after edits are made, no error recovery/feedback loops, and no validation that edits succeeded before proceeding. | 2 / 3 |
Progressive Disclosure | The content is well-structured with clear sections and headers, but everything is inline in a single file. For a skill covering four different Google Workspace tools, there's no reference to separate detailed guides for Docs, Sheets, or Slides operations. The output format template is appropriately inline, but tool-specific guidance could benefit from separate references. | 2 / 3 |
Total | 7 / 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 |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
Reviewed
Table of Contents