remorses/zele
skills/zele/SKILL.md
zele is a multi-account email and calendar CLI for Gmail, IMAP/SMTP (Fastmail, Outlook, any provider), and Google Calendar. It reads, searches, sends, replies, forwards, archives, stars, and trashes emails, manages drafts, labels, attachments, and Gmail filters, and creates, updates, and deletes calendar events with RSVP and free/busy support. Output is YAML so commands can be piped through yq and xargs. ALWAYS load this skill when the user asks to check email, read/send messages, reply or forward, archive or trash threads, manage drafts or labels, download attachments, schedule meetings, check their calendar, RSVP to events, or when they run any `zele` command. Load it before writing any code or shell commands that touch zele so you know the correct subcommand structure, the Google vs IMAP feature matrix, the headless login flow, and the agent-specific rules.
$ install --global
skillsauthnpx skillsauth add remorses/kimaki zeleInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 22, 2026, 3:09 PM20.6s1 file scanned
SKILL.md
- name:
- zele
- description:
- >
zele
Every time you use zele, you MUST fetch the latest README:
curl -s https://raw.githubusercontent.com/remorses/zele/main/README.md # NEVER pipe to head/tail, read the full output
Then run the CLI help once — it already includes every subcommand, option, and flag:
zele --help # NEVER pipe to head/tail, read the full output
The README and zele --help output are the source of truth for commands, options, flags, the Google vs IMAP feature matrix, search operators, and the headless login flow.
Rules
- Never use the TUI. Running
zelewith no subcommand launches a human-facing TUI. Agents must use the CLI subcommands (zele mail list,zele cal events, etc.) which output structured YAML. - Always run
zele whoamifirst when the user asks to operate on a specific account. Pick the exact email from the output and pass it with--account. Never guess account emails. - Never truncate
--helpor README output withhead,tail,sed,awk, orless. Critical rules are spread throughout. Read them in full. - Parse YAML output with
yq, not regex. Pipe IDs throughxargsfor bulk actions. Always use--limit 100(or higher) so you don't miss threads:# read all unread emails zele mail list --filter "is:unread" --limit 100 | yq '.[].id' | xargs zele mail read # bulk archive zele mail list --filter "is:unread" --limit 100 | yq '.[].id' | xargs zele mail archive - Google-only features (labels, Gmail filters,
zele cal *, full profile) fail on IMAP accounts with a clear error. Checkzele whoamioutput for account type before using them. - Headless Google login requires a tmux wrapper because
zele loginis interactive. See the README "Remote / headless login" section for the exact pattern.
Related Skills
remorses/npm-package
development
VerifiedTrustedCommunity
Opinionated TypeScript npm package template for ESM packages. Enforces src→dist builds with tsc, strict TypeScript defaults, explicit exports, and publish-safe package metadata. Use this when creating or updating any npm package in this repo.
1,138SKILL.mdUpdated Apr 25, 2026
remorses/new-skill
documentation
VerifiedTrustedCommunity
Best practices for creating a SKILL.md file. Covers file structure, frontmatter, writing style, and where to place skills in a repository. Use when the user wants to create a new skill, update an existing skill, write a SKILL.md, or asks how skills work.
1,130SKILL.mdUpdated Apr 25, 2026
remorses/new-skill
documentation
VerifiedTrustedCommunity
Best practices for creating a SKILL.md file. Covers file structure, frontmatter, writing style, and where to place skills in a repository. Use when the user wants to create a new skill, update an existing skill, write a SKILL.md, or asks how skills work.
1,087SKILL.mdUpdated Apr 19, 2026
remorses/zustand-centralized-state
tools
VerifiedTrustedCommunity
Centralized state management pattern using Zustand vanilla stores. One immutable state atom, functional transitions via setState(), and a single subscribe() for all reactive side effects. Based on Rich Hickey's "Simple Made Easy" principles: prefer values over mutable state, derive instead of cache, centralize transitions, and push side effects to the edges. Resource co-location in the same store is also valid when lifecycle management is safer that way. Also covers state encapsulation: keeping state local to its owner (closures, plugins, factory functions) so it doesn't leak across the app, reducing the blast radius of mutations. Also covers event sourcing: keeping a bounded event buffer and deriving state with pure functions instead of mutable flags, making event handlers easy to test and reason about. Use this skill when building any stateful TypeScript application (servers, extensions, CLIs, relays) to keep state simple, testable, and easy to reason about. ALWAYS read this skill when a project uses zustand/vanilla for state management outside of React.
1,052SKILL.mdUpdated Apr 25, 2026