The recipe can immediately publish an unconfirmed organizational announcement as the user
Source references: 3The steps directly invoke Gmail and Chat send operations without requiring a draft preview, confirmation of the recipient and space, or validation between the two sends. The template also asserts that there are “policy changes” requiring review.
If an agent runs it unchanged or with mistaken parameters from an authenticated work account, an inaccurate policy notice could reach the wrong email address or Chat space, causing confusion, reputational harm, and organizational communication records that may be difficult to retract.
This is an execution-oriented sending recipe, not merely a warning or test: its steps direct an email to a team address and a message to a Google Chat space. The shown flow does not first present a draft, verify the real recipients/space, or request per-send confirmation. If an agent substitutes real targets and runs it, messages would be published through the user's authorized Google identity and could lead coworkers to believe policy changes exist. Sending is nevertheless the skill's stated purpose, and the source does not prove execution. A user can require draft-only output and confirmation of targets and text before sending.
1. Send email: `gws gmail +send --to team@company.com --subject 'Important Update' --body 'Please review the attached policy changes.'`2. Post in Chat: `gws chat +send --space spaces/TEAM_SPACE --text '📢 Important Update: Please check your email for policy changes.'`Show 2 other places
name: recipe-send-team-announcementdescription: "Send a team announcement via both Gmail and a Google Chat space."metadata:1. Send email: `gws gmail +send --to team@company.com --subject 'Important Update' --body 'Please review the attached policy changes.'`2. Post in Chat: `gws chat +send --space spaces/TEAM_SPACE --text '📢 Important Update: Please check your email for policy changes.'`