Send a team announcement via both Gmail and a Google Chat space.
67
60%
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/recipe-send-team-announcement/SKILL.mdQuality
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 is concise and identifies the specific platforms (Gmail and Google Chat) and the core action (sending a team announcement), which provides some clarity. However, it lacks an explicit 'Use when...' clause, covers only a single action, and misses common trigger term variations that users might naturally use.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user wants to broadcast a message to the team via email and chat simultaneously.'
Include natural trigger term variations such as 'email', 'notify team', 'broadcast', 'group message', 'Google Workspace'.
Expand the capability description to mention related actions if applicable, such as formatting the announcement, selecting recipients, or scheduling the message.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Gmail and Google Chat) and a specific action (send a team announcement), but only describes a single action rather than listing multiple concrete capabilities. | 2 / 3 |
Completeness | Describes what the skill does but has no explicit 'Use when...' clause or equivalent trigger guidance, and per the rubric a missing 'Use when' clause caps completeness at 2—but since the 'when' is entirely absent and the 'what' is also narrow, this scores at 1. | 1 / 3 |
Trigger Term Quality | Includes natural keywords like 'Gmail', 'Google Chat space', 'team announcement', but misses common variations such as 'email', 'chat message', 'broadcast', 'notify team', or 'group message'. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of Gmail and Google Chat space is somewhat distinctive, but it could overlap with general Gmail skills or general Google Chat skills since the scope of 'team announcement' is not sharply delineated. | 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 concise, well-structured recipe skill that provides clear, actionable commands for a two-step workflow. Its main weakness is the lack of any validation or error-handling guidance between the two steps (e.g., confirming the email sent before posting to Chat). Overall it's a strong simple skill.
Suggestions
Add a brief note on verifying each step succeeded before proceeding (e.g., check send confirmation or handle errors), which would improve workflow clarity for a two-service operation.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Very lean and efficient. No unnecessary explanations of what Gmail or Google Chat are. Every line serves a purpose. | 3 / 3 |
Actionability | Provides fully concrete, copy-paste ready commands with specific flags, arguments, and example values for both steps. | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced, but there's no validation or error handling—e.g., no check that the email was sent successfully before posting to Chat, and no guidance on what to do if either step fails. | 2 / 3 |
Progressive Disclosure | For a simple two-step skill under 50 lines, the structure is appropriate. It clearly references prerequisite skills for deeper details rather than inlining them. | 3 / 3 |
Total | 11 / 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.