recipe-send-team-announcement
Send a team announcement via both Gmail and a Google Chat space.
Install with Tessl CLI
npx tessl i github:googleworkspace/cli --skill recipe-send-team-announcement72
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/skillEvaluation — 100%
↑ 3.03xAgent success when using this skill
Validation 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 integration (Gmail + Google Chat) but is too brief and lacks explicit trigger guidance. It fails to explain when Claude should choose this skill over other email or messaging skills, and doesn't cover the full range of user language that might indicate this skill is needed.
Suggestions
Add a 'Use when...' clause with trigger terms like 'announce to team', 'send to everyone', 'broadcast message', 'notify via email and chat'
Include common variations of keywords: 'email', 'chat message', 'Google Workspace', 'team notification'
Expand capabilities if applicable (e.g., 'format announcements, schedule sends, target specific channels')
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (team announcements) and specific actions (send via Gmail and Google Chat space), but only describes one action rather than multiple concrete 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 'Gmail', 'Google Chat space', 'team announcement', but missing common variations like 'email', 'chat message', 'notify team', 'broadcast', or 'group message'. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of Gmail AND Google Chat space is somewhat distinctive, but 'team announcement' is generic and could overlap with other notification or messaging skills. | 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-crafted, concise skill that provides clear, actionable commands for a simple two-step workflow. The main weakness is the lack of validation or error handling guidance between steps - if the email fails, should the Chat message still be sent? For a workflow involving two separate services, some error handling guidance would strengthen it.
Suggestions
Add brief error handling guidance: what to do if email send fails before posting to Chat
Consider adding a verification step or success confirmation pattern after each command
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. No unnecessary explanations, assumes Claude knows what Gmail and Chat are, every line serves a purpose. | 3 / 3 |
Actionability | Provides fully executable, copy-paste ready commands with specific flags and example values. Clear CLI syntax that can be directly used. | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced, but lacks validation checkpoints. No guidance on what to do if email fails before posting to Chat, or how to verify successful delivery. | 2 / 3 |
Progressive Disclosure | Appropriately simple skill with clear prerequisite reference to detailed skills. No need for external files given the straightforward two-step process. | 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.