Agent skill

Email Assistant

by appleweiping in appleweiping/WEIPING_WIKI

Personal Gmail and Google Workspace email assistant for Vipin.

MITAuto-check passedProductivity & Automation

Install Email Assistant

skills CLI
$ npx skills add appleweiping/WEIPING_WIKI --skill email-assistant -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install appleweiping/WEIPING_WIKI email-assistant --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/appleweiping/WEIPING_WIKI.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skill/email-assistant .claude/skills/email-assistant && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
email-assistant
GitHub stars
119
Token cost
~1.3k tokens
SKILL.md length
394 words
Files
17 (incl. scripts)
Skills in repo
51
Repo updated
First seen
Licence
MIT

At a glance

Personal Gmail and Google Workspace email assistant for Vipin.

  • Works in 6 steps: Clarify which account to use when… → Search/read the smallest relevant set of… → Summarize in Chinese → …
  • Codex needs to search
  • SKILL.md covers Defaults, Local Paths, First-Time Setup and Workflow, plus 3 more sections
  • Runs JavaScript scripts from its folder; calls node

What it does

Email Assistant is an agent skill from appleweiping/WEIPING_WIKI. Personal Gmail and Google Workspace email assistant for Vipin. Use when Codex needs to search, read, summarize, translate, triage, draft, update drafts, or user-approved send email for the UMN and vipinapple Gmail accounts. Optimized for API-first low-interruption workflows, Chinese summaries of English email, polished email drafting, multi-account Gmail profiles, and explicit user approval before any send action.

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 20 other files, including scripts (for example `agents/openai.yaml`, `docs/google-cloud-setup.md` and `package.json`).

It sits in Productivity & Automation, covering Email management. It works with Gmail and Google Workspace. The repository describes itself as: knowledge base managed with an LLM workflow. The licence is MIT.

When your agent uses it

  • Codex needs to search
  • User-approved send email for the UMN and vipinapple Gmail accounts

Example prompts

  • “/email-assistant”

Requirements

  • Node.js

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Clarify which account to use when ambiguous: umn or vipinapple.
  2. Search/read the smallest relevant set of messages.
  3. Summarize in Chinese
  4. Draft the reply and show it to the user.
  5. Create or update a Gmail draft when requested.
  6. Send only after explicit approval, using --confirm-send YES_SEND.

What it can do on your machine

Read from SKILL.md and the folder at commit 76fdc42. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 11 files in scripts/ (JavaScript), which the agent can run.

    Shell commands in SKILL.md call:

    • node

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Email Assistant loads about 1.3k tokens when it runs. Until then it costs about 108 tokens; SKILL.md has 394 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~108
When it runs · the whole SKILL.md, loaded when a task matches
~1.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from appleweiping/WEIPING_WIKI at commit 76fdc42, republished under its MIT licence (© appleweiping). 394 words, ~1,294 tokens.

