Menú
Gmail CLI for searching emails, reading threads, sending messages, managing drafts, and handling labels/attachments.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
| name | gmcli |
| description | Gmail CLI for searching emails, reading threads, sending messages, managing drafts, and handling labels/attachments. |
Command-line interface for Gmail operations.
npm install -g @mariozechner/gmcli
First check if already configured:
gmcli accounts list
If no accounts, guide the user through setup:
gmcli accounts credentials ~/path/to/credentials.jsongmcli accounts add <email> (use --manual for browserless OAuth)Run gmcli --help for full command reference.
Common operations:
gmcli <email> search "<query>" - Search emails using Gmail query syntaxgmcli <email> thread <threadId> - Read a thread with all messagesgmcli <email> send --to <emails> --subject <s> --body <b> - Send emailgmcli <email> labels list - List all labelsgmcli <email> drafts list - List drafts~/.gmcli/credentials.json - OAuth client credentials~/.gmcli/accounts.json - Account tokens~/.gmcli/attachments/ - Downloaded attachmentsfrom:, subject:, has:attachment, after:, before:gmcli accounts add <email>Web search and content extraction via Brave Search API. Use for searching documentation, facts, or any web content. Lightweight, no browser required.
Interactive browser automation via Chrome DevTools Protocol. Use when you need to interact with web pages, test frontends, or when user interaction with a visible browser is required.
Create software architecture diagrams using the C4 model (Context, Containers, Components, Code). Applies Simon Brown's diagramming principles: titles, legends, directional arrows, explicit text, abstractions-first. Use when user asks for architecture diagrams, system diagrams, C4 diagrams, or wants to document software structure.
Ultra-compressed communication mode. Cuts token usage ~75% by dropping filler, articles, and pleasantries while keeping full technical accuracy. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman.
Query the cerebro cortex knowledge base for project context, journal entries, intent/goals, TODOs, and statistics. Use when the user asks about their projects, wants to read journal entries, check goals/intentions, search for TODOs across repos, or get an overview of their activity data. Also use when browsing what the user has been working on across their side projects.
Disciplined diagnosis loop for hard bugs and performance regressions. Reproduce → minimise → hypothesise → instrument → fix → regression-test. Use when user says "diagnose this" / "debug this", reports a bug, says something is broken/throwing/failing, or describes a performance regression.