Read, search, and send Gmail emails. Access Google contacts.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versiongmail-skillExecute the skills CLI command in your project's root directory to begin installation:
Fetches gmail-skill from idanbeck/claude-skills 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 gmail-skill. Access via /gmail-skill 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
3
total installs
3
this week
7
GitHub stars
0
upvotes
Run in your terminal
3
installs
3
this week
7
stars
Read, search, and send Gmail emails. Access Google contacts.
Before sending ANY email, you MUST get explicit user confirmation.
When the user asks to send an email:
This applies even when:
Always confirm first. No exceptions.
On first run, the script will guide you through setup. You need to create a Google Cloud OAuth client once:
gmail.readonly, gmail.send, gmail.modify, contacts.readonly~/.claude/skills/gmail-skill/credentials.jsonThen just run any command - 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.
python3 ~/.claude/skills/gmail-skill/gmail_skill.py search "query" [--max-results N] [--account EMAIL]
Query examples:
from:[email protected] - from specific sendersubject:meeting after:2026/01/01 - subject + datehas:attachment filename:pdf - with PDF attachmentsis:unread - unread emails"exact phrase" - exact matchpython3 ~/.claude/skills/gmail-skill/gmail_skill.py read EMAIL_ID [--account EMAIL]
python3 ~/.claude/skills/gmail-skill/gmail_skill.py list [--max-results N] [--label LABEL] [--account EMAIL]
python3 ~/.claude/skills/gmail-skill/gmail_skill.py send --to EMAIL --subject "Subject" --body "Body text" [--cc EMAIL] [--bcc EMAIL] [--account EMAIL]
Required arguments:
--to / -t - Recipient email address--subject / -s - Email subject line--body / -b - Email body textOptional arguments:
--cc - CC recipients (comma-separated)--bcc - BCC recipients (comma-separated)--account / -a - Send from specific accountExample:
python3 ~/.claude/skills/gmail-skill/gmail_skill.py send \
--to "[email protected]" \
--subject "Meeting Tomorrow" \
--body "Hi, just confirming our meeting at 2pm tomorrow." \
--account [email protected]
python3 ~/.claude/skills/gmail-skill/gmail_skill.py mark-read EMAIL_ID [--account EMAIL]
python3 ~/.claude/skills/gmail-skill/gmail_skill.py mark-unread EMAIL_ID [--account EMAIL]
Both mark-read and mark-unread support multiple IDs (comma-separated):
python3 ~/.claude/skills/gmail-skill/gmail_skill.py mark-read "id1,id2,id3" --account [email protected]
Archives email(s) by removing from inbox. Equivalent to Gmail's 'e' keyboard shortcut.
python3 ~/.claude/skills/gmail-skill/gmail_skill.py mark-done EMAIL_ID [--account EMAIL]
Moves email(s) back to inbox (undo archive).
python3 ~/.claude/skills/gmail-skill/gmail_skill.py unarchive EMAIL_ID [--account EMAIL]
python3 ~/.claude/skills/gmail-skill/gmail_skill.py star EMAIL_ID [--account EMAIL]
python3 ~/.claude/skills/gmail-skill/gmail_skill.py unstar EMAIL_ID [--account EMAIL]
All label commands support multiple IDs (comma-separated):
python3 ~/.claude/skills/gmail-skill/gmail_skill.py star "id1,id2,id3" --account [email protected]
Creates a draft email. Use --reply-to-id when replying to an existing email to ensure proper threading in email clients like Superhuman.
python3 ~/.claude/skills/gmail-skill/gmail_skill.py 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 textOptional 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 accountExample (new email):
python3 ~/.claude/skills/gmail-skill/gmail_skill.py draft \
--to "[email protected]" \
--subject "Draft for Review" \
--body "Here's my draft message."
Example (reply to existing email):
python3 ~/.claude/skills/gmail-skill/gmail_skill.py draft \
--to "[email protected]" \
--subject "Re: Original Subject" \
--body "Thanks for your email..." \
--reply-to-id 19b99b3127793843 \
--account [email protected]
python3 ~/.claude/skills/gmail-skill/gmail_skill.py labels [--account EMAIL]
python3 ~/.claude/skills/gmail-skill/gmail_skill.py contacts [--max-results N] [--account EMAIL]
python3 ~/.claude/skills/gmail-skill/gmail_skill.py search-contacts "query" [--account EMAIL]
# List all authenticated accounts
python3 ~/.claude/skills/gmail-skill/gmail_skill.py accounts
# Remove an account
python3 ~/.claude/skills/gmail-skill/gmail_skill.py logout --account [email protected]
Add accounts by using --account with a new email - browser opens for that account:
# First account (auto-authenticates)
python3 ~/.claude/skills/gmail-skill/gmail_skill.py list
# Add work account
python3 ~/.claude/skills/gmail-skill/gmail_skill.py list --account [email protected]
# Add personal account
python3 ~/.claude/skills/gmail-skill/gmail_skill.py list --account [email protected]
# Use specific account
python3 ~/.claude/skills/gmail-skill/gmail_skill.py search "from:boss" --account [email protected]
Tokens are stored per-account in ~/.claude/skills/gmail-skill/tokens/
python3 ~/.claude/skills/gmail-skill/gmail_skill.py search "is:unread after:2026/01/01"
python3 ~/.claude/skills/gmail-skill/gmail_skill.py read 18d5a3b2c1f4e5d6
python3 ~/.claude/skills/gmail-skill/gmail_skill.py send \
--to "[email protected]" \
--subject "Hello!" \
--body "Just wanted to say hi."
python3 ~/.claude/skills/gmail-skill/gmail_skill.py search-contacts "John Smith"
python3 ~/.claude/skills/gmail-skill/gmail_skill.py list --account [email protected] --max-results 5
All commands output JSON for easy parsing.
pip install google-auth google-auth-oauthlib google-auth-httplib2 google-api-python-client requests~/.claude/skills/gmail-skill/tokens/Prerequisites
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.
openai/skills
libtv-labs/libtv-skills
yejinlei/pdf-ocr-skill
yctimlin/mcp_excalidraw
aktsmm/agent-skills
mcollina/skills
Solid pick for teams standardizing on skills: gmail-skill is focused, and the summary matches what you get after install.
Solid pick for teams standardizing on skills: gmail-skill is focused, and the summary matches what you get after install.
Keeps context tight: gmail-skill is the kind of skill you can hand to a new teammate without a long onboarding doc.
Keeps context tight: gmail-skill is the kind of skill you can hand to a new teammate without a long onboarding doc.
We added gmail-skill from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
We added gmail-skill from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
gmail-skill fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
gmail-skill is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
gmail-skill fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Useful defaults in gmail-skill — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
showing 1-10 of 54