Save Gmail messages to Google Docs for archival and reference.
Works with
Requires gws-gmail and gws-docs skills to be loaded
Workflow: search Gmail by query, retrieve message content, create a new Google Doc, and append the email body as formatted text
Supports filtering by subject, sender, and other Gmail query parameters for targeted message selection
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionrecipe-save-email-to-docExecute the skills CLI command in your project's root directory to begin installation:
Fetches recipe-save-email-to-doc from googleworkspace/cli and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate recipe-save-email-to-doc. Access via /recipe-save-email-to-doc in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
0
total installs
0
this week
23.9K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
23.9K
stars
1c:["$","div",null,{"className":"prose prose-invert max-w-none prose-headings:font-semibold prose-headings:tracking-tight prose-h1:text-4xl prose-h1:mb-2 prose-h2:text-2xl prose-h2:mb-2 prose-h3:text-lg prose-h3:mb-2 prose-p:text-muted-foreground prose-li:text-muted-foreground prose-code:bg-muted prose-code:text-foreground prose-code:px-1 prose-code:py-0.5 prose-code:rounded-sm prose-code:text-sm prose-code:before:content-none prose-code:after:content-none prose-pre:bg-muted prose-pre:text-foreground prose-pre:border prose-pre:border-border prose-pre:rounded-md [&_table]:!border-[color:var(--border)] [&_th]:!border-[color:var(--border)] [&_td]:!border-[color:var(--border)]","dangerouslySetInnerHTML":{"__html":"<p><strong>Save Gmail messages to Google Docs for archival and reference.</strong></p>\n<ul>\n<li>Requires <code>gws-gmail</code> and <code>gws-docs</code> skills to be loaded</li>\n<li>Workflow: search Gmail by query, retrieve message content, create a new Google Doc, and append the email body as formatted text</li>\n<li>Supports filtering by subject, sender, and other Gmail query parameters for targeted message selection</li>\n</ul>"}}] 22:T405,<h1>Save a Gmail Message to Google Docs</h1>
<blockquote> <p><strong>PREREQUISITE:</strong> Load the following skills to execute this recipe: <code>gws-gmail</code>, <code>gws-docs</code></p> </blockquote> <p>Save a Gmail message body into a Google Doc for archival or reference.</p> <h2>Steps</h2> <ol> <li>Find the message: <code>gws gmail users messages list --params '{"userId": "me", "q": "subject:important from:[email protected]"}' --format table</code></li> <li>Get message content: <code>gws gmail users messages get --params '{"userId": "me", "id": "MSG_ID"}'</code></li> <li>Create a doc with the content: <code>gws docs documents create --json '{"title": "Saved Email - Important Update"}'</code></li> <li>Write the email body: `gws docs +write --document-id DOC_ID --text 'From: <a href="https://github.com/googleworkspace/cli/blob/HEAD/skills/recipe-save-email-to-doc/mailto:[email protected]" target="_blank" rel="ugc nofollow noopener">[email protected]</a> Subject: Important Update</li> </ol> <p>[EMAIL BODY]'`</p>1d:["$","div",null,{"className":"prose prose-invert max-w-none prose-headings:font-semibold prose-headings:tracking-tight prose-h1:text-4xl prose-h1:mb-2 prose-h2:text-2xl prose-h2:mb-2 prose-h3:text-lg prose-h3:mb-2 prose-p:text-muted-foreground prose-li:text-muted-foreground prose-code:bg-muted prose-code:text-foreground prose-code:px-1 prose-code:py-0.5 prose-code:rounded-sm prose-code:text-sm prose-code:before:content-none prose-code:after:content-none prose-pre:bg-muted prose-pre:text-foreground prose-pre:border prose-pre:border-border prose-pre:rounded-md [&_table]:!border-[color:var(--border)] [&_th]:!border-[color:var(--border)] [&_td]:!border-[color:var(--border)]","dangerouslySetInnerHTML":{"__html":"$22"}}] 18:[["$","meta","0",{"charSet":"utf-8"}],["$","meta","1",{"name":"viewport","content":"width=device-width, initial-scale=1"}]] 16:nullPrerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
shadowcz007/skills
aaronontheweb/dotnet-skills
davila7/claude-code-templates
intellectronica/agent-skills
am-will/codex-skills
sickn33/antigravity-awesome-skills
Useful defaults in recipe-save-email-to-doc — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
recipe-save-email-to-doc reduced setup friction for our internal harness; good balance of opinion and flexibility.
recipe-save-email-to-doc has been reliable in day-to-day use. Documentation quality is above average for community skills.
Useful defaults in recipe-save-email-to-doc — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Registry listing for recipe-save-email-to-doc matched our evaluation — installs cleanly and behaves as described in the markdown.
We added recipe-save-email-to-doc from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
recipe-save-email-to-doc fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
recipe-save-email-to-doc is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
recipe-save-email-to-doc reduced setup friction for our internal harness; good balance of opinion and flexibility.
recipe-save-email-to-doc has been reliable in day-to-day use. Documentation quality is above average for community skills.
showing 1-10 of 67