Gmail Query Syntax

Community

provos

gmail-query-syntax

Reference for Gmail's search query syntax — operators like is:sent, newer_than:, from:, has:attachment, label:, and how they compose. Read this when constructing a Gmail search query string for the google_workspace.gmail_search_messages Code Mode call, especially when filtering by sent vs received, recency, sender, or labels.

Overview

Publisher	provos
Repository	`ironcurtain`
Skill name	`gmail-query-syntax`
Stars	612
Forks	81
Bundled files	Instructions only
License	Apache-2.0
Links	Skill source Repository Homepage

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
Self-contained
Everything the model needs lives in the instructions — no extra files to sync.
Open source
Published by provos on GitHub. Read the source before you install it.

Installation

Install the Gmail Query Syntax AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/provos/ironcurtain/tree/master/src/workflow/workflows/test-email-summary/skills/gmail-query-syntax
Enable the skill in any chat where you want it available.

Store

Installed

Skills

Add skills

Import one or more skills from a public GitHub folder or a local .skill or .zip archive, or SKILL.md file.

From GitHub URLFrom .skill, .zip, or SKILL.md

GitHub repo or folder

https://github.com/provos/ironcurtain/tree/master/src/workflow/workflows/test-email-summary/skills/gmail-query-syntax

Points to a single skill folder, or any folder that contains multiple skills. Public repos only.

CancelContinue

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/provos/ironcurtain.git /tmp/ironcurtain
mkdir -p .claude/skills
cp -r /tmp/ironcurtain/src/workflow/workflows/test-email-summary/skills/gmail-query-syntax .claude/skills/gmail-query-syntax

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Gmail Query Syntax in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Gmail Query Syntax on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Gmail Query Syntax is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Gmail query syntax primer

These tools live on the google-workspace MCP server, sanitized to google_workspace in Code Mode. In Docker Agent Mode the only MCP tool exposed to Claude Code is execute_code; write TypeScript inside it and call the Gmail tools as dotted callables, e.g. google_workspace.gmail_search_messages({ query: "is:sent", pageSize: 3 }).

gmail_search_messages accepts a query parameter that uses Gmail's standard search operator language — the same syntax the Gmail web UI search box accepts. Operators combine with implicit AND; use OR (uppercase) for disjunction and parentheses for grouping.

Note: gmail_search_messages returns message IDs, thread IDs, and URLs only — not full message contents. To read sender, recipient, subject, date, and body for a matched message, follow up with google_workspace.gmail_get_message (single id) or google_workspace.gmail_get_messages_batch (array of ids).

Common operators

Operator	Meaning	Example
`is:sent`	Messages the user sent (not received)	`is:sent`
`is:unread`	Unread messages	`is:unread`
`is:starred`	Starred messages	`is:starred`
`from:<addr>`	Sender address (substring or full)	`from:alice@example.com`
`to:<addr>`	Recipient address	`to:team@example.com`
`subject:<text>`	Subject contains text	`subject:"weekly update"`
`newer_than:<n>d`	Messages newer than N days (also `h`, `m`, `y`)	`newer_than:7d`
`older_than:<n>d`	Messages older than N (same units)	`older_than:30d`
`after:<date>`	After a date (YYYY/MM/DD)	`after:2025/01/01`
`before:<date>`	Before a date	`before:2025/02/01`
`has:attachment`	Messages with at least one attachment	`has:attachment`
`label:<name>`	Messages with the given Gmail label	`label:invoices`
`in:inbox`	In the inbox (excludes archived)	`in:inbox`
`in:anywhere`	Includes Spam and Trash (rarely needed)	`in:anywhere`

Composing queries

Implicit AND: is:sent newer_than:7d -> sent in the last 7 days.
Explicit OR with grouping: (from:alice OR from:bob) is:unread.
Negation with -: is:sent -label:archived.
Quote multi-word values: subject:"quarterly review".

Tips

Prefer newer_than:Nd over after: when "the last N days" is what you actually want — after: is calendar-anchored and behaves unexpectedly across timezone boundaries.
For "the most recent N sent emails", combine is:sent with the pageSize argument on the dotted call — google_workspace.gmail_search_messages({ query: "is:sent", pageSize: N }) — do not try to express the limit inside the query string. (Pagination tokens come back as pageToken and are passed back in via the same argument name on the next call if you need to walk past the first page.)
The query is case-insensitive for operator names but case-sensitive inside quoted values.

Frequently asked questions

What does the Gmail Query Syntax AI skill do?

Why use Gmail Query Syntax on TypingMind?

Because you install it once and use it with any model. Gmail Query Syntax is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Gmail Query Syntax in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/provos/ironcurtain/tree/master/src/workflow/workflows/test-email-summary/skills/gmail-query-syntax. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Gmail Query Syntax?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Gmail Query Syntax?

As many as you like. As long as a model supports skills, you can use Gmail Query Syntax with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Gmail Query Syntax AI skill free?

Yes. It is published on GitHub by provos under the Apache-2.0 license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Openclaw Docker E2e Authoring

openclaw

OrganizationPopular

Author OpenClaw Docker E2E and live provider Docker lanes.

Openclaw Parallels Smoke

openclaw

OrganizationPopular

Prepare, snapshot, run, rerun, debug, or interpret OpenClaw Parallels guest install, onboarding, gateway smoke, and upgrade checks across macOS, Windows, and Linux.

Openclaw Update

Route routine updates of an existing local or remote OpenClaw Gateway to its installation owner, with automatic session recovery. Defer to deployment-specific skills when available.

Tag Duplicate Prs Issues

openclaw

OrganizationPopular

Use gitcrawl to search duplicate OpenClaw PRs/issues, group related work in prtags, and sync duplicate state to GitHub.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Gmail query syntax primer

Common operators

Composing queries

Tips

Frequently asked questions

Related AI Skills

Set up your own AI workspace now