gws-workflow-file-announce
Google Workflow: Announce a Drive file in a Chat space.
Install with Tessl CLI
npx tessl i github:googleworkspace/cli --skill gws-workflow-file-announce65
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
32%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 task but is too terse to be effective for skill selection. It lacks explicit trigger guidance ('Use when...'), missing natural keyword variations users would say, and provides only a single action rather than comprehensive capability coverage.
Suggestions
Add a 'Use when...' clause with trigger terms like 'share Drive file to Chat', 'post file to Google Chat', 'announce document in space', or 'notify team about file'
Include natural keyword variations: 'Google Drive', 'Google Chat', 'Spaces', 'share', 'post', 'notify', '.gdoc', '.gsheet'
Expand the capability description to cover related actions if applicable, such as formatting the announcement, selecting recipients, or handling different file types
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Google Workflow) and a specific action (announce a Drive file in a Chat space), but only describes one concrete action rather than multiple capabilities. | 2 / 3 |
Completeness | Describes what the skill does but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Includes relevant keywords like 'Drive file', 'Chat space', and 'Announce', but missing common variations users might say like 'share', 'post', 'notify', 'Google Drive', 'Google Chat', or 'Spaces'. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of Drive + Chat space is somewhat specific, but 'Google Workflow' is generic and could overlap with other Google-related skills; lacks explicit file type or scenario triggers to clearly distinguish it. | 2 / 3 |
Total | 7 / 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-structured, concise skill that provides clear, actionable guidance for announcing Drive files in Chat spaces. The main weakness is the lack of explicit workflow sequencing and validation for what is described as a write operation. The skill effectively uses progressive disclosure by referencing shared documentation.
Suggestions
Add explicit workflow steps showing the upload-then-announce sequence with validation (e.g., '1. Upload file, 2. Verify upload success, 3. Announce, 4. Confirm message sent')
Include guidance on verifying the announcement was successful or handling common errors (e.g., invalid space ID, missing file permissions)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, presenting only essential information: usage, flags, examples, and tips. No unnecessary explanations of what Drive or Chat are, assumes Claude's competence. | 3 / 3 |
Actionability | Provides concrete, copy-paste ready commands with clear flag documentation. The examples show exact usage patterns with placeholder IDs that are immediately executable. | 3 / 3 |
Workflow Clarity | The tips mention using 'gws drive +upload' first, suggesting a multi-step workflow, but doesn't provide explicit sequencing or validation steps. For a write command that sends messages, there's no mention of verifying success or handling failures. | 2 / 3 |
Progressive Disclosure | Clear structure with well-signaled one-level-deep references to gws-shared and gws-workflow. Content is appropriately scoped to this specific command with navigation to related skills. | 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.