scheduling-tasks

scheduling-tasks is a skill for Claude Code, Codex from natea/ExoMind. It costs 0 tokens per session (6,700 once invoked), scanned A, original, MIT.

A workflow that turns tasks from a to-do list into time blocks on a calendar. It considers available time, priorities, task type, and energy level.

In plain words
What is it for?
Scheduling focused work, fitting tasks into open calendar time, protecting deep-work periods, and reducing overcommitment.
Why use it?
It helps prevent important work from staying indefinitely on a task list and exposes when plans exceed available capacity.

Skill for Claude CodeCodex

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

Good fit Scheduling focused work, fitting tasks into open calendar time, protecting deep-work periods, and reducing overcommitment.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/natea/exomind/scheduling-tasks
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 scheduling-tasks
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 scheduling-tasks

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/natea/exomind/scheduling-tasks"><img src="https://agentmods.dev/badge/skills/natea/exomind/scheduling-tasks.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 6,700 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.06700
Opus 5 $0.00000 $0.03350
Sonnet 5 $0.00000 $0.01340
Haiku 4.5 $0.00000 $0.00670

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

Security

Grade A, and why

scheduling-tasks 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/scheduling-tasks/SKILL.md · 1,001 lines

How it starts

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

Scheduling Tasks

Overview

This skill bridges the gap between task management and calendar management. It transforms abstract tasks and to-do items into concrete time blocks on your calendar, ensuring that important work actually gets done rather than perpetually remaining on a list. This is the critical link between planning and execution.

Purpose

  • Convert Intentions to Actions: Move tasks from lists into actual scheduled time
  • Realistic Planning: Ensure tasks fit into available time
  • Priority Execution: Schedule most important tasks first
  • Deep Work Protection: Block focused time for complex tasks
  • Energy Optimization: Match tasks to appropriate energy levels
  • Prevent Overcommitment: Visualize true workload capacity
  • Increase Follow-Through: Scheduled tasks are 3x more likely to be completed

Prerequisites

  • Google Calendar connected via MCP
  • Google Tasks or task list connected via MCP
  • Completed "Analyzing Schedule" skill (understand available time)
  • Clear priorities and goals

Core Principles

1. Task Types Require Different Scheduling

Deep Work Tasks (2-4 hours):

  • Complex problem-solving
  • Creative work
  • Strategic thinking
  • Learning new skills → Need: Uninterrupted morning blocks, high energy

Shallow Work Tasks (30-60 min):

  • Email processing
  • Admin tasks
  • Quick updates
  • Routine work → Can do: Between meetings, afternoon, lower energy

Quick Tasks (< 15 min):

  • Quick replies
  • Simple updates
  • Status checks → Can do: Anytime, batch together

Meeting Prep (15-30 min before):

  • Review agenda
  • Prepare materials
  • Gather context → Must schedule: Before meeting, never skip

2. Time Blocking Fundamentals

Rules:

  1. Deep work needs 90-180 minute blocks minimum
  2. Include buffer time between different activities
  3. Schedule tasks during appropriate energy levels
  4. Always include prep time for meetings
  5. Leave 25% of time unscheduled for unexpected items
  6. Batch similar tasks together

Read the full file on GitHub · 1,001 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 · 1,001 lines · 0 tokens per session scan A 387c05e82084

Subscribe to this mod's changes

scheduling-tasks 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 6,700 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.

Related

Other skills, from other repositories

recipe-create-meet-space

Create a Google Meet meeting space and share the join link.

googleworkspace/cli · 18 tokens

workthreads

SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…

specstoryai/getspecstory · 126 tokens

atmos-config

Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.

cloudposse/atmos · 31 tokens

story-readiness

Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…

Donchitos/Claude-Code-Game-Studios · 77 tokens

autotask-creator

Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.

Orkas-AI/Orkas · 5 tokens

monorepo-management

Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.

wshobson/agents · 54 tokens