The “draft” workflow actually sends the full document, risking unconfirmed disclosure
Source references: 2The title says “Draft a Gmail Message,” but the execution step invokes `+send`; it neither creates a draft nor requires the user to verify the recipient, body, or approve transmission. It also copies the document body without limiting what may be disclosed.
If the document contains confidential, personal, or internal information, this step immediately transmits it to the specified recipient. A wrong address, an unchanged example address, or a user expecting only a preview could result in an email that cannot be recalled.
The source supports this risk. The skill describes the task as “Draft,” but its actual workflow retrieves a Google Doc, copies its body, and invokes Gmail `+send` to a recipient; the shown steps neither create a draft nor require pre-send confirmation. If an agent has the required Docs and Gmail access and runs the recipe, document content could be sent before the user verifies the recipient, subject, or disclosure scope. A user can ask the author to create a Gmail draft and require explicit review of recipient, subject, and body before sending, or restrict Gmail permission to draft creation only.
# Draft a Gmail Message from a Google Doc> **PREREQUISITE:** Load the following skills to execute this recipe: `gws-docs`, `gws-gmail`Read content from a Google Doc and use it as the body of a Gmail message.Show 1 other places
1. Get the document content: `gws docs documents get --params '{"documentId": "DOC_ID"}'`2. Copy the text from the body content3. Send the email: `gws gmail +send --to recipient@example.com --subject 'Newsletter Update' --body 'CONTENT_FROM_DOC'`