What is schedule-query?

A scheduling assistant that checks configured Google Calendars and drafts replies proposing specific meeting times. Google Calendar is an online calendar service, and the optional email connection lets it use scheduling messages.

Use it to find conflicts across calendars and prepare a reply with available time options.

It avoids manually comparing calendars and composing several rounds of scheduling email. Calendar rules can also identify protected time, such as deep-work blocks.

schedule-query — Skill for Claude Code by chrisblattman/claudeblattman

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add chrisblattman/claudeblattman --skill schedule-query

Clone the repo

git clone --depth 1 https://github.com/chrisblattman/claudeblattman

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/chrisblattman/claudeblattman/schedule-query/github.svg)](https://agentmods.dev/skills/chrisblattman/claudeblattman/schedule-query)

Your own site

<a href="https://agentmods.dev/skills/chrisblattman/claudeblattman/schedule-query"><img src="https://agentmods.dev/badge/skills/chrisblattman/claudeblattman/schedule-query/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/chrisblattman/claudeblattman/schedule-query"><img src="https://agentmods.dev/badge/skills/chrisblattman/claudeblattman/schedule-query.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 17 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,225 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00017	$0.02225
Opus 5.5	$0.00007	$0.00890
Sonnet 5.5	$0.00003	$0.00445
Haiku 4.5	$0.00002	$0.00222

Measured today against content hash 8f8aa11aafbd, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

schedule-query scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured today.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/schedule-query/SKILL.md · 221 lines

How it starts

The opening of the file, as written. The whole thing — 221 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Schedule Query

v1.1 — Check calendar availability and draft scheduling replies with specific time proposals

Check calendar availability across your configured Google calendars and draft a scheduling reply with specific time proposals. Can be used standalone or invoked from a morning workflow when a scheduling email is detected.

Prerequisites

Google Calendar MCP — google_workspace_mcp with calendar and Gmail tools enabled
Calendar policy config — ~/.claude-assistant/config/calendar-policy.md (calendar IDs, scheduling preferences, deep work protection). Download the template from the GitHub repo (see First-Time Setup).
Email voice config (optional) — ~/.claude-assistant/config/email-voice.md for tone/voice templates
Goals file (optional) — ~/.claude-assistant/config/goals.yaml for deep work block protection

First-Time Setup

Create config directory:
```
mkdir -p ~/.claude-assistant/config
```
Create calendar-policy.md from the template. At minimum, fill in:
- Calendar IDs — list every Google Calendar you want checked for conflicts. Find these in Google Calendar Settings > [Calendar name] > "Integrate calendar" > Calendar ID.
- Scheduling preferences — working hours, buffer times, deep work blocks
- Your timezone — e.g., America/New_York, America/Chicago, Europe/London
Test:
```
/schedule-query range:3
```
This queries the next 3 days to verify calendar access works.

Arguments

$ARGUMENTS can include:

with:[name] — who to meet with (searches Gmail for their email)
duration:[minutes] — meeting length (default: 30)
range:[days] — how far ahead to look (default: 14)
email:[id] — reply to a specific email thread with availability
(freeform text) — "schedule a meeting with [Name] next week about the paper"

Instructions

Step 1: Read Config

Read these files:

~/.claude-assistant/config/calendar-policy.md — calendar IDs, scheduling preferences, deep work protection
~/.claude-assistant/config/goals.yaml — for deep work block protection (if exists)
~/.claude-assistant/config/email-voice.md — email voice rules (if exists)

Read the full file on GitHub · 221 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

today First seen · 221 lines · 17 tokens per session scan A 8f8aa11aafbd

Subscribe to this mod's changes

schedule-query is a skill published in the GitHub repository chrisblattman/claudeblattman (476 stars, last pushed today), licensed MIT. It adds 17 tokens to every session and 2,225 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-11-06.

Project management academic-research ai-tools claude-ai mkdocs

schedule-query next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
schedule-querychrisblattman/claudeblattman	Skill	476	today	MIT	A	17	Claude Code
skill-builderyusufkaraaslan/Skill_Seekers	Skill	15k	1mo ago	MIT	A	38	Claude Code, Codex
strategic-revisionflonat/flonat-research	Skill	149	3d ago	MIT	A	66	Claude Code
skill-creatorflonat/flonat-research	Skill	149	3d ago	MIT	A	41	Claude Code
beamer-deckflonat/flonat-research	Skill	149	3d ago	MIT	A	63	Claude Code
numerical-checkflonat/flonat-research	Skill	149	3d ago	MIT	A	65	Claude Code
skill-preflightflonat/flonat-research	Skill	149	3d ago	MIT	A	34	Claude Code