Google Workspace Skills: Official, But Mid
Official provenance is a useful signal. It is not a score. The five Google Workspace skills in the new batch average 7.00, with a range from 5.9 to 8.3.
| Skill | Trigger | Structure | Workflow | Content | Engineering | Security | Total |
|---|---|---|---|---|---|---|---|
| google-calendar | 7.0 | 8.5 | 8.0 | 9.0 | 8.0 | 9.5 | 8.3 |
| google-docs | 7.0 | 8.0 | 7.5 | 6.5 | 8.0 | 9.5 | 7.8 |
| google-sheets | 5.5 | 7.0 | 4.5 | 7.5 | 7.0 | 9.5 | 6.6 |
| gmail | 5.5 | 7.0 | 3.0 | 8.5 | 7.5 | 9.5 | 6.4 |
| google-slides | 5.5 | 6.5 | 2.5 | 6.5 | 7.5 | 9.0 | 5.9 |
The pattern is consistent: structure and security are high, workflow and trigger are weak. These are official connectors, so the API knowledge is reliable. The weakness is in turning that knowledge into a task procedure.
Calendar is the exception
google-calendar scores 8.3 because it treats calendar operations as tasks: find availability, create an event, handle conflicts, confirm the result. It asks for the information it needs and checks what it wrote.
Slides is the clearest gap
google-slides scores 5.9 with a workflow score of 2.5. It describes the Slides API and leaves the deck-building procedure implicit. For a task that is fundamentally about structure — title, sections, speaker notes, visual hierarchy — the file does not encode the structure.
The lesson
Official integrations are a good starting point because they get the API details right. They are not automatically good skills. The same five-part workflow test applies: preconditions, order, inputs and outputs, verification, and failure handling.
The spreadsheet-specific version of this gap is covered in the next post.