plugins/google-workspace/skills/gws-gmail-watch/SKILL.md
Gmail: Watch for new emails and stream them as NDJSON.
npx skillsauth add pleaseai/claude-code-plugins gws-gmail-watchInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
PREREQUISITE: Read
../gws-shared/SKILL.mdfor auth, global flags, and security rules. If missing, rungws generate-skillsto create it.
Watch for new emails and stream them as NDJSON
gws gmail +watch
| Flag | Required | Default | Description |
|------|----------|---------|-------------|
| --project | — | — | GCP project ID for Pub/Sub resources |
| --subscription | — | — | Existing Pub/Sub subscription name (skip setup) |
| --topic | — | — | Existing Pub/Sub topic with Gmail push permission already granted |
| --label-ids | — | — | Comma-separated Gmail label IDs to filter (e.g., INBOX,UNREAD) |
| --max-messages | — | 10 | Max messages per pull batch |
| --poll-interval | — | 5 | Seconds between pulls |
| --msg-format | — | full | Gmail message format: full, metadata, minimal, raw |
| --once | — | — | Pull once and exit |
| --cleanup | — | — | Delete created Pub/Sub resources on exit |
| --output-dir | — | — | Write each message to a separate JSON file in this directory |
gws gmail +watch --project my-gcp-project
gws gmail +watch --project my-project --label-ids INBOX --once
gws gmail +watch --subscription projects/p/subscriptions/my-sub
gws gmail +watch --project my-project --cleanup --output-dir ./emails
development
RTK (Rust Token Killer) reduces LLM token consumption by 60-90% by filtering and compressing command outputs. Use when user asks about token savings, token optimization, RTK usage, `rtk gain`, `rtk discover`, or `rtk proxy`. Triggers on mentions of token reduction, RTK commands, or checking command cost.
tools
Semantic code search using the Semble MCP server. Use when exploring an unfamiliar codebase, finding code by what it does rather than exact text, locating an implementation, understanding how a feature works, or discovering related code. Triggers on requests like "where is X handled", "find the code that does Y", "how does Z work", "search the codebase for", or any semantic/exploratory code question where grep's literal matching is a poor fit.
development
Get best practices for developing applications with Spring Boot.
development
Get best practices for JUnit 5 unit testing, including data-driven tests