Agent skill · operations · alirezarezvani
deep-work
Use when someone wants to plan a deep work day, time-block their calendar or task list, budget or cut shallow work, protect focus hours, track deep-work sessions and streaks, run an end-of-day shutdown ritual, or says "/deep-work" or "/time-block". Classifies tasks deep vs shallow, builds an energy-first time-blocked schedule that refuses deep demand past the 4-hour ceiling, batches shallow work into at most two windows, and logs focus sessions against a weekly target.
Why this skill is useful
Adds 3 executable Python scripts for deep work scheduling and tracking that aren't in public documentation.
What it needs
Requires python installed locally. About 4k tokens when loaded. Last updated 2026-08-05. 23,939 stars on the source repository.
What this skill does
Deep Work — Time-Block the Day, Budget the Shallow Portability: Reasoning-led skill with 3 stdlib Python scripts. No external APIs, no LLM calls in scripts. Works in Claude Code CLI and Claude.ai web. The scripts fix the arithmetic; you keep the judgment. What this does A calendar full of reactions is not a plan. This skill turns a raw task list into a day where attention is the protected resource: deep tasks get the earliest hours in blocks of at least 90 minutes, shallow work is batched into at most two windows, buffers absorb attention residue, and the schedule flatly refuses more than 4 hours of deep demand — the trained daily ceiling. A local ledger of focus sessions keeps the weekly deep-hours target measured, not felt. Step 1 — Classify and budget the shallow Ask for today's task list with rough minutes per task (or take it from $ARGUMENTS). The auditor classifies each task deep vs shallow (keyword heuristics; an explicit :deep/:shallow suffix always wins), computes the shallow share against the budget, and prints the forcing question for every shallow item — how long would it take to train a smart recent graduate to do this? OVER-BUDGET (exit 2) means cut, batch, or delegate before any schedule is built. Step 2 — Block the day Feed the surviving tasks to the planner with the day's hard start and hard end (fixed-schedule productivity: the end time does not move). Deep first and earliest, 10-minute buffers, shallow in two batches (late morning + end of day), an optional fixed lunch: Two refusals, both exit 2: deep demand past the 4-hour cap (the planner names what to defer), and shallow overflow past --end (the planner names what to drop — the day never silently extends). Step 3 — Log the session, keep the streak After each real focus block, log it. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills alirezarezvani/deep-work--cd0cab