agentsclimarketplace

Deep work optimization

Skill fabioc-aloha/Alex_Skill_Mall/plugins/devops-process/deep-work-optimization

284 curated plugins for AI assistants across 16 categories: security, Azure, documentation, code quality, cloud infrastructure, and more. Works with GitHub Copilot. Drop into .github/skills/local/ and go.

Install
npx -y skills add fabioc-aloha/Alex_Skill_Mall --skill deep-work-optimization

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Focus blocks, distraction management, and flow state triggers for cognitively demanding work

SKILL.md

11.1 KB, ~2.7k tokens by cl100k_base, as published. Nobody here has run it

Skill: Deep Work Optimization

Focus blocks, distraction management, and flow state triggers for cognitively demanding work.

Metadata

FieldValue
Skill IDdeep-work-optimization
Version1.0.0
CategoryProductivity
DifficultyIntermediate
PrerequisitesNone
Related Skillscognitive-load-management, meeting-efficiency, frustration-recognition

Overview

Deep work is the ability to focus without distraction on cognitively demanding tasks. In Cal Newport's framework, deep work produces rare and valuable results that can't be replicated by shallow multitasking.

The Deep Work Hypothesis

The ability to perform deep work is becoming increasingly rare at exactly the same time it is becoming increasingly valuable in our economy.

This skill helps maximize deep work capacity for dissertation writing, complex analysis, architecture design, and creative problem-solving.


Module 1: Understanding Deep Work

Deep vs. Shallow Work

Deep WorkShallow Work
Cognitively demandingLogistical, low-value
Creates new valueMaintains status quo
Difficult to replicateEasily automated
Requires uninterrupted focusTolerates interruption
Examples: Writing, coding, analysisExamples: Email, meetings, admin

The Attention Residue Problem

When you switch tasks, attention doesn't fully transfer—residue from the previous task reduces cognitive capacity.

Research finding (Leroy, 2009): People who frequently switch tasks perform worse than those who complete tasks before moving on.

Implication: Batch similar shallow work; protect deep work blocks from interruption.

Deep Work Capacity

FactorImpact on Capacity
PracticeIncreases (like a muscle)
RestEssential for recovery
Start of dayTypically highest capacity
After interruption23 minutes to recover (Iqbal & Horvitz)
CaffeineTemporary boost, then crash

Typical daily limit: 4 hours of true deep work (trained professional).


Module 2: Deep Work Scheduling

The Four Philosophies

PhilosophyDescriptionBest For
MonasticEliminate all shallow workWriters, researchers
BimodalDedicated deep periods (days/weeks)Academics on sabbatical
RhythmicDaily fixed-time deep blocksMost professionals
JournalisticOpportunistic deep workExperienced practitioners

Recommended for Fabio: Rhythmic philosophy with morning deep blocks (6-10 AM) for dissertation, bimodal when possible (full days for writing sprints).

Time Blocking

Assign every minute of your day to a block:

6:00 - 6:30  | Morning routine
6:30 - 10:00 | DEEP WORK: Dissertation writing
10:00 - 10:30| Break, shallow batch
10:30 - 12:00| DEEP WORK: Analysis/Research
12:00 - 13:00| Lunch, walk
13:00 - 17:00| Work meetings, shallow work
17:00 - 17:30| Daily shutdown ritual

Focus Session Tracking

{
  "date": "2026-04-14",
  "sessions": [
    { "start": "06:30", "end": "10:00", "type": "deep", "task": "Chapter 3 draft", "quality": 4 },
    { "start": "10:30", "end": "12:00", "type": "deep", "task": "UTAUT analysis", "quality": 3 }
  ],
  "deep_hours": 5.0,
  "interruptions": 2,
  "notes": "Morning block productive; afternoon meeting overran"
}

The Shutdown Ritual

End each workday with a complete shutdown:

  1. Review tasks - Check that nothing urgent is missed
  2. Check calendar - Next day preparation
  3. Capture loose ends - Write down any lingering thoughts
  4. Say the phrase - "Shutdown complete" (triggers mental release)

Why it works: Zeigarnik effect—incomplete tasks occupy mental space. The ritual signals completion.


Module 3: Environment Design

Physical Environment

ElementOptimization
LocationDedicated deep work space (not email/meetings space)
LightingNatural light or warm artificial
TemperatureSlightly cool (68-72°F)
SeatingErgonomic, supports long sessions
VisualMinimal distraction, clean desk

Digital Environment

ElementOptimization
NotificationsAll off during deep work
EmailBatch 2-3x daily, not continuous
Slack/TeamsStatus: Focus mode, check at block ends
BrowserBlock distracting sites (Freedom, Cold Turkey)
PhoneDifferent room or drawer

The Focus Mode Protocol

Before starting deep work:

  1. Close email client completely
  2. Set Teams/Slack to "Do Not Disturb"
  3. Put phone in another room
  4. Open only necessary applications
  5. Start a timer (Pomodoro or fixed block)
  6. Have water/coffee ready

Module 4: Flow State Triggers

Conditions for Flow (Csikszentmihalyi)

