scheduling

scheduling is a skill for Claude Code, Codex from taslim/nanoclaw-gws-ea. It costs 43 tokens per session (1,547 once invoked), scanned A, original, MIT.

A calendar assistant for booking, moving, declining, and suggesting meeting times. It accounts for calendar permissions, availability, relationship priority, and follow-up records.

In plain words
What is it for?
Use it to find suitable times, create meetings, move or decline events, and propose alternatives. It is also for checking calendar access and updating related matter records after an event.
Why use it?
It helps prevent scheduling conflicts and avoids changing calendars that are read-only or outside the permitted rules. It also keeps decisions consistent when several calendars or people are involved.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to find suitable times, create meetings, move or decline events, and propose alternatives. It is also for checking calendar access and updating related matter records after an event.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/taslim/nanoclaw-gws-ea/scheduling
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 taslim/nanoclaw-gws-ea --skill scheduling
Clone the repo
git clone --depth 1 https://github.com/taslim/nanoclaw-gws-ea

Made for: Claude Code, Codex.

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.

agentmods badge for scheduling

README.md
[![agentmods](https://agentmods.dev/badge/skills/taslim/nanoclaw-gws-ea/scheduling/github.svg)](https://agentmods.dev/skills/taslim/nanoclaw-gws-ea/scheduling)
Your own site
<a href="https://agentmods.dev/skills/taslim/nanoclaw-gws-ea/scheduling"><img src="https://agentmods.dev/badge/skills/taslim/nanoclaw-gws-ea/scheduling/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.

agentmods 80×15 button for scheduling

Your own site · 80×15
<a href="https://agentmods.dev/skills/taslim/nanoclaw-gws-ea/scheduling"><img src="https://agentmods.dev/badge/skills/taslim/nanoclaw-gws-ea/scheduling.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 43 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,547 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00043 $0.01547
Opus 5.5 $0.00017 $0.00619
Sonnet 5.5 $0.00009 $0.00309
Haiku 4.5 $0.00004 $0.00155

Measured 1mo ago against content hash b128e17032ff, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

scheduling 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 1mo ago.

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.

templates/container/skills/scheduling/SKILL.md · 134 lines

How it starts

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

Scheduling

Calendars

Name ID Notes
{{PRINCIPAL_CALENDAR_ROWS}}

Always use the calendar ID when calling calendar tools — not the display name. The first calendar listed is your primary — default to creating new events there unless context dictates otherwise (e.g. personal events on a personal calendar).

Week Template

Availability hours are the hard boundary for Tier 3-5 scheduling. Tier 1 and Tier 2 (family, close friends, key partners) get flexibility beyond these windows — use the notes and judgment to find something that works.

Monday

  • Available: 9am–5pm
  • Notes:

Tuesday

  • Available: 9am–5pm
  • Notes:

Wednesday

  • Available: 9am–5pm
  • Notes:

Thursday

  • Available: 9am–5pm
  • Notes:

Friday

  • Available: 9am–5pm
  • Notes:

Saturday

  • Notes: No meetings preferred.

Sunday

  • Notes: No meetings preferred.

Calendar Access

Respect each calendar's mode (queried from the API at use time):

  • freebusy — you can see when your principal is blocked but not why. Treat as immovable terrain. Schedule around it.
  • readonly — you can read event details but not modify. Use for context only.
  • readwrite — full access, but don't create events here unless the context calls for it (e.g., personal events on a personal calendar). Follow the table notes.

You can only edit events where your principal is the organizer. For events organized by others, don't edit directly — it only changes your principal's copy and won't reach other attendees. Instead, send an email to the organizer requesting the change.

When a freebusy calendar conflicts with a calendar you can write to, the freebusy one wins — move the event you control or find a different time.

Judgment

The question is never "should I confirm this?" It's how hard is this to undo if I get it wrong?

Who's asking matters

→ See the relationships skill for tier definitions, assessment, and Google Contacts lookup.

Read the full file on GitHub · 134 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.

  1. 1mo ago First seen · 134 lines · 43 tokens per session scan A b128e17032ff

Subscribe to this mod's changes

scheduling is a skill published in the GitHub repository taslim/nanoclaw-gws-ea (11 stars, last pushed today), licensed MIT. It adds 43 tokens to every session and 1,547 once invoked, about $0.0002 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-09-18.