← Back to Skills Marketplace
officialdelta

Gmail Secretary

by OfficialDelta · GitHub ↗ · v1.0.27 · MIT-0
cross-platform ⚠ suspicious
2189
Downloads
0
Stars
10
Active Installs
28
Versions
Install in OpenClaw
/install gmail-secretary
Description
Gmail triage assistant using Haiku LLM for classification, label application, and draft replies (uses gog CLI; never auto-sends).
README (SKILL.md)

Gmail Secretary (Alan)

Safety rules (non-negotiable)

  • Never send email automatically. Only create drafts + summaries.
  • Prefer labels over moving/deleting.
  • Keep the voice reference style-focused (patterns + a few short redacted snippets), not a full archive.

Labels (user-friendly)

Use/create these labels:

  • Urgent
  • Needs Reply
  • Waiting On
  • Read Later
  • Receipt / Billing
  • School
  • Clubs
  • Mayo
  • Admin / Accounts

Classification: Agent-based (Haiku)

Classification uses a Haiku LLM agent (via sessions_spawn) instead of regex.

  • scripts/triage-and-draft.sh fetches inbox → writes summaries to cache/gmail-inbox-summaries.json
  • Agent reads summaries, classifies each email, writes results to cache/gmail-triage-labels.json
  • scripts/apply-labels.sh reads classification results and applies Gmail labels via gog

Agent classification prompt context:

  • Student at Stanton College Prep (IB/AP classes)
  • Clubs: FBLA, Science Fair, Medical Society, Psi Alpha, NHS
  • Project: Mayo Clinic cancer cell simulation
  • Companies (Apple, Google, Amazon, etc.) are NOT "School"
  • Newsletters/promos → Read Later
  • Account security/password/verification → Admin / Accounts

Files

  • Voice reference (auto-maintained): references/voice.md
  • Draft queue (generated): /home/delta/.openclaw/workspace/cache/gmail-drafts.md
  • Triage digest (generated): /home/delta/.openclaw/workspace/cache/gmail-triage.md
  • Inbox summaries (intermediate): /home/delta/.openclaw/workspace/cache/gmail-inbox-summaries.json
  • Classification results: /home/delta/.openclaw/workspace/cache/gmail-triage-labels.json

Scripts

  • Build/refresh voice reference from Sent mail:
    • scripts/build-voice-reference.sh (samples last 50 sent messages)
  • Fetch inbox + extract summaries:
    • scripts/triage-and-draft.sh
  • Apply labels from classification:
    • scripts/apply-labels.sh

Workflow

  1. Run triage-and-draft.sh — fetches inbox, extracts summaries
  2. Agent (Haiku) classifies emails from gmail-inbox-summaries.json
  3. Agent writes results to gmail-triage-labels.json
  4. Run apply-labels.sh — applies labels to Gmail threads
  5. Agent writes triage digest to cache/gmail-triage.md for nudges
