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 and keyword variations to improve discoverability.
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 Drive link to Chat.'
Include natural keyword variations like 'Google Drive', 'Google Chat', 'share file', 'post link', 'notify team', 'send to space' to improve trigger term coverage.
Expand the capability description slightly to mention related actions, e.g., 'Announces a Google Drive file in a Google Chat space by posting a formatted message with the file link and optional description.'
| 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 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 skill that clearly documents flags and usage for a single-purpose workflow command. Its main weaknesses are the lack of expected output examples and missing validation/error-handling guidance for what is explicitly noted as a write operation. The content would benefit from showing what success and failure look like.
Suggestions
Add an example of expected output (success and error cases) so Claude knows what to expect and how to handle failures.
Add a brief validation step or feedback loop, e.g., 'Verify the message was posted by checking the response status or using gws chat +list-messages'.
| 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 values (FILE_ID, spaces/ABC123) without showing expected output. There's no indication of what the actual workflow does under the hood (API calls, message format) or what success/failure looks like. | 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. Since this is a write command that sends a Chat message, there's no verification step (e.g., confirming the message was sent, checking for errors). Missing feedback loops for a write operation caps this at 2. | 2 / 3 |
Progressive Disclosure | Clear, well-organized structure with appropriate references to gws-shared and gws-workflow skills. The prerequisite callout is well-signaled, and the See Also section provides one-level-deep navigation to related skills. | 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 | |
a3768d0
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.