hermes-gmail-read

Name: hermes-gmail-read
Availability: InStock
Author: Allen

Refresh OAuth tokens and read recent Gmail messages via the Gmail API.

Updated Aug 27, 2026

Search Tags:#automation #oauth #gmail #cron #hermes #token-refresh #gmail-api

Ready to run

npx skills add https://github.com/AllenZhou/MIRISE --skill hermes-gmail-read

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

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.

Core Features & Use Cases

Provides a cron-safe, non-interactive read path by refreshing the OAuth token and querying the Gmail API.
Uses stored credentials to avoid interactive authentication in headless environments.
Use Case: Monitor Hermes prod inbox for recent messages without requiring interactive login.

Quick Start

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.

Frequently Asked Questions about hermes-gmail-read

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I read recent Gmail messages in a cron job without interactive login?▼

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.

Why does reading Gmail fail in headless production 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.

Do I need a valid Gmail OAuth token to fetch recent mail in automated environments?▼

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.

What is the best way to automate reading Gmail in a non-interactive runtime?▼

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.

Can I use the Gmail API to monitor an inbox without himalaya?▼

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.

What environment variables are required to run a Gmail API read script in production?▼

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.