Usage Guidance
This skill appears to implement a real Gmail triage workflow, but there are a few red flags you should address before installing or running it: - Verify required binaries and paths: the scripts call /home/linuxbrew/.linuxbrew/bin/gog and node, but the skill metadata lists no required binaries. Ensure 'gog' and Node.js are installed at those paths or edit the scripts to point to the correct locations. - Confirm credentials usage: the scripts rely on GOG_ACCOUNT and GOG_KEYRING_PASSWORD (defaults exist). The package metadata should declare these; otherwise you may be surprised when the skill accesses your Gmail via the local gog credential store. Do not set a real password to the weak default value; prefer explicit, documented configuration. - Review data access and outputs: the skill reads inbox and Sent messages to build a voice reference and will write drafts and triage files under /home/delta/.openclaw/workspace/cache. Inspect those generated files (gmail-drafts.md, gmail-triage.md, gmail-inbox-summaries.json, gmail-triage-labels.json) before letting the agent act on them. The voice reference samples include personal context (name, school); confirm you are comfortable with that processing and local storage. - Test manually first: run the scripts yourself in a controlled environment or on a throwaway/secondary Gmail account to verify behavior (that it only creates drafts and applies labels) before granting the agent autonomous access. - Consider limiting autonomy: if you don't want the agent to alter your mailbox without oversight, disable autonomous invocation for this skill or require manual invocation for apply-labels.sh. If the author updates the skill metadata to declare required binaries (gog, node), required env vars (GOG_ACCOUNT, GOG_KEYRING_PASSWORD), and avoids hard-coded absolute paths (or documents them), the incoherences would be resolved and my assessment could be upgraded to benign.
Capability Analysis
Type: OpenClaw Skill Name: gmail-secretary Version: 1.0.27 The skill is a Gmail triage assistant that uses the 'gog' CLI to manage emails and build a writing style reference. It is classified as suspicious due to significant security vulnerabilities and high-privilege data handling: it uses a hardcoded keyring password ('openclaw') and a specific hardcoded email address across multiple scripts (scripts/apply-labels.sh, scripts/build-voice-reference.sh). Additionally, it extracts and stores snippets from the user's sent messages in a local file (references/voice.md), which, while aligned with its stated purpose, constitutes high-risk PII handling without robust protection.
Capability Assessment
Purpose & Capability
The scripts implement exactly what the description says (fetch inbox, build voice reference from Sent, classify with an LLM agent, create drafts, and apply labels). However the registry metadata claims no required binaries or env vars while the scripts clearly require node and the 'gog' CLI (invoked at /home/linuxbrew/.linuxbrew/bin/gog) and use GOG_ACCOUNT/GOG_KEYRING_PASSWORD. The omission of these runtime requirements is an incoherence.
Instruction Scope
Instructions and scripts operate only on the user's Gmail via the gog CLI and local cache files (no external network endpoints other than what gog uses). They read Sent mail to build a voice profile and redact some PII, create draft text and triage summaries, and apply labels. This is within the stated purpose, but the skill will access and process personal email content (including Sent messages) and write files under /home/delta/.openclaw/workspace — the hard-coded paths are environment-specific and potentially surprising.
Install Mechanism
There is no download/install spec (instruction-only + bundled scripts). That avoids remote code fetching, which is lower risk. The scripts will be present on disk as part of the skill package; they invoke existing local binaries rather than installing new ones.
Credentials
The skill requests no env vars in metadata, but the scripts rely on GOG_ACCOUNT and GOG_KEYRING_PASSWORD (with defaults). It also implicitly needs the user's gog-authenticated Gmail credentials via the gog CLI. Requesting access to a mailbox is proportional to a Gmail triage assistant, but the missing/undocumented credential requirements and a hardcoded keyring-password default ('openclaw') are mismatches and could lead to accidental credential exposure or misconfiguration.
Persistence & Privilege
The skill does not set always:true and does not modify other skills. It can, however, modify the user's Gmail labels (apply-labels.sh) which is a meaningful capability. Autonomous invocation is allowed by default (disable-model-invocation is false) — combined with Gmail access this increases impact, but autonomous invocation alone is expected for many skills.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install gmail-secretary
  3. After installation, invoke the skill by name or use /gmail-secretary
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.27
gmail-secretary 1.0.27 - Updated voice reference documentation in references/voice.md. - No functional or workflow changes to core skill.
v1.0.26
- Updated voice reference documentation in `references/voice.md` (auto-maintained). - No changes to workflow or core functionality.
v1.0.25
- Updated voice reference documentation in references/voice.md. - No changes to logic or core workflow; update is documentation-only.
v1.0.24
- Updated the voice reference documentation in references/voice.md. - No changes to logic or workflow; all core features remain unchanged.
v1.0.23
gmail-secretary 1.0.23 - Updated the voice reference documentation for improved style focus and clarity. - No changes made to logic, workflow, or scripts—only the voice reference file was modified.
v1.0.22
- Updated the voice reference documentation in references/voice.md to improve email style guidance. - No changes to core functionality or workflow.
v1.0.21
- Updated voice reference guide in references/voice.md (content or samples may have changed) - No changes to workflow, labels, or core functionality - Maintains strict safety rules: only drafts and summaries, never auto-sends email
v1.0.20
- Updated voice reference documentation in references/voice.md for improved clarity and style guidance. - No functional or workflow changes to the skill itself.
v1.0.19
gmail-secretary 1.0.19 - Updated the voice reference documentation (references/voice.md). - No changes to logic, workflow, or feature set.
v1.0.18
gmail-secretary 1.0.18 Changelog - Updated the voice reference file instructions and usage details in the documentation. - No changes to logic or functionality; documentation only.
v1.0.17
- Documentation update only: revised and/or refreshed contents of references/voice.md. - No changes to code or user-facing features.
v1.0.16
- Updated and refreshed the voice reference file in references/voice.md. - No changes to workflows, scripts, or classification logic.
v1.0.15
- Voice reference generation script and documentation updated for clarity and maintainability. - `scripts/build-voice-reference.sh` now better documents its process for sampling the last 50 sent messages. - Minor language and formatting adjustments in `references/voice.md` for improved guidance.
v1.0.14
gmail-secretary 1.0.14 - Updated the voice reference documentation (references/voice.md). - No changes to core functionality or workflow.
v1.0.13
- Updated the voice reference documentation in references/voice.md. - No functional or workflow changes; core Gmail triage and labeling features remain the same.
v1.0.12
- Updated the voice reference documentation (references/voice.md) to improve clarity and maintain consistency with the skill's guidance. - No changes to core features or logic.
v1.0.11
- Updated the voice reference documentation (references/voice.md). - No changes to functionality or workflow.
v1.0.10
- Updated the voice reference file (`references/voice.md`) for improved style guidance in replies and drafts. - No functional or workflow changes.
v1.0.9
- Updated the voice reference documentation (`references/voice.md`). - No changes to workflow, safety rules, or classification process. - All existing automation and labeling rules remain unchanged.
v1.0.8
gmail-secretary 1.0.8 - Improved code formatting and readability in scripts/apply-labels.sh. - Updated references/voice.md (details not shown in diff). - No changes to workflow or classification logic.
Metadata
Slug gmail-secretary
Version 1.0.27
License MIT-0
All-time Installs 10
Active Installs 10
Total Versions 28
Frequently Asked Questions

What is Gmail Secretary?

Gmail triage assistant using Haiku LLM for classification, label application, and draft replies (uses gog CLI; never auto-sends). It is an AI Agent Skill for Claude Code / OpenClaw, with 2189 downloads so far.

How do I install Gmail Secretary?

Run "/install gmail-secretary" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Gmail Secretary free?

Yes, Gmail Secretary is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does Gmail Secretary support?

Gmail Secretary is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Gmail Secretary?

It is built and maintained by OfficialDelta (@officialdelta); the current version is v1.0.27.

💬 Comments