gmail-watcher

Monitor Gmail for unread or important emails and create Needs_Action action files.

Updated Mar 17, 2026
One-click install
npx skills add https://github.com/akbarfarooq2006/Hackathon0_Digital_FTE --skill gmail-watcher-akbarfarooq2006
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gmail-watcher
Source: https://github.com/akbarfarooq2006/Hackathon0_Digital_FTE/tree/main/.qwen/skills/gmail-watcher
Command: npx skills add https://github.com/akbarfarooq2006/Hackathon0_Digital_FTE --skill gmail-watcher-akbarfarooq2006

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires google-api-python-client, google-auth-httplib2, google-auth-oauthlib, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Gmail inbox management is time-consuming and prone to missed items; this skill watches Gmail for unread or important messages and converts them into actionable notes stored in Needs_Action for processing by the AI workflow.

Core Features & Use Cases

  • Gmail Watching: Monitors unread or important emails and creates Needs_Action action files for downstream processing.
  • Workflow Integration: Integrates with the vault's processing pipeline and HITL approvals.
  • Use Case Example: When a high-priority email arrives, automatically generate a task and route it for review.

Quick Start

Start the Gmail watcher to generate Needs_Action action files from new emails.

Frequently Asked Questions about gmail-watcher

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

FAQPage Schema
How do I automate Gmail monitoring to create actionable tasks from unread emails?

Automating Gmail monitoring uses a watcher script to poll for unread or important emails and generate Needs_Action files. This converts incoming messages into actionable notes for downstream AI workflow processing and triage.

Do I need OAuth credentials and Gmail API access to monitor my inbox automatically?

Yes, OAuth credentials and Gmail API access are required to monitor your inbox automatically. The watcher script uses these dependencies to authenticate, poll unread messages, and create action files in your local vault structure.

What is the best way to route high-priority Gmail alerts into a team triage pipeline?

Routing high-priority Gmail alerts into a triage pipeline is achieved by watching for important emails and converting them into Needs_Action files. This routes the generated tasks through an approval and execution pipeline for team review.

Can I integrate Gmail inbox alerts with a vault workflow and human-in-the-loop approvals?

Integrating Gmail alerts with a vault workflow and human-in-the-loop approvals is supported. The watcher monitors unread emails, generates action notes in the Needs_Action folder, and passes them through the vault's processing pipeline for HITL review.

How does the watcher script handle unread Gmail messages to prevent missed items?

The watcher script handles unread Gmail messages by polling the inbox for unread or important emails and automatically generating action files. This mechanism ensures important messages are captured as tasks, preventing missed items during inbox triage.

Are there limitations when using a local vault structure for Gmail action files?

Using a local vault structure for Gmail action files requires a local directory to store Needs_Action notes and depends on continuous execution of the watcher script. It operates locally, meaning automated polling stops if the local environment is inactive.