ConditionImplementation
Clear goalsKnow exactly what you're working on
Immediate feedbackSee progress as you work
Challenge-skill balanceTask is hard but doable
Deep concentrationNo interruptions
Sense of controlAutonomy over approach
Altered time perceptionHours feel like minutes

Pre-Work Rituals

Triggers that signal "deep work mode" to your brain:

RitualPurpose
Same time dailyCircadian consistency
Same locationEnvironmental trigger
Same beverageSensory anchor
Same music (or silence)Auditory cue
Brief review of goalsClarity of purpose

Music for Deep Work

GenreBest ForWhy
Video game soundtracksCoding, analysisDesigned for focus
Lo-fi hip hopWriting, creativeNon-intrusive rhythm
Classical (baroque)Complex thinkingStructured, no lyrics
White/brown noiseAny deep workMasks distractions
SilenceHighest complexityMaximum cognitive resources

Module 5: Distraction Management

The Distraction Hierarchy

LevelSourceSolution
ExternalNotifications, peopleEnvironment design, signaling
InternalWandering thoughtsCapture list, meditation
Task-switch"Quick check" urgesDelayed gratification
BoredomResistance to hard thinkingPush through, build tolerance

The Capture List

Keep a notepad for intrusive thoughts:

During Deep Work Session:
- "Check if package delivered" → write down, continue
- "Reply to Sarah's email" → write down, continue
- "Buy milk" → write down, continue

After Session:
- Process the list during shallow work time

The 10-Minute Rule

When tempted to check email/social:

  1. Note the urge
  2. Wait 10 minutes
  3. Continue working
  4. After 10 minutes, reassess

Usually: The urge passes. The habit of delayed gratification builds focus capacity.

Attention Restoration

When focus degrades:

DurationRestoration
5 minutesLook out window, stretch
15 minutesWalk outside
30 minutesNap (proven cognitive benefits)
60 minutesComplete break, different activity

Module 6: Measuring and Improving

Deep Work Metrics

MetricTargetTracking
Deep work hours/day3-4 hoursTime log or app
Longest unbroken session90+ minutesTimer records
Deep/shallow ratio50%+ deepWeekly review
Output per sessionVaries by taskSelf-assessment

Weekly Review Questions

  1. How many deep work hours this week?
  2. What interrupted my longest session?
  3. What shallow work could be eliminated?
  4. When was I in flow state?
  5. What will I do differently next week?

Building Capacity

WeekTargetNotes
1-21 hour/dayBuild habit
3-41.5 hours/dayExtend sessions
5-62 hours/dayAdd second block
7-82.5 hours/dayOptimize environment
9+3-4 hours/daySustainable maximum

Integration with the AI assistant

Session Start: Deep Work Mode

When user says "deep work", "focus session", or "dissertation time":

  1. Confirm goal: "What's the specific deliverable for this session?"
  2. Set duration: "90-minute block, or different duration?"
  3. Reduce the AI assistant verbosity: Shorter responses, fewer suggestions
  4. Defer non-urgent: "I'll note that for after the session"
  5. Track time: Log session for weekly review

During Deep Work

  • Minimize interruption: Only respond to direct questions
  • Capture distractions: "I've noted that—let's handle it after"
  • Encourage continuation: "Good progress—keep going"
  • Respect time: Warn at 10 minutes before end

Session End

  1. Celebrate completion: "90 minutes of deep work—well done"
  2. Process capture list: Address items noted during session
  3. Log metrics: Update deep work tracking
  4. Suggest break: "Take 15 before next session?"

Quick Reference

Deep Work Checklist

  • Goal for session is specific and written
  • Time block scheduled and defended
  • Notifications disabled (all devices)
  • Environment prepared (clean, comfortable)
  • Capture list ready for intrusive thoughts
  • Water/beverage at hand
  • Timer started
  • Shutdown ritual planned

Emergency Focus Recovery

When you can't seem to focus:

  1. Acknowledge: "I'm struggling today—that's okay"
  2. Start small: "Just 25 minutes (Pomodoro)"
  3. Lower the bar: "I'll just outline, not write perfectly"
  4. Change location: Different room, coffee shop
  5. Try tomorrow: Sometimes rest is the answer

The Dissertation Deep Work Protocol

For March 2026 defense:

DayDeep Work Focus
MondayLiterature review, synthesis
TuesdayMethodology refinement
WednesdayAnalysis and findings
ThursdayDiscussion and implications
FridayEditing, polishing
WeekendStrategic rest, review

Activation Patterns

TriggerResponse
"deep work", "focus session", "concentration"Full skill activation
"dissertation time", "writing session"Deep Work Mode + defense skill
"distracted", "can't focus"Module 5 + Emergency Recovery
"flow state", "get in the zone"Module 4: Flow Triggers
"time blocking", "schedule deep work"Module 2: Scheduling

References

  • Newport, C. (2016). Deep Work: Rules for Focused Success in a Distracted World
  • Csikszentmihalyi, M. (1990). Flow: The Psychology of Optimal Experience
  • Leroy, S. (2009). Why is it so hard to do my work?
  • Iqbal, S. & Horvitz, E. (2007). Disruption and Recovery of Computing Tasks

Skill created: 2026-02-10 | Category: Productivity | Status: Active


Keep looking

Skills are one crate of 327,069. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.