recipe-draft-email-from-doc

Read content from a Google Doc and use it as the body of a Gmail message.

31,509
installs: 0 up / 0 down, score 0.00
votes
In the catalog since: 30 Sept 2026
From: googleworkspace/cli

Get it through your agent

Skill instructions

Rendered from the published SKILL.md, 13 lines.

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.

Steps

Get the document content: gws docs documents get --params '{"documentId": "DOC_ID"}'
Copy the text from the body content
Send the email: gws gmail +send --to recipient@example.com --subject 'Newsletter Update' --body 'CONTENT_FROM_DOC'

Get it through your agent

Call the Graph-of-Skills MCP server's retrieve_skill_bundle tool and it returns this skill's text inside your budget.

{
  "tool": "retrieve_skill_bundle",
  "arguments": {
    "query": "recipe-draft-email-from-doc"
  }
}

New to this? Set up Graph-of-Skills or get a free key. The text on this page comes from its authors: how skills are sourced and what we check. If none fits your task, your agent can write a skill for your own library. To keep a skill from your own library on a machine, see how to install one of your skills.

Share on X Share on LinkedIn Share on Bluesky Share on Hacker News

Share on Reddit

Source

Listing on skills.sh

From googleworkspace/cli via skills.sh

Related skills

recipe-save-email-to-doc
Save a Gmail message body into a Google Doc for archival or reference.
30,315 installs
gws-gmail-read
Gmail: Read a message and extract its body or headers.
40,974 installs
connector-googlemail
MANDATORY recipe for every Caffeine build that sends email through the user's own Gmail account. The ONLY supported path is the `googlemail-client` mops package (Gmail REST API) combined with the `google-oauth` mops package (token exchange + refresh + PKCE). Hand-rolling `ic.http_request` calls to `oauth2.googleapis.com` or `gmail.googleapis.com` is a FORBIDDEN anti-pattern — it bypasses bearer auth, replication-cost safeguards, and the `google-oauth` library's percent-encoding and JSON parsing. Load this skill whenever the user, spec, or any prior task mentions sending email, Gmail, "notify via email", "forward results by email", or any equivalent phrasing — and BEFORE writing any code that touches a Google endpoint.
24,504 installs
readout
Produce a polished, self-contained HTML "readout" document under ~/.readouts (with an auto-maintained index page), either by snapshotting the findings accumulated in the current conversation or — when invoked fresh, e.g. "/readout on how github webhook events are processed" — by sharpening scope with clarifying questions and researching the codebase before documenting. The work runs in a child agent so the main conversation's context stays clean. Use whenever the user invokes /readout, says "write this up", "turn this into a doc/page", "make a readout", or asks for a readable, shareable document capturing findings or explaining how something works.
17,461 installs
google-cloud-recipe-onboarding
Guides a developer's first steps on Google Cloud, covering account creation, billing setup, project management, and deploying a first resource. Use when a new developer wants to initialize their first Google Cloud project, configure billing, and verify deployment. Don't use for enterprise organization setup (use Google Cloud Setup guided flow for that instead). Don't use for complex multi-project architectures.
15,377 installs