use-gmail

Read, search, send, and draft Gmail emails and Google contacts. Use when the user asks to check email, find emails, search messages, send emails, create drafts, look up contacts, or find someone's email/phone. Supports multiple accounts.

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "use-gmail" with this command: npx skills add helincao/skilled/helincao-skilled-use-gmail

Use-Gmail Skill - Email & Contacts Access

Read, search, and send Gmail emails. Access Google contacts.

Run commands with the CLI at "$SKILL_DIR/scripts/gmailcli.js" (SKILL_DIR is the directory containing this SKILL.md).

CRITICAL: Email Sending Confirmation Required

Before sending ANY email, you MUST get explicit user confirmation.

When the user asks to send an email:

  1. First, show them the complete email details:
    • From (which account)
    • To
    • CC/BCC (if any)
    • Subject
    • Full body text
  2. Ask: "Do you want me to send this email?"
  3. ONLY run the send command AFTER the user explicitly confirms (e.g., "yes", "send it", "go ahead")
  4. NEVER send an email without this confirmation, even if the user asked you to send it initially

This applies even when:

  • The user says "send an email to X"
  • You are in "dangerously skip permissions" mode
  • The user seems to be in a hurry

Always confirm first. No exceptions.

First-Time Setup (One-Time, ~2 minutes)

On first run, the script will guide you through setup. You need to create a Google Cloud OAuth client once:

  1. Go to Google Cloud Console
  2. Create a project (or select existing)
  3. Enable Gmail API and People API (APIs & Services → Library)
  4. Configure OAuth consent screen:
    • User Type: External
    • App name: Use Gmail
    • Add yourself as test user
    • Add scopes: gmail.readonly, gmail.send, gmail.modify, contacts.readonly
  5. Create OAuth client ID:
    • Application type: Desktop app
    • Copy the Client ID and Client Secret
  6. Add them to the repo root .env file:
    • GMAIL_CLIENT_ID=...
    • GMAIL_CLIENT_SECRET=...

Then run any command (from the repo root using the node command examples below) - browser opens, you approve, done. Works for all your accounts.

Note: If you previously used gmail-reader, you'll need to re-authenticate to grant the new gmail.send scope. Note: OAuth tokens and account metadata are stored in the repo root .env as base64 JSON (GMAIL_SKILL_TOKENS_B64, GMAIL_SKILL_ACCOUNTS_META_B64).

Commands

Search Emails

node "$SKILL_DIR/scripts/gmailcli.js" search "query" [--max-results N] [--account EMAIL]

Query examples:

  • from:john@example.com - from specific sender
  • subject:meeting after:2026/01/01 - subject + date
  • has:attachment filename:pdf - with PDF attachments
  • is:unread - unread emails
  • "exact phrase" - exact match

Read Email

node "$SKILL_DIR/scripts/gmailcli.js" read EMAIL_ID [--account EMAIL]

List Recent Emails

node "$SKILL_DIR/scripts/gmailcli.js" list [--max-results N] [--label LABEL] [--account EMAIL]

Send Email (Requires Confirmation)

node "$SKILL_DIR/scripts/gmailcli.js" send --to EMAIL --subject "Subject" --body "Body text" [--cc EMAIL] [--bcc EMAIL] [--account EMAIL] [--yes]

Required arguments:

  • --to / -t - Recipient email address
  • --subject / -s - Email subject line
  • --body / -b - Email body text

Optional arguments:

  • --cc - CC recipients (comma-separated)
  • --bcc - BCC recipients (comma-separated)
  • --account / -a - Send from specific account
  • --yes - Skip interactive prompt (ONLY after explicit user confirmation)

Example:

node "$SKILL_DIR/scripts/gmailcli.js" send \
  --to "recipient@example.com" \
  --subject "Meeting Tomorrow" \
  --body "Hi, just confirming our meeting at 2pm tomorrow." \
  --account work@company.com \
  --yes

Mark as Read

node "$SKILL_DIR/scripts/gmailcli.js" mark-read EMAIL_ID [--account EMAIL]

Mark as Unread

node "$SKILL_DIR/scripts/gmailcli.js" mark-unread EMAIL_ID [--account EMAIL]

Both mark-read and mark-unread support multiple IDs (comma-separated):

node "$SKILL_DIR/scripts/gmailcli.js" mark-read "id1,id2,id3" --account user@gmail.com

Mark Done (Archive)

Archives email(s) by removing from inbox. Equivalent to Gmail's 'e' keyboard shortcut.

node "$SKILL_DIR/scripts/gmailcli.js" mark-done EMAIL_ID [--account EMAIL]

Unarchive

Moves email(s) back to inbox (undo archive).

node "$SKILL_DIR/scripts/gmailcli.js" unarchive EMAIL_ID [--account EMAIL]

Star / Unstar

node "$SKILL_DIR/scripts/gmailcli.js" star EMAIL_ID [--account EMAIL]
node "$SKILL_DIR/scripts/gmailcli.js" unstar EMAIL_ID [--account EMAIL]

