analyzing-schedule

analyzing-schedule is a skill for Claude Code, Codex from natea/ExoMind. It costs 0 tokens per session (5,487 once invoked), scanned A, original, MIT.

A calendar analysis workflow that reviews how you spend your time and compares it with your priorities.

In plain words
What is it for?
Use it to review calendar patterns, find time for concentrated work, and spot scheduling habits that may contribute to burnout.
Why use it?
It helps reveal overbooked schedules, conflicts, weak priority alignment, and missing focus time before they become persistent problems.

Skill for Claude CodeCodex

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

Good fit Use it to review calendar patterns, find time for concentrated work, and spot scheduling habits that may contribute to burnout.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/natea/exomind/analyzing-schedule
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 natea/ExoMind --skill analyzing-schedule
Clone the repo
git clone --depth 1 https://github.com/natea/ExoMind

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 analyzing-schedule

README.md
[![agentmods](https://agentmods.dev/badge/skills/natea/exomind/analyzing-schedule/github.svg)](https://agentmods.dev/skills/natea/exomind/analyzing-schedule)
Your own site
<a href="https://agentmods.dev/skills/natea/exomind/analyzing-schedule"><img src="https://agentmods.dev/badge/skills/natea/exomind/analyzing-schedule/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 analyzing-schedule

Your own site · 80×15
<a href="https://agentmods.dev/skills/natea/exomind/analyzing-schedule"><img src="https://agentmods.dev/badge/skills/natea/exomind/analyzing-schedule.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 5,487 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.00000 $0.05487
Opus 5 $0.00000 $0.02743
Sonnet 5 $0.00000 $0.01097
Haiku 4.5 $0.00000 $0.00549

Measured 5d ago against content hash 9abbbe26104c, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

analyzing-schedule 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 5d 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.

skills/analyzing-schedule/SKILL.md · 871 lines

How it starts

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

Analyzing Schedule

Overview

This skill helps you gain clarity and control over your time by systematically analyzing your calendar. It reveals patterns in how you spend time, identifies potential problems like overcommitment or misalignment with priorities, and provides insights for better time management decisions.

Purpose

  • Understand Time Allocation: See how time is actually spent vs. intended
  • Detect Overcommitment: Identify scheduling conflicts and unrealistic expectations
  • Assess Priority Alignment: Check if calendar reflects your true priorities
  • Find Focus Time: Locate opportunities for deep work and strategic thinking
  • Prevent Burnout: Recognize unsustainable patterns before they cause problems
  • Optimize Energy: Align tasks with your energy levels throughout day/week

Prerequisites

  • Google Calendar connected via MCP
  • Understanding of your priorities and goals
  • Defined categories for time allocation (optional but helpful)

Step-by-Step Workflow

Phase 1: Data Collection (5-10 minutes)

Gather calendar data for analysis period.

1. Define Analysis Period

Choose appropriate timeframe:

  • Daily Review: Today and tomorrow
  • Weekly Review: This week and next week
  • Monthly Planning: Next 30 days
  • Quarterly Planning: Next 90 days
Ask: "Show me all calendar events for the next 7 days"

MCP Tool: mcp__google-workspace__get_events
Parameters:
  calendar_id: "primary"
  time_min: "2025-10-20T00:00:00Z"
  time_max: "2025-10-27T23:59:59Z"
  max_results: 100
  detailed: true
  user_google_email: "[email protected]"
2. Collect Metrics

Ask for key calendar statistics:

Questions to ask:
1. "How many hours of meetings do I have this week?"
2. "What's my longest consecutive meeting block?"
3. "How many hours of free time remain?"
4. "What types of meetings dominate my schedule?"
5. "Which days are most/least packed?"

Phase 2: Time Allocation Analysis (10-15 minutes)

Categorize and quantify how time is distributed.

Read the full file on GitHub · 871 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. 5d ago First seen · 871 lines · 0 tokens per session scan A 9abbbe26104c

Subscribe to this mod's changes

analyzing-schedule is a skill published in the GitHub repository natea/ExoMind (21 stars, last pushed 10mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 5,487 tokens. 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-03.