Download SKILL.mdSave it as .claude/skills/email-assistant/SKILL.md (or your agent's skills folder). This skill also uses 16 other files; get the full folder from GitHub.
name
email-assistant
description
Personal Gmail and Google Workspace email assistant for Vipin. Use when Codex needs to search, read, summarize, translate, triage, draft, update drafts, or user-approved send email for the UMN and vipinapple Gmail accounts. Optimized for API-first low-interruption workflows, Chinese summaries of English email, polished email drafting, multi-account Gmail profiles, and explicit user approval before any send action.

Email Assistant

Use this skill for Vipin's Gmail/Google Workspace email workflows: reading, searching, explaining, summarizing, drafting, and updating Gmail drafts across the umn and vipinapple account profiles.

Defaults

  • Use Gmail API scripts first. Do not open or control the browser for routine mail reading or drafting.
  • Keep normal output in Chinese unless the user asks otherwise.
  • Write outgoing professional or UMN mail in polished English unless the thread clearly uses another language.
  • Default to draft-only. Never send email unless the user explicitly says to send.
  • Use browser automation only for OAuth login, manual user review, or web-only fallback, and only with explicit confirmation before live account actions.
  • Do not store email bodies, tokens, cookies, credentials, browser profiles, or private mail content in the public wiki or Git.

Local Paths

Skill install:

powershell
D:\Research\vipin's knowledgebase\.codex\skills\email-assistant

Source mirror:

powershell
D:\Research\vipin's knowledgebase\skill\email-assistant

OAuth files are local-only and ignored by Git:

powershell
D:\Research\vipin's knowledgebase\.wiki-tmp\email-assistant\auth\credentials.json
D:\Research\vipin's knowledgebase\.wiki-tmp\email-assistant\auth\tokens.json

Override paths only when needed:

powershell
$env:EMAIL_ASSISTANT_AUTH_DIR = "D:\Research\vipin's knowledgebase\.wiki-tmp\email-assistant\auth"
$env:EMAIL_ASSISTANT_LOG_DIR = "D:\Research\vipin's knowledgebase\.wiki-tmp\email-assistant\logs"

First-Time Setup

From the skill directory:

powershell
& "D:\cc\node\corepack.cmd" pnpm install

Create a Google Cloud OAuth Desktop credential with Gmail API enabled, then save the downloaded credentials.json to:

powershell
.wiki-tmp\email-assistant\auth\credentials.json

Authenticate both accounts:

powershell
& "D:\cc\node\corepack.cmd" pnpm run setup -- --account umn --email "<umn email address>"
& "D:\cc\node\corepack.cmd" pnpm run setup -- --account vipinapple --email "<vipinapple email address>"
node scripts/manage-accounts.js --list

If UMN cannot authenticate through Gmail API, mark umn as pending and keep vipinapple usable. Do not replace v1 with fragile browser-only mail handling.

Workflow

  1. Clarify which account to use when ambiguous: umn or vipinapple.
  2. Search/read the smallest relevant set of messages.
  3. Summarize in Chinese:
    • sender
    • what they want
    • deadline or time sensitivity
    • risk or hidden obligation
    • suggested response
  4. Draft the reply and show it to the user.
  5. Create or update a Gmail draft when requested.
  6. Send only after explicit approval, using --confirm-send YES_SEND.
Show full SKILL.md (132 more words)Show less

Commands

Run scripts from the skill directory:

powershell
cd "D:\Research\vipin's knowledgebase\.codex\skills\email-assistant"

List accounts:

powershell
node scripts/manage-accounts.js --list

Search unread UMN mail:

powershell
node scripts/gmail-search.js --account umn --query "is:unread" --limit 10

Search likely action items:

powershell
node scripts/gmail-search.js --account umn --query "(deadline OR due OR bill OR course OR visa OR housing) newer_than:30d" --limit 20

Read one message:

powershell
node scripts/gmail-read.js --account umn --id "<message-id>" --thread

Create a draft:

powershell
node scripts/gmail-drafts.js --account umn --action create --to "person@example.com" --subject "Subject" --body "Draft body"

Update a draft:

powershell
node scripts/gmail-drafts.js --account umn --action update --id "<draft-id>" --to "person@example.com" --subject "Subject" --body "Updated body"

Send a direct message only after explicit user approval:

powershell
node scripts/gmail-send.js --account umn --to "person@example.com" --subject "Subject" --body "Body" --confirm-send YES_SEND

Send an approved draft:

powershell
node scripts/gmail-drafts.js --account umn --action send --id "<draft-id>" --confirm-send YES_SEND

Safety Rules

  • Prefer drafts over sends.
  • Do not delete messages.
  • Do not create filters or forwarding rules unless the user explicitly asks and understands the account-wide effect.
  • Do not expose raw email content in wiki pages, logs, commit messages, or partner prompts.
  • When calling read-only partners for review, redact sender addresses and message bodies unless the user explicitly approves sharing.
  • If OAuth opens a browser, tell the user first because it may need manual account login.

Useful User Prompts

  • "帮我看 UMN 未读邮件,中文讲重点。"
  • "把这封英文邮件讲人话。"
  • "帮我回这封邮件,先写草稿。"
  • "查一下 UMN 有没有 deadline / bill / course / visa 相关邮件。"
  • "写好草稿,我确认后再发。"

© appleweiping, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 16 other files (scripts) in skill/email-assistant of appleweiping/WEIPING_WIKI.

  • SKILL.md
  • .gitignore
  • agents/openai.yaml
  • docs/google-cloud-setup.md
  • package.json
  • pnpm-lock.yaml
  • scripts/action-logger.js
  • scripts/auth/auth-utils.js
  • scripts/auth/paths.js
  • scripts/auth/setup-oauth.js
  • scripts/email-message.js
  • scripts/gmail-drafts.js
  • scripts/gmail-labels.js
  • scripts/gmail-read.js
  • scripts/gmail-search.js
  • scripts/gmail-send.js
  • scripts/manage-accounts.js

Open the folder on GitHubat commit 76fdc42

Compare with similar skills

Email Assistant next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Email Assistant compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Email Assistant this skillappleweiping/WEIPING_WIKI119—~1.3kAutomated safety check: PassMIT
Google Workspaceyc-software/qm15k—~1.8kAutomated safety check: PassMIT
Gws Gmail Readgoogleworkspace/cli31k1 repos~345Automated safety check: PassApache-2.0
Gws Gmail Triagegoogleworkspace/cli31k1 repos~301Automated safety check: PassApache-2.0
Gogtrpc-group/trpc-agent-go1.9k15 repos~1.1kAutomated safety check: PassApache-2.0
Gmail Query Syntaxprovos/ironcurtain612—~971Automated safety check: PassApache-2.0

Similar skills

  • Google Workspace

    yc-software/qm

    Read and act on the user's Gmail, Google Calendar, and Google Tasks through per-user OAuth.

    15k GitHub stars~1.8k tokensUpdated today
    Productivity & AutomationAuto-check passed
  • Gws Gmail Read

    googleworkspace/cli

    Gmail: Read a message and extract its body or headers. An agent skill from googleworkspace/cli.

    31k GitHub starsUsed in 1 repo~345 tokens
    Productivity & AutomationAuto-check passed
  • Gws Gmail Triage

    googleworkspace/cli

    Gmail: Show unread inbox summary (sender, subject, date). An agent skill from googleworkspace/cli.

    31k GitHub starsUsed in 1 repo~301 tokens
    Productivity & AutomationAuto-check passed
  • Gog

    trpc-group/trpc-agent-go

    Google Workspace CLI for Gmail, Calendar, Drive, Contacts, Sheets, and Docs.

    1.9k GitHub starsUsed in 15 repos~1.1k tokens
    Productivity & AutomationAuto-check passed
  • Gmail Query Syntax

    provos/ironcurtain

    Reference for Gmail's search query syntax — operators like is:sent, newerthan:, from:, has:attachment, label:, and how they compose.

    612 GitHub stars~971 tokensUpdated 2 days ago
    Productivity & AutomationAuto-check passed
  • Google

    letta-ai/lettabot

    Google Workspace CLI (gog) for Gmail, Calendar, Drive, Contacts, Sheets, and Docs.

    327 GitHub stars~774 tokensUpdated 4 mo ago
    Productivity & AutomationAuto-check: notes

More from appleweiping/WEIPING_WIKI

All 51 skills in this repo
  • Communication Assistant

    appleweiping/WEIPING_WIKI

    Unified lazy-mode communication assistant for Vipin across WhatsApp, WeChat, QQ, Feishu/Lark, and email.

    119 GitHub stars~1.1k tokensUpdated 1 mo ago
    Auto-check passed
  • Content Refinement Agent

    appleweiping/WEIPING_WIKI

    Step 5 of the PaperOrchestra pipeline (arXiv:2604.05018). An agent skill from appleweiping/WEIPING_WIKI.

    119 GitHub stars~3k tokensUpdated 1 mo ago
    Auto-check passed
  • Chrome Automation

    appleweiping/WEIPING_WIKI

    Connect to and control Google Chrome browser using agent-browser with CDP (Chrome DevTools Protocol).

    119 GitHub starsUsed in 1 repo~5.3k tokens
    Auto-check: warnings
  • Wechat Video Channel Publish

    appleweiping/WEIPING_WIKI

    A skill your agent uses when the user wants to log into 微信视频号, validate cookie state, upload videos, set scheduled publish time, fill long description, set a cover image, or save drafts through a…

    119 GitHub stars~765 tokensUpdated 1 mo ago
    Auto-check passed
  • Feishu Bridge

    appleweiping/WEIPING_WIKI

    Route Feishu/Lark content access for Codex. An agent skill from appleweiping/WEIPING_WIKI.

    119 GitHub stars~906 tokensUpdated 1 mo ago
    Auto-check passed
  • Lark Event

    appleweiping/WEIPING_WIKI

    Lark/Feishu real-time event listening / subscribing / consuming: stream events as NDJSON via lark-cli event consume <EventKey (covers IM message receive, reactions, chat member changes, etc.).

    119 GitHub stars~1.9k tokensUpdated 1 mo ago
    Auto-check passed

Questions about Email Assistant

What does Email Assistant do?

Personal Gmail and Google Workspace email assistant for Vipin. Email Assistant is an agent skill from appleweiping/WEIPING_WIKI. Personal Gmail and Google Workspace email assistant for Vipin.

When should I use Email Assistant?

Email Assistant fits situations like: Codex needs to search; user-approved send email for the UMN and vipinapple Gmail accounts.

How do I install Email Assistant in Claude Code?

Run `npx skills add appleweiping/WEIPING_WIKI --skill email-assistant -a claude-code`. Or copy the skill folder (skill/email-assistant in appleweiping/WEIPING_WIKI) into .claude/skills/email-assistant in your project. Claude Code loads it when a task matches its description.

How do I install Email Assistant in Codex?

Run `npx skills add appleweiping/WEIPING_WIKI --skill email-assistant -a codex`. Or copy the skill folder (skill/email-assistant in appleweiping/WEIPING_WIKI) into .agents/skills/email-assistant in your project. Codex loads it when a task matches its description.

Can I use Email Assistant in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add appleweiping/WEIPING_WIKI --skill email-assistant -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/email-assistant, .gemini/skills/email-assistant, .github/skills/email-assistant and .opencode/skills/email-assistant in your project.

What does Email Assistant need to run?

Going by SKILL.md and its folder, Email Assistant needs JavaScript for the scripts in its folder and the command-line tools its instructions call (node). Our summary lists: Node.js.

Does Email Assistant access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Email Assistant safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Email Assistant use?

Email Assistant is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Email Assistant use?

About 1.3k tokens (SKILL.md is roughly 5.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Email Assistant?

Skills that share tags, products or a category with Email Assistant: Google Workspace (yc-software/qm, 15k stars), Gws Gmail Read (googleworkspace/cli, 31k stars), Gws Gmail Triage (googleworkspace/cli, 31k stars) and Gog (trpc-group/trpc-agent-go, 1.9k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Email Assistant?

appleweiping (a GitHub user) maintains it in appleweiping/WEIPING_WIKI, which has 119 GitHub stars. The repository holds 51 skills in this directory. The repository was last updated on August 26, 2026.

Source: appleweiping/WEIPING_WIKI on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.