Google Workflow: Announce a Drive file in a Chat space.
64
56%
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-workflow-file-announce/SKILL.mdQuality
Discovery
40%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 identifies a specific Google integration workflow but is too terse to be highly effective for skill selection. It lacks a 'Use when...' clause, which is critical for Claude to know when to select this skill, and could benefit from additional trigger terms covering common user phrasings.
Suggestions
Add a 'Use when...' clause such as 'Use when the user wants to share or announce a Google Drive file in a Google Chat space, or mentions posting a file link to a chat room.'
Include natural trigger term variations like 'Google Drive', 'Google Chat', 'share file', 'post link', 'notify team', 'send to space' to improve matching against diverse user requests.
Expand the 'what' portion slightly to clarify the workflow steps, e.g., 'Retrieves a Google Drive file and posts an announcement with a link to a specified Google Chat space.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names a specific domain (Google Workflow) and a concrete action (announce a Drive file in a Chat space), but it only describes a single action rather than listing multiple specific capabilities. | 2 / 3 |
Completeness | The description answers 'what' (announce a Drive file in a Chat space) but completely lacks a 'Use when...' clause or any explicit trigger guidance, which per the rubric should cap completeness at 2, and since the 'when' is entirely missing, it scores a 1. | 1 / 3 |
Trigger Term Quality | Includes relevant keywords like 'Drive file', 'Chat space', and 'announce', which are natural terms users might say. However, it misses common variations like 'Google Drive', 'Google Chat', 'share file', 'post file link', 'notify', or 'send to channel'. | 2 / 3 |
Distinctiveness Conflict Risk | The description is quite specific to a narrow workflow involving Google Drive and Google Chat, making it clearly distinguishable from other skills and unlikely to conflict with unrelated skills. | 3 / 3 |
Total | 8 / 12 Passed |
Implementation
72%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-structured, concise CLI reference skill for a single-purpose workflow command. Its main weakness is the lack of explicit workflow sequencing with validation steps (e.g., verify file exists before announcing, confirm message delivery) and the absence of expected output examples. The progressive disclosure and conciseness are strong.
Suggestions
Add an explicit multi-step workflow sequence: 1) verify file exists with Drive API, 2) send announcement, 3) confirm message was posted — especially since this is a write/destructive operation.
Include an example of expected output (e.g., the JSON response after a successful announcement) so Claude knows what success looks like.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. Every section serves a purpose — flags table, examples, tips — with no unnecessary explanation of what Drive or Chat spaces are. No wasted tokens. | 3 / 3 |
Actionability | Provides concrete CLI commands and a clear flags table, but the examples use placeholder IDs without showing expected output. There's no indication of what the actual API calls or implementation look like — it's a CLI reference rather than executable guidance for building the workflow. | 2 / 3 |
Workflow Clarity | The tips mention using `gws drive +upload` first, hinting at a multi-step workflow, but there's no explicit sequenced workflow with validation checkpoints. For a write command that sends a Chat message, there's no verification step (e.g., confirming the message was sent or checking the file exists before announcing). | 2 / 3 |
Progressive Disclosure | Clear, concise overview with well-signaled one-level-deep references to gws-shared and gws-workflow. The prerequisite callout at the top is well-structured. Content is appropriately scoped for this single-purpose skill. | 3 / 3 |
Total | 10 / 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 | |
c7c6646
Table of Contents
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.