Refresh OAuth tokens and read recent Gmail messages via the Gmail API.
npx skills add https://github.com/AllenZhou/MIRISE --skill hermes-gmail-read
Please help me install this Agent Skill. Skill: hermes-gmail-read Source: https://github.com/AllenZhou/MIRISE/tree/main/agents/hermes-utils/skills/hermes-gmail-read Command: npx skills add https://github.com/AllenZhou/MIRISE --skill hermes-gmail-read
Read recent Gmail messages in the MIRISE Hermes prod workspace by refreshing the stored OAuth token directly and calling Gmail API. Use when himalaya is unavailable or scripts/shared/read_gmail.py is broken.
Run the read_gmail.py script in the Hermes production workspace with the appropriate MIRISE_RUNTIME_ENV_FILE to supply env vars and the required command-line flags to fetch recent mail.
High-intent search queries and answers about installing and using this skill.
To read recent Gmail messages in a cron job, you can refresh the stored OAuth token directly and call the Gmail API. This provides a non-interactive, cron-safe read path for headless environments.
Reading Gmail in headless production environments often fails when the standard mail CLI path like himalaya is unavailable or read_gmail.py is broken, requiring an automated OAuth token refresh to avoid interactive prompts.
Yes, you need a valid Gmail OAuth token to fetch recent mail in automated environments. The process uses stored credentials and requires correct environment variables to query the Gmail API without interactive authentication.
The best way to automate reading Gmail in a non-interactive runtime is to use a script that refreshes the stored OAuth token and queries the Gmail API. This approach avoids interactive prompts and works in cron-style environments.
Yes, you can use the Gmail API to monitor an inbox without himalaya. By refreshing a stored OAuth token and calling the Gmail API directly, you can securely read recent messages in headless workspaces where himalaya is unavailable.
Running a Gmail API read script in production requires a MIRISE_RUNTIME_ENV_FILE to supply the correct environment variables. This setup ensures the non-interactive runtime can access stored credentials and refresh the OAuth token.
NicholasSutinAutomate Vercel deployments and environment management using token-based authentication.
cellarwoodApply Gmail labels to matching messages and archive threads.
vm0-aiRead, search, and send Gmail messages via REST API.
lvndryManage email accounts through the Himalaya CLI for reading, sending, and organizing messages.