All label commands support multiple IDs (comma-separated):

node "$SKILL_DIR/scripts/gmailcli.js" star "id1,id2,id3" --account user@gmail.com

Create Draft

Creates a draft email. Use --reply-to-id when replying to an existing email to ensure proper threading in email clients like Superhuman.

node "$SKILL_DIR/scripts/gmailcli.js" draft --to EMAIL --subject "Subject" --body "Body text" [--reply-to-id EMAIL_ID] [--cc EMAIL] [--bcc EMAIL] [--account EMAIL]

Required arguments:

  • --to / -t - Recipient email address
  • --subject / -s - Email subject line
  • --body / -b - Email body text

Optional arguments:

  • --reply-to-id / -r - Message ID to reply to (adds proper In-Reply-To and References headers for threading)
  • --cc - CC recipients (comma-separated)
  • --bcc - BCC recipients (comma-separated)
  • --account / -a - Create draft in specific account

Example (new email):

node "$SKILL_DIR/scripts/gmailcli.js" draft \
  --to "recipient@example.com" \
  --subject "Draft for Review" \
  --body "Here's my draft message."

Example (reply to existing email):

node "$SKILL_DIR/scripts/gmailcli.js" draft \
  --to "sender@example.com" \
  --subject "Re: Original Subject" \
  --body "Thanks for your email..." \
  --reply-to-id 19b99b3127793843 \
  --account work@company.com

List Labels

node "$SKILL_DIR/scripts/gmailcli.js" labels [--account EMAIL]

List Contacts

node "$SKILL_DIR/scripts/gmailcli.js" contacts [--max-results N] [--account EMAIL]

Search Contacts

node "$SKILL_DIR/scripts/gmailcli.js" search-contacts "query" [--account EMAIL]

Manage Accounts

# List all authenticated accounts
node "$SKILL_DIR/scripts/gmailcli.js" accounts

# Remove an account
node "$SKILL_DIR/scripts/gmailcli.js" logout --account user@gmail.com

Multi-Account Support

Add accounts by using --account with a new email - browser opens for that account:

# First account (auto-authenticates)
node "$SKILL_DIR/scripts/gmailcli.js" list

# Add work account
node "$SKILL_DIR/scripts/gmailcli.js" list --account work@company.com

# Add personal account
node "$SKILL_DIR/scripts/gmailcli.js" list --account personal@gmail.com

# Use specific account
node "$SKILL_DIR/scripts/gmailcli.js" search "from:boss" --account work@company.com

Tokens and account metadata are stored in the repo root .env:

  • GMAIL_SKILL_TOKENS_B64
  • GMAIL_SKILL_ACCOUNTS_META_B64

Examples

Find unread emails from this week

node "$SKILL_DIR/scripts/gmailcli.js" search "is:unread after:2026/01/01"

Read a specific email

node "$SKILL_DIR/scripts/gmailcli.js" read 18d5a3b2c1f4e5d6

Send a quick email

node "$SKILL_DIR/scripts/gmailcli.js" send \
  --to "friend@example.com" \
  --subject "Hello!" \
  --body "Just wanted to say hi." \
  --yes

Find someone's contact info

node "$SKILL_DIR/scripts/gmailcli.js" search-contacts "John Smith"

Check work email from personal machine

node "$SKILL_DIR/scripts/gmailcli.js" list --account work@company.com --max-results 5

Output

All commands output JSON for easy parsing.

Requirements

  • Node.js 18+ (Node 20+ recommended)
  • Google OAuth Desktop App credentials in repo root .env:
    • GMAIL_CLIENT_ID
    • GMAIL_CLIENT_SECRET

Security Notes

  • Send confirmation required - You must always confirm with the user before sending emails, then use --yes
  • Tokens/account metadata stored in repo root .env (GMAIL_SKILL_TOKENS_B64, GMAIL_SKILL_ACCOUNTS_META_B64)
  • Revoke access anytime: https://myaccount.google.com/permissions
  • Apps in "testing" mode may require re-auth every 7 days (publish app to avoid)

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Open in GitHubOpen in ClawHub

Related Skills

Related by shared tags or category signals.

General

image-gen

No summary provided by upstream source.

Repository SourceNeeds Review
4-helincao
General

build

No summary provided by upstream source.

Repository SourceNeeds Review
4-helincao
Coding

github-issues

No summary provided by upstream source.

Repository SourceNeeds Review
5-helincao
General

neo

Browse websites, read web pages, interact with web apps, call website APIs, and automate web tasks. Use Neo when: user asks to check a website, read a web page, post on social media (Twitter/X), interact with any web app, look up information on a specific site, scrape data from websites, automate browser tasks, or when you need to call any website's API. Keywords: website, web page, browse, URL, http, API, twitter, tweet, post, scrape, web app, open site, check site, read page, social media, online service.

Archived SourceRecently Updated
--4ier