{"id":"04860764-5158-48cb-a7be-e696c8126387","entityType":"agent","slug":"clawhub-deciqai-deep-work","name":"Deep Work","canonicalUrl":"https://www.xpersona.co/agent/clawhub-deciqai-deep-work","canonicalPath":"/agent/clawhub-deciqai-deep-work","generatedAt":"2026-10-11T08:40:47.831Z","source":"CLAWHUB","claimStatus":"UNCLAIMED","verificationTier":"NONE","summary":{"evidence":{"source":"editorial-content","verified":true,"confidence":"high","updatedAt":"2026-10-11T06:05:37.644Z","emptyReason":null},"description":"Activate when: user says 'I can never find time for focused work', 'I feel busy but produce nothing', 'I keep getting interrupted', 'I want to protect my foc... Skill: Deep Work Owner: deciqai Summary: Activate when: user says 'I can never find time for focused work', 'I feel busy but produce nothing', 'I keep getting interrupted', 'I want to protect my foc... Tags: latest:1.0.5 Version history: v1.0.5 | 2026-07-16T17:57:05.645Z | user Description tail link + agents machine-readable metadata line (deciqai.com/s/deep-work.json) v1.0.4 | 2026-07-10T10:24:46.922Z | user Add 202","descriptionLabel":"Technical summary","evidenceSummary":"Capability contract not published. No trust telemetry is available yet. 1.1K downloads reported by the source. Last updated 10/11/2026.","installCommand":"clawhub skill install s17a4mqcnk515kvaca5ze55d0x88pfpx:deep-work","sourceUrl":"https://clawhub.ai/deciqai/deep-work","homepage":"https://clawhub.ai/deciqai/skills/deep-work","primaryLinks":[{"label":"View on ClawHub","url":"https://clawhub.ai/deciqai/deep-work","kind":"source"},{"label":"Homepage","url":"https://clawhub.ai/deciqai/skills/deep-work","kind":"homepage"}],"safetyScore":84,"overallRank":62,"popularityScore":61,"trustScore":null,"claimedByName":null,"isOwner":false,"seoDescription":"Activate when: user says 'I can never find time for focused work', 'I feel busy but produce nothing', 'I keep getting interrupted', 'I want to protect my foc..."},"coverage":{"evidence":{"source":"public-profile","verified":false,"confidence":"medium","updatedAt":"2026-10-11T06:05:37.644Z","emptyReason":null},"protocols":[{"protocol":"OPENCLEW","label":"OpenClaw","status":"self-declared","notes":"Declared in the public agent profile."}],"capabilities":[],"verifiedCount":0,"selfDeclaredCount":1,"capabilityMatrix":{"rows":[{"key":"OPENCLEW","type":"protocol","support":"unknown","confidenceSource":"profile","notes":"Listed on profile"}],"flattenedTokens":"protocol:OPENCLEW|unknown|profile"}},"adoption":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-11T06:05:37.644Z","emptyReason":null},"stars":null,"forks":null,"downloads":1138,"packageName":null,"latestVersion":"1.0.5","tractionLabel":"1.1K downloads"},"release":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-11T06:05:37.629Z","emptyReason":null},"lastUpdatedAt":"2026-10-11T06:05:37.644Z","lastCrawledAt":"2026-10-11T06:05:37.629Z","lastIndexedAt":null,"nextCrawlAt":"2026-10-12T06:05:37.629Z","lastVerifiedAt":null,"highlights":[{"version":"1.0.5","createdAt":"2026-07-16T17:57:05.645Z","changelog":"Description tail link + agents machine-readable metadata line (deciqai.com/s/deep-work.json)","fileCount":7,"zipByteSize":17449},{"version":"1.0.4","createdAt":"2026-07-10T10:24:46.922Z","changelog":"Add 2024-2026 AI-era worked example + updated sources","fileCount":7,"zipByteSize":17151},{"version":"1.0.3","createdAt":"2026-07-08T10:59:08.826Z","changelog":"Footer now uses /c/<slug> short link (fixes UTM truncation when SKILL.md is read in a terminal)","fileCount":6,"zipByteSize":12587},{"version":"1.0.2","createdAt":"2026-07-08T00:44:03.457Z","changelog":"Refreshed content + GitHub star link in footer","fileCount":6,"zipByteSize":12595},{"version":"1.0.1","createdAt":"2026-07-07T20:31:51.676Z","changelog":"Add catalog categories and topics","fileCount":5,"zipByteSize":9493},{"version":"1.0.0","createdAt":"2026-06-27T07:17:44.232Z","changelog":"Initial publish","fileCount":5,"zipByteSize":9478}]},"execution":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No published capability contract is available yet."},"installCommand":"clawhub skill install s17a4mqcnk515kvaca5ze55d0x88pfpx:deep-work","setupComplexity":"low","setupSteps":["Setup complexity is classified as HIGH. You must provision dedicated cloud infrastructure or an isolated VM. Do not run this directly on your local workstation.","Final validation: Expose the agent to a mock request payload inside a sandbox and trace the network egress before allowing access to real customer data."],"contract":{"contractStatus":"missing","authModes":[],"requires":[],"forbidden":[],"supportsMcp":false,"supportsA2a":false,"supportsStreaming":false,"inputSchemaRef":null,"outputSchemaRef":null,"dataRegion":null,"contractUpdatedAt":null,"sourceUpdatedAt":null,"freshnessSeconds":null},"invocationGuide":{"preferredApi":{"snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-deciqai-deep-work/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-deciqai-deep-work/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-deciqai-deep-work/trust"},"curlExamples":["curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-deciqai-deep-work/snapshot\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-deciqai-deep-work/contract\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-deciqai-deep-work/trust\""],"jsonRequestTemplate":{"query":"summarize this repo","constraints":{"maxLatencyMs":2000,"protocolPreference":["OPENCLEW"]}},"jsonResponseTemplate":{"ok":true,"result":{"summary":"...","confidence":0.9},"meta":{"source":"CLAWHUB","generatedAt":"2026-10-11T08:40:47.824Z"}},"retryPolicy":{"maxAttempts":3,"backoffMs":[500,1500,3500],"retryableConditions":["HTTP_429","HTTP_503","NETWORK_TIMEOUT"]}},"endpoints":{"dossierUrl":"https://www.xpersona.co/api/v1/agents/clawhub-deciqai-deep-work/dossier","snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-deciqai-deep-work/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-deciqai-deep-work/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-deciqai-deep-work/trust"}},"reliability":{"evidence":{"source":"runtime-metrics","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No trust, reliability, or runtime telemetry is available."},"trust":{"status":"unavailable","handshakeStatus":"UNKNOWN","verificationFreshnessHours":null,"reputationScore":null,"p95LatencyMs":null,"successRate30d":null,"fallbackRate":null,"attempts30d":null,"trustUpdatedAt":null,"trustConfidence":"unknown","sourceUpdatedAt":null,"freshnessSeconds":null},"decisionGuardrails":{"doNotUseIf":["Contract metadata is missing or unavailable for deterministic execution."],"safeUseWhen":[],"riskFlags":["missing_or_unavailable_contract","trust_data_unavailable","schema_references_missing"],"operationalConfidence":"low"},"executionMetrics":{"observedLatencyMsP50":null,"observedLatencyMsP95":null,"estimatedCostUsd":null,"uptime30d":null,"rateLimitRpm":null,"rateLimitBurst":null,"lastVerifiedAt":null,"verificationSource":null},"runtimeMetrics":{"successRate":null,"avgLatencyMs":null,"avgCostUsd":null,"hallucinationRate":null,"retryRate":null,"disputeRate":null,"p50Latency":null,"p95Latency":null,"lastUpdated":null}},"benchmarks":{"evidence":{"source":"no-benchmark-data","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No benchmark suites or observed failure patterns are available."},"suites":[],"failurePatterns":[]},"artifacts":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"high","updatedAt":"2026-10-11T06:05:37.644Z","emptyReason":null},"readme":"Skill: Deep Work\n\nOwner: deciqai\n\nSummary: Activate when: user says 'I can never find time for focused work', 'I feel busy but produce nothing', 'I keep getting interrupted', 'I want to protect my foc...\n\nTags: latest:1.0.5\n\nVersion history:\n\nv1.0.5 | 2026-07-16T17:57:05.645Z | user\n\nDescription tail link + agents machine-readable metadata line (deciqai.com/s/deep-work.json)\n\nv1.0.4 | 2026-07-10T10:24:46.922Z | user\n\nAdd 2024-2026 AI-era worked example + updated sources\n\nv1.0.3 | 2026-07-08T10:59:08.826Z | user\n\nFooter now uses /c/<slug> short link (fixes UTM truncation when SKILL.md is read in a terminal)\n\nv1.0.2 | 2026-07-08T00:44:03.457Z | user\n\nRefreshed content + GitHub star link in footer\n\nv1.0.1 | 2026-07-07T20:31:51.676Z | user\n\nAdd catalog categories and topics\n\nv1.0.0 | 2026-06-27T07:17:44.232Z | user\n\nInitial publish\n\nArchive index:\n\nArchive v1.0.5: 7 files, 17449 bytes\n\nFiles: examples/carl-jung-bollingen-tower-retreats.md (5590b), examples/deep-work-amid-ai-copilots-2024-2026.md (8016b), examples/donald-knuth-no-email-policy-1990.md (6441b), references/sources.md (2372b), skill-card.md (3027b), SKILL.md (8081b), _meta.json (128b)\n\nFile v1.0.5:SKILL.md\n\n---\nname: deep-work\ndescription: \"Activate when: user says 'I can never find time for focused work', 'I feel busy but produce nothing', 'I keep getting interrupted', 'I want to protect my focus time', 'flow state', 'deliberate practice', 'Cal Newport', or asks how to make progress on hard cognitive work (research, writing, engineering, strategy). Do NOT activate when: the role is genuinely high-coordination with no discrete focus windows (ER medicine, real-time trading desk), or user is in a short-term emergency where availability must dominate. More: deciqai.com/c/deep-work\"\n---\n\n# Deep Work\n\n## Overview\n\nCal Newport's framework (2016): **deep work** = undistracted, cognitively demanding activity that creates hard-to-replicate value; **shallow work** = logistical, responsive, easy-to-replicate work that fills modern calendars. The most valuable knowledge work is disproportionately the product of deep work; shallow work is increasingly automatable. Three foundations: attention research shows 15-25 min recovery cost per interruption; expert performance requires deliberate practice (structurally a form of deep work); the opportunity cost of shallow work is invisible — no one tracks which deep work didn't happen this week.\n\nComposes with `wu-wei` (flow as the felt experience), `metacognition` (monitoring drift out of deep mode), `okr-goal-setting` (OKRs give deep work direction), `pareto-principle` (the 20% producing 80% of value is almost always deep work).\n\n## When to Use\n\n- Output depends on hard-to-replicate cognitive work (research, engineering, writing, design, strategy)\n- Calendar fragmentation prevents the work that actually matters; weeks feel busy but produce nothing\n- High-stakes project requires extended concentration; career advancement depends on skill development\n- AI copilots / assistants have become another interruption stream (\"is AI helping my focus or fragmenting it?\", \"AI adoption vs deep work\", \"AI hype and staying focused\")\n\n**Not when:** genuinely high-coordination roles where deep work is structurally impossible; already done with deep work and shallow follow-through is now required; short-term emergency where availability dominates.\n\n## Coaching Novices (Adaptive Front Door)\n\n- **Engine mode:** user has a concrete case → run The Process directly.\n- **Coach mode:** user unfamiliar or has no concrete case → guide step by step.\n\nIn Coach mode, respond one step at a time. Each [WAIT] is a hard stop — output only that step's question, then stop.\n\n1. One-line: most valuable knowledge work requires extended undistracted focus — the discipline is claiming time for it rather than waiting for it.\n2. Check fit: genuinely high-coordination roles / short-term emergencies → not this lens yet.\n3. Elicit the specific work that requires depth — what's not getting done?\n> **[WAIT — do not advance until user responds]**\n4. One question at a time: what's your deep-vs-shallow ratio? What's the highest-leverage deep work? What's the cost of not doing it?\n> **[WAIT — do not advance until user responds]**\n5. Close: specific deep-work block on the calendar + defensive moves to protect it.\n> **[WAIT — do not advance until user responds]**\n\n## The Process\n\n**Step 1 — Instrument:** Track one week. Most workers estimate 4-5 hrs/day deep; measurement shows 0.5-2 hrs in fragments.\n```\n- Deep work hours/day (tracked): | Shallow hours/day: | Ratio: | Surprise factor:\n```\n**Step 2 — Identify:** What specific deep work, if done well, produces the most valuable output? Why isn't it happening? What barriers?\n\n**Step 3 — Choose a philosophy:** Monastic (eliminate shallow entirely); Bimodal (alternating deep/shallow periods); Rhythmic (fixed daily block — best default for most); Journalistic (switch in whenever a gap appears — requires strong attention discipline, worst for beginners).\n\n**Step 4 — Build the practice:** Same time + location + setup (ritual). Calendar the block, mark \"Do not interrupt.\" End with a shutdown phrase to prevent cognitive leakage. Boundary is binary: Slack/email closed or you are not in deep work.\n\n**Step 5 — Reduce shallow load:** Audit meetings, email, Slack. Set a shallow-work budget (typically 30-50% for ICs) and stay under it.\n\n**Step 6 — Defend:** Internal — discomfort of being unreachable fades over 2-4 weeks. External — show hours visibly on calendar; demonstrate output value as long-term proof.\n\n## Output: Deep Work Plan\n\n```markdown\n# Deep Work Plan: <person, role>\nDiagnosis — deep hrs/day: | shallow hrs/day: | deep work not happening:\nPhilosophy — selected: | why this fits:\nStructure — block time/duration/location: | ritual: | boundary: | shutdown:\nShallow budget — %: | specific reductions:\nDefense — calendar mark: | comms norms: | output evidence to track:\n```\n\n*→ Method in Action: [Donald Knuth and the No-Email Policy, 1990](examples/donald-knuth-no-email-policy-1990.md) · [Carl Jung's Bollingen Tower Retreats](examples/carl-jung-bollingen-tower-retreats.md)*\n*→ 2026 lens: [Protecting Deep Work Amid AI Copilots (2024–2026)](examples/deep-work-amid-ai-copilots-2024-2026.md)*\n\n## Pack: Deep Work by Role\n\n| Role | Highest-leverage deep work | Common shallow intrusion |\n|---|---|---|\n| Engineer | Architecture, hard debugging | Slack, status meetings |\n| Writer | Drafting, revision | Email, research rabbit holes |\n| Researcher | Literature synthesis, experiments | Grant admin, departmental meetings |\n| Founder | Strategy, customer depth, recruiting | Investor follow-up, feedback meetings |\n| PM | Research synthesis, spec writing | Alignment meetings, status reports |\n\n## Applying It Well\n\nProtect the morning block first — cognitive freshness depletes with shallow work. Track deep-work hours as a lagging metric. Treat the shutdown ritual as non-negotiable. Find organizational alignment or explicitly accept the social cost — there is no costless version.\n\n*→ Primary sources: [references/sources.md](references/sources.md)*\n\n## Common Rationalizations\n\n**[D] = designed upfront | [O] = observed in real use. [O] entries are more valuable.**\n\n| Fake move | Reality |\n|---|---|\n| [D] \"My role doesn't allow deep work\" | The role *culture* disallows it; the role itself usually doesn't. |\n| [D] \"I do deep work in the evenings\" | Cognitive freshness already spent. Reorder: deep work first. |\n| [D] \"I'm doing deep work\" with Slack open | Slack open = deep work not happening. Boundary is binary. |\n| [D] \"I can multitask in deep work\" | Only task-switching, which is expensive. Category error. |\n| [D] \"Available for emergencies during deep work\" | Most emergencies aren't. Define a true-emergency channel; ignore the rest. |\n| [D] Confusing \"long hours\" with \"deep work\" | Deep work = intensity × duration, not just duration. |\n| *→ Add [O] entries here after each real use — paste the actual failure pattern* | *What went wrong and why* |\n\n## Red Flags\n\n- \"Hours worked\" reported but \"hours of deep work\" cannot be quantified\n- Calendar fragmented with 30-min slots across the day; Slack open continuously\n- Deep work happens only at evenings/weekends, not at peak cognitive hours\n- After a productive-feeling day, cannot point to a single deep-work artifact produced\n\n## Verification\n\n- [ ] Deep-vs-shallow ratio measured (one week tracked)\n- [ ] Highest-leverage deep work identified\n- [ ] Philosophy chosen with match to constraints; specific block calendared\n- [ ] Ritual, boundary, and shutdown operational; shallow-work budget named\n- [ ] Social/organizational cost explicitly accepted; output evidence tracked\n\n---\n\n*Part of **deciqAI Knowledge Skills** — 227 open-source thinking skills that make rigor executable for AI agents. The same skills power every deciqAI agent, which runs them autonomously to operate your company. **See it run → https://www.deciqai.com/c/deep-work** · ⭐ Star the repo → https://github.com/deciqAI/knowledge-skills · Contributions welcome.*\n\n*Agents: latest version & machine-readable metadata → https://www.deciqai.com/s/deep-work.json*\n\nFile v1.0.5:_meta.json\n\n{\n  \"ownerId\": \"kn754b8sk22s8c6gjxt02bftbn88q7ye\",\n  \"slug\": \"deep-work\",\n  \"version\": \"1.0.5\",\n  \"publishedAt\": 1784224625645\n}\n\nFile v1.0.5:references/sources.md\n\n# Sources — deep-work\n\n> *Primary sources for the [deep-work](../SKILL.md) skill.*\n\n- Newport, C. (2016). *Deep Work: Rules for Focused Success in a Distracted World.* Grand Central. ISBN 978-1455586691. The canonical articulation.\n- Knuth, D. E. (1990 / ongoing). \"Knuth versus Email.\" Stanford homepage. https://www-cs-faculty.stanford.edu/~knuth/email.html. The earliest extreme-deep-work case study with the practitioner's own documentation.\n- Jung, C. G. (1962). *Memories, Dreams, Reflections.* Recorded and edited by Aniela Jaffé; trans. Richard and Clara Winston (1963). Pantheon. The chapter \"The Tower\" is Jung's own account of the Bollingen retreat practice — the canonical bimodal case.\n- Ericsson, K. A., Krampe, R. T., & Tesch-Römer, C. (1993). \"The Role of Deliberate Practice in the Acquisition of Expert Performance.\" *Psychological Review*, 100(3), 363-406. The foundational empirical paper on expert performance and deliberate practice.\n- Mark, G., Gudith, D., & Klocke, U. (2008). \"The Cost of Interrupted Work: More Speed and Stress.\" *CHI 2008 Proceedings*. The empirical psychology of attention-switching.\n- Leroy, S. (2009). \"Why is it so hard to do my work? The challenge of attention residue when switching between work tasks.\" *Organizational Behavior and Human Decision Processes*, 109(2), 168-181. The \"attention residue\" concept.\n- Csikszentmihalyi, M. (1990). *Flow: The Psychology of Optimal Experience.* Harper & Row. ISBN 978-0061339202. The experiential side of deep work.\n- Newport, C. (2019). *Digital Minimalism: Choosing a Focused Life in a Noisy World.* Portfolio. ISBN 978-0525536512. The companion volume on personal-life dimensions.\n- Carr, N. (2010). *The Shallows: What the Internet Is Doing to Our Brains.* Norton. ISBN 978-0393339758. The cultural diagnosis of why deep work has become rare.\n- GitHub (2022, June 21). \"GitHub Copilot is generally available to all developers.\" https://github.blog/2022-06-21-github-copilot-is-generally-available-to-all-developers/. Marks the mainstreaming of AI copilots in daily knowledge work — the 2024–2026 context for the deep/shallow distinction.\n- Newport, C. (2024–2025). *Deep Questions* podcast and essays on AI and knowledge work. https://calnewport.com. Newport's contemporary argument that undistracted human cognition rises in value as routine output is automated.\n\nFile v1.0.5:examples/carl-jung-bollingen-tower-retreats.md\n\n# Method in Action: Carl Jung's Bollingen Tower Retreats (1923–1961)\n\n> *Example for the [deep-work](../SKILL.md) skill.*\n\nCarl Jung's Bollingen tower is the case Cal Newport chose to open *Deep Work* (2016), and it remains the cleanest historical demonstration of the **Bimodal philosophy**: a working psychiatrist who could not abandon his shallow obligations, and instead built a physical architecture for alternating between them and depth.\n\n**The diagnosis (Steps 1-2):** In the 1920s Jung's professional life in Zurich and Küsnacht was structurally shallow-saturated: a busy clinical practice with a full patient load, lectures, seminars, and heavy correspondence. This was also the period in which Jung was establishing analytical psychology as an independent school after his break with Freud — an intellectual project competing against the most formidable rival imaginable. The highest-leverage deep work was unambiguous: the sustained theoretical writing that would define archetypes, the collective unconscious, and individuation. That writing could not happen between patient sessions. Jung did not need a tracking week to see the ratio; the clinical calendar made it visible.\n\n**The philosophy choice (Step 3):** Jung could not go monastic — his clinical practice was both his income and his empirical material. He chose the bimodal split: full engagement with practice and public life in Zurich, then regular retreats to a private refuge for concentrated writing.\n\n**The practice (Step 4):** In 1922 Jung bought land at Bollingen on the upper lake of Zurich, and beginning in 1923 built a stone tower there by stages, expanding it over the following decades. The tower was deliberately spartan — no electricity; Jung chopped his own wood, drew his own water, and lit oil lamps. In *Memories, Dreams, Reflections* (1962), the chapter \"The Tower\" describes the place in Jung's own account as a site of repose and renewal where he felt most deeply himself — a purpose-built container for concentration. Newport reconstructs the working rhythm: mornings locked in a private study for undisturbed writing, afternoons given to meditation and walks, early nights. Same location, same setup, hard boundary — the full ritual structure of Step 4, implemented in stone.\n\n**Shallow reduction and defense (Steps 5-6):** Every Bollingen period was clinical income refused and patients turned away — the shallow-work budget enforced at direct financial cost. The retreats could look like withdrawal from a career; they were its engine. The output produced across four decades of this regime — the essays and books that became the *Collected Works* and established analytical psychology as a lasting school — is the long-term evidence Step 6 says to accumulate: output value as the defense of the practice.\n\nThe structural lesson mirrors Knuth's but from the opposite pole: Knuth shows the monastic extreme (eliminate the shallow channel permanently); Jung shows that a practitioner who *cannot* eliminate shallow work can still get monastic-grade depth by alternating modes — provided the deep mode has a hard physical and temporal boundary, a ritual, and an accepted cost.\n\nThree operational lessons from the Bollingen case:\n\n**First, bimodal beats waiting.** Jung never had a calendar that \"allowed\" deep work; he manufactured the allowance by pre-committing whole blocks of days. Anyone whose role genuinely requires shallow engagement — clinicians, managers, founders — should read Jung, not Knuth, as the applicable template: claim retreat units (a day, a week) rather than trying to carve depth out of an interrupt-driven day.\n\n**Second, the environment does defensive work the willpower budget cannot.** A tower with no electricity, reachable only by deliberate travel, made shallow intrusion physically impossible rather than merely discouraged. The modern equivalent is weaker but real: a separate room, a machine with no messaging clients, a location where interruption cannot follow. Build the boundary into the environment so it does not have to be re-decided hourly.\n\n**Third, deep work was not competing against the practice — it fed it.** Jung's clinical work supplied the case material his theoretical writing systematized, and the writing in turn made the practice world-famous. The bimodal split is not a tax paid by the shallow mode; run well, each mode compounds the other. That is the strongest answer to the \"my role doesn't allow it\" rationalization.\n\nThe mapped steps:\n1. Instrument: Zurich clinical calendar made the deep/shallow ratio visible — practice, lectures, correspondence consumed the day\n2. Identify: the theoretical corpus of analytical psychology, in direct competition with Freud, was the highest-leverage deep work not happening\n3. Philosophy: Bimodal — full shallow engagement in Zurich alternating with retreat periods at Bollingen\n4. Practice: the stone tower as ritual — fixed location, spartan setup, locked morning study, afternoon walks, early nights\n5. Shallow budget: patients refused and engagements declined during retreat periods, at real financial cost\n6. Defense: decades of published output — the *Collected Works* — as the standing proof that the protected time paid\n\nPrimary source: Jung, C. G. (1962). *Memories, Dreams, Reflections.* Recorded and edited by Aniela Jaffé; trans. Richard and Clara Winston (1963). Pantheon. Chapter \"The Tower.\" Secondary: Newport, C. (2016). *Deep Work: Rules for Focused Success in a Distracted World.* Grand Central. Chapter 1 and Rule #1 (Bimodal philosophy).\n\nFile v1.0.5:examples/deep-work-amid-ai-copilots-2024-2026.md\n\n# Method in Action: Protecting Deep Work Amid AI Copilots (2024–2026)\n\n> *Example for the [deep-work](../SKILL.md) skill.*\n\nBetween 2022 and 2026, generative-AI copilots moved from novelty to default fixture of knowledge work. GitHub Copilot became generally available in June 2022; ChatGPT launched in November 2022; and by 2024–2025 assistants were embedded directly into the tools where work happens — IDEs (Copilot, Cursor), office suites (Microsoft 365 Copilot, Google's Gemini in Workspace), and communication tools. The promise was more focus. The lived experience for many knowledge workers was the opposite: **another always-on stream demanding attention** — suggestions to accept or reject, chat panels to consult, notifications, and a new social pressure to \"use the AI.\" This example runs a composite knowledge worker — a senior software engineer, call her Maya — through the deep-work Process to decide how AI should relate to her focus rather than fragment it.\n\nThe core tension is exactly the deep/shallow distinction Newport drew in 2016, now with a new actor. An AI copilot can serve deep work (as a tool inside a protected block) or become shallow work (another interruption stream, another inbox). The framework's job is to keep it the former.\n\n**Step 1 — Instrument.** Maya tracks one week. Her estimate before tracking: \"maybe 4 hours a day of real focused coding.\" The tracked reality: roughly 1–1.5 hours of genuinely uninterrupted deep work per day, scattered in fragments. The new finding specific to 2024–2026: a meaningful share of her fragmentation now comes from *AI-adjacent* micro-switches — pausing mid-thought to prompt a chatbot, context-switching to read and evaluate a generated suggestion, and tab-hopping between editor and assistant. The copilot did not remove interruptions; it added a self-inflicted one that feels productive. This matches the widely-reported pattern in industry research on developer experience: perceived productivity gains from AI tools coexist with fragmented attention, and the recovery cost of task-switching (the 2008 Mark et al. and 2009 Leroy attention-residue findings) does not disappear just because the interruption is a helpful one.\n\n```\n- Deep work hours/day (tracked): ~1.25 | Shallow hours/day: ~5 | Ratio: poor\n- Surprise factor: high — AI prompting felt like focus but registered as switching\n```\n\n**Step 2 — Identify.** The highest-leverage deep work is the hard, hard-to-replicate cognitive work: system design, reasoning about a subtle concurrency bug, and the architectural decisions that shape months of downstream code. This is precisely the class of work that current AI models assist *least* well — they accelerate boilerplate, recall, and first-draft scaffolding, but the load-bearing judgment (what to build, why, and what breaks at scale) still resists being outsourced. Why isn't the deep work happening? Because the day is saturated with shallow work — and now the copilot, if used reflexively, invites her to *stay in* a shallow, reactive loop (accept/reject, re-prompt) instead of holding a hard problem in her head.\n\n**Step 3 — Choose a philosophy.** Maya's role is collaborative but has discrete focus windows, so the **Rhythmic** philosophy fits: a fixed daily deep-work block (the SKILL's recommended default for most). She adds a rule specific to the AI era: the copilot is *scoped by mode*, not banned. In the deep block, AI is allowed only as a pull tool she invokes deliberately for a bounded sub-task (e.g., \"generate the test fixtures so I don't leave flow to write boilerplate\"), never as an ambient chat she monitors. Outside the block, AI-assisted drafting and batching are welcome.\n\n**Step 4 — Build the practice.** Same time (morning, peak cognitive freshness), same location, same setup. She calendars a 90-minute block marked \"Do not interrupt,\" and closes Slack and email — the boundary is binary. The AI-specific move: **turn off ambient/automatic AI features during the block** (inline autosuggestions that interrupt her own line of reasoning, background chat notifications) while keeping the ability to *summon* the assistant on demand for a defined offload. The distinction is control: AI as a tool she reaches for, not a stream that reaches for her. She ends with a shutdown phrase to prevent cognitive leakage.\n\n**Step 5 — Reduce shallow load.** Maya audits meetings, email, and Slack, and adds an AI-native tactic: **use AI to compress shallow work rather than expand it.** She batches low-stakes correspondence and lets the assistant draft first passes of status updates, routine PR descriptions, and meeting summaries — collapsing an hour of shallow work into fifteen minutes, which *buys back* time for the deep block. This is the constructive use of the tool: AI applied to the shallow layer (its comparative advantage) to protect the deep layer (where it is weakest). She sets a shallow-work budget and stays under it.\n\n**Step 6 — Defend.** *Internal:* the discomfort of not reflexively reaching for the AI on every problem — of sitting with a hard problem unaided — fades over a few weeks, the same adaptation curve as going unreachable. Resisting the copilot for the load-bearing thinking is itself the deliberate practice that keeps her skill from atrophying; over-reliance risks deskilling on exactly the judgment that makes her valuable. *External:* she shows the deep block on her calendar and lets output — shipped architecture, hard bugs closed — stand as the long-term proof. She frames AI adoption to her team honestly: the tool multiplies her shallow-work throughput and drafts, but the hard cognitive work is still done by a focused human, and protecting that focus is what makes the AI worth having.\n\nThe mapped steps:\n1. Instrument: tracked week showed ~1.25 deep hrs/day; AI prompting was a hidden source of self-inflicted fragmentation\n2. Identify: system design and subtle debugging — the work AI assists least — as the highest-leverage deep work being crowded out\n3. Philosophy: Rhythmic daily block, with AI scoped by mode (deliberate pull-tool inside the block, not ambient stream)\n4. Practice: morning 90-min block, binary boundary, ambient AI features off but on-demand summon allowed, shutdown ritual\n5. Shallow budget: AI used to compress shallow work (drafts, summaries, boilerplate) to buy back deep-work time\n6. Defense: calendar visibility plus shipped output; internal defense against deskilling by keeping hard judgment human\n\n**The 2026 lesson.** The arrival of capable AI copilots does not repeal the deep/shallow distinction — it sharpens it. The tools are genuinely good at shallow work and first drafts, and genuinely limited at the extended, hard-to-replicate reasoning that deep work exists to produce. The failure mode is treating the copilot as a third inbox to monitor; the winning move is treating it as a tool you invoke to *shrink* the shallow layer, so the deep layer survives. As Newport himself argued through 2024–2025 in his writing and podcast on AI and productivity, the value of undistracted human cognition rises, not falls, as routine output becomes cheap to automate.\n\n*Sources: Newport, C. (2016). Deep Work: Rules for Focused Success in a Distracted World. Grand Central. · Mark, G., Gudith, D., & Klocke, U. (2008). \"The Cost of Interrupted Work: More Speed and Stress.\" CHI 2008 Proceedings. · Leroy, S. (2009). \"Why is it so hard to do my work? The challenge of attention residue when switching between work tasks.\" Organizational Behavior and Human Decision Processes, 109(2), 168-181. · GitHub. \"GitHub Copilot is generally available to all developers\" (announcement, June 21, 2022), https://github.blog/2022-06-21-github-copilot-is-generally-available-to-all-developers/. · OpenAI. \"Introducing ChatGPT\" (November 30, 2022), https://openai.com/blog/chatgpt. · Newport, C. Deep Questions podcast and essays on AI and knowledge work (2024–2025), https://calnewport.com.*\n\nFile v1.0.5:examples/donald-knuth-no-email-policy-1990.md\n\n# Method in Action: Donald Knuth and the No-Email Policy, 1990\n\n> *Example for the [deep-work](../SKILL.md) skill.*\n\nThe most extreme and well-documented case of deep-work practice in modern science is **Donald Knuth**, Professor Emeritus of Computer Science at Stanford and author of *The Art of Computer Programming* (TAOCP), the multi-volume work he has been writing since 1962 and which Bill Gates once called \"the best book on programming ever written.\"\n\nKnuth's challenge: TAOCP requires sustained, cognitively-intensive mathematical and programming work that does not yield to fragmentation. The work also requires Knuth to maintain mathematical correctness across a corpus that, by 2025, runs to several thousand published pages. In the 1980s, as email began to dominate academic life, Knuth observed that his TAOCP progress was slowing — and traced the slowdown to email's compounding effect on his attention.\n\nIn **January 1, 1990**, Knuth announced on his Stanford homepage that he was discontinuing email use. The statement (preserved at https://www-cs-faculty.stanford.edu/~knuth/email.html and unchanged in substance for 35 years) reads:\n\n> \"I have been a happy man ever since January 1, 1990, when I no longer had an email address. I'd used email since about 1975, and it seems to me that 15 years of email is plenty for one lifetime.\n>\n> Email is a wonderful thing for people whose role in life is to be on top of things. But not for me; my role is to be on the bottom of things. What I do takes long hours of studying and uninterruptible concentration. I try to learn certain areas of computer science exhaustively; then I try to digest that knowledge into a form that is accessible to people who don't have time for such study.\"\n\n— Knuth, D. E. (1990 / continuously updated). \"Knuth versus Email.\" Stanford homepage. https://www-cs-faculty.stanford.edu/~knuth/email.html\n\nThe substantive structure of Knuth's argument is precisely the Newport deep/shallow distinction (anticipating Newport's 2016 book by 26 years):\n\n- **\"To be on top of things\"** = the shallow-work mode of constant responsiveness, awareness, coordination\n- **\"To be on the bottom of things\"** = the deep-work mode of sustained, uninterruptible concentration\n- **The trade-off is structural:** Knuth claims you cannot do both. The roles require incompatible cognitive modes.\n\nKnuth's policy is not absence of communication — postal mail still reaches him, and his assistant handles correspondence. The policy is specifically refusal of the *interruption-pattern* email demands, on the grounds that the cost (to deep work) exceeds the value (of any individual email).\n\nThe empirical evidence from Knuth's output: between 1990 and 2025, while running this policy and *also* fully retiring from teaching in 1992, Knuth produced TAOCP Volume 4A (2011), 4B (2022), 4C (in progress), and other works — output that would be remarkable for any full-time professor, let alone an \"emeritus.\" His policy is not eccentric; it is the operational architecture that enables the output.\n\n**Newport's 2016 articulation** generalizes Knuth's insight beyond the specific case. The four philosophies, the shallow-work budget, the rituals — all describe operational implementations of the same deep/shallow trade-off Knuth made formal in 1990.\n\nNewport quotes the cognitive scientist **K. Anders Ericsson**, the originator of the modern theory of expert performance:\n\n> \"Deliberate practice is a highly structured activity, the explicit goal of which is to improve performance. Specific tasks are invented to overcome weaknesses, and performance is carefully monitored to provide cues for ways to improve it further.\"\n>\n> — Ericsson, K. A., Krampe, R. T., & Tesch-Römer, C. (1993). \"The Role of Deliberate Practice in the Acquisition of Expert Performance.\" *Psychological Review*, 100(3), 363-406. p. 368.\n\nNewport draws the connection: deliberate practice is structurally deep work. The expert performers Ericsson studied did not get expert by working more hours; they got expert by doing more *deliberately structured, distraction-free, edge-of-ability* work. The empirical fact that elite performers across domains (musicians, athletes, chess players, programmers, surgeons) all show this pattern is the cognitive-science foundation for deep work.\n\nMark, Gudith & Klocke's empirical study at UC Irvine (2008) added the attention-fragmentation data:\n\n> \"After only 20 minutes of interrupted performance people reported significantly higher stress, frustration, workload, effort, and pressure. We compared self-reports of stress and other affective responses with measures of physiological response. Our results suggest that to compensate for interruptions, people work faster, but this comes at a price: experiencing more stress, higher frustration, time pressure and effort.\"\n>\n> — Mark, G., Gudith, D., & Klocke, U. (2008). \"The Cost of Interrupted Work: More Speed and Stress.\" *Proceedings of the SIGCHI Conference on Human Factors in Computing Systems*, 107-110.\n\nThe combined picture: deep work produces the most valuable knowledge-work output; expert performance requires it; interruption fragments it; and most modern work environments are structurally interruption-saturated. The Newport / Knuth response is structural protection of deep-work time.\n\nThree operational lessons from Knuth's case and Newport's framework:\n\n**First, the cost of shallow work is real but invisible.** Knuth could have kept doing email, and TAOCP would have progressed more slowly, and no one would have noticed which specific volume was delayed. The cost of *not* protecting deep work is paid by the long-term output, not the short-term calendar. This invisibility is what makes the trade-off so frequently lost.\n\n**Second, the social cost is real and must be paid.** Knuth's policy is rude by modern standards. People who write him reasonable, polite emails do not get replies. The framework requires accepting that some social and professional cost is the price of the protected output. There is no costless version.\n\n**Third, the discipline scales down.** Most people cannot, and should not, adopt Knuth's monastic posture. But the same logic — protect specific blocks, accept structural shallow-work reduction, defend the boundary — scales down to 2-4 hours per day of protected deep work, which is enough to dramatically shift output for most knowledge workers.\n\nFile v1.0.5:skill-card.md\n\n## Description:\n\nDeep Work helps agents coach users through protecting focused cognitive work, measuring deep-versus-shallow work, selecting an appropriate deep-work philosophy, and producing a practical Deep Work Plan.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[deciqai](https://clawhub.ai/user/deciqai)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nEmployees, external users, and developers use this skill when focused knowledge work is being crowded out by interruptions, shallow work, AI copilots, or fragmented calendars. The skill guides a coaching flow that identifies the valuable deep work, protects time for it, sets boundaries, and returns a concise Deep Work Plan.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: The skill can encourage recording observed focus failure patterns, which may include personal, workplace, or sensitive details if copied directly into notes.\n\nMitigation: Avoid storing sensitive details unless intentionally retained; summarize patterns generically and remove names, confidential project details, and private workplace information.\n\nRisk: Deep-work advice can be misapplied in high-coordination roles or short-term emergencies where availability should dominate.\n\nMitigation: Use the skill's fit check before coaching and defer the deep-work lens when the user needs real-time coordination or emergency responsiveness.\n\n## Reference(s):\n\n- [ClawHub Deep Work skill page](https://clawhub.ai/deciqai/skills/deep-work)\n- [deciqAI Deep Work page](https://www.deciqai.com/c/deep-work)\n- [Deep Work machine-readable metadata](https://www.deciqai.com/s/deep-work.json)\n- [Sources - deep-work](references/sources.md)\n- [Donald Knuth and the No-Email Policy, 1990](examples/donald-knuth-no-email-policy-1990.md)\n- [Carl Jung's Bollingen Tower Retreats](examples/carl-jung-bollingen-tower-retreats.md)\n- [Protecting Deep Work Amid AI Copilots (2024-2026)](examples/deep-work-amid-ai-copilots-2024-2026.md)\n- [deciqAI knowledge-skills repository](https://github.com/deciqAI/knowledge-skills)\n- [Knuth versus Email](https://www-cs-faculty.stanford.edu/~knuth/email.html)\n- [GitHub Copilot is generally available to all developers](https://github.blog/2022-06-21-github-copilot-is-generally-available-to-all-developers/)\n- [Cal Newport](https://calnewport.com)\n\n## Skill Output:\n\n**Output Type(s):** [text, markdown, guidance]\n\n**Output Format:** [Markdown coaching questions and a Deep Work Plan template]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Coach mode uses explicit wait points before advancing; engine mode produces a concise plan from the user's concrete case.]\n\n## Skill Version(s):\n\n1.0.5 (source: server release metadata)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.\n\nArchive v1.0.4: 7 files, 17151 bytes\n\nFiles: examples/carl-jung-bollingen-tower-retreats.md (5590b), examples/deep-work-amid-ai-copilots-2024-2026.md (8016b), examples/donald-knuth-no-email-policy-1990.md (6441b), references/sources.md (2372b), skill-card.md (2490b), SKILL.md (7952b), _meta.json (128b)\n\nFile v1.0.4:SKILL.md\n\n---\nname: deep-work\ndescription: \"Activate when: user says 'I can never find time for focused work', 'I feel busy but produce nothing', 'I keep getting interrupted', 'I want to protect my focus time', 'flow state', 'deliberate practice', 'Cal Newport', or asks how to make progress on hard cognitive work (research, writing, engineering, strategy). Do NOT activate when: the role is genuinely high-coordination with no discrete focus windows (ER medicine, real-time trading desk), or user is in a short-term emergency where availability must dominate.\"\n---\n\n# Deep Work\n\n## Overview\n\nCal Newport's framework (2016): **deep work** = undistracted, cognitively demanding activity that creates hard-to-replicate value; **shallow work** = logistical, responsive, easy-to-replicate work that fills modern calendars. The most valuable knowledge work is disproportionately the product of deep work; shallow work is increasingly automatable. Three foundations: attention research shows 15-25 min recovery cost per interruption; expert performance requires deliberate practice (structurally a form of deep work); the opportunity cost of shallow work is invisible — no one tracks which deep work didn't happen this week.\n\nComposes with `wu-wei` (flow as the felt experience), `metacognition` (monitoring drift out of deep mode), `okr-goal-setting` (OKRs give deep work direction), `pareto-principle` (the 20% producing 80% of value is almost always deep work).\n\n## When to Use\n\n- Output depends on hard-to-replicate cognitive work (research, engineering, writing, design, strategy)\n- Calendar fragmentation prevents the work that actually matters; weeks feel busy but produce nothing\n- High-stakes project requires extended concentration; career advancement depends on skill development\n- AI copilots / assistants have become another interruption stream (\"is AI helping my focus or fragmenting it?\", \"AI adoption vs deep work\", \"AI hype and staying focused\")\n\n**Not when:** genuinely high-coordination roles where deep work is structurally impossible; already done with deep work and shallow follow-through is now required; short-term emergency where availability dominates.\n\n## Coaching Novices (Adaptive Front Door)\n\n- **Engine mode:** user has a concrete case → run The Process directly.\n- **Coach mode:** user unfamiliar or has no concrete case → guide step by step.\n\nIn Coach mode, respond one step at a time. Each [WAIT] is a hard stop — output only that step's question, then stop.\n\n1. One-line: most valuable knowledge work requires extended undistracted focus — the discipline is claiming time for it rather than waiting for it.\n2. Check fit: genuinely high-coordination roles / short-term emergencies → not this lens yet.\n3. Elicit the specific work that requires depth — what's not getting done?\n> **[WAIT — do not advance until user responds]**\n4. One question at a time: what's your deep-vs-shallow ratio? What's the highest-leverage deep work? What's the cost of not doing it?\n> **[WAIT — do not advance until user responds]**\n5. Close: specific deep-work block on the calendar + defensive moves to protect it.\n> **[WAIT — do not advance until user responds]**\n\n## The Process\n\n**Step 1 — Instrument:** Track one week. Most workers estimate 4-5 hrs/day deep; measurement shows 0.5-2 hrs in fragments.\n```\n- Deep work hours/day (tracked): | Shallow hours/day: | Ratio: | Surprise factor:\n```\n**Step 2 — Identify:** What specific deep work, if done well, produces the most valuable output? Why isn't it happening? What barriers?\n\n**Step 3 — Choose a philosophy:** Monastic (eliminate shallow entirely); Bimodal (alternating deep/shallow periods); Rhythmic (fixed daily block — best default for most); Journalistic (switch in whenever a gap appears — requires strong attention discipline, worst for beginners).\n\n**Step 4 — Build the practice:** Same time + location + setup (ritual). Calendar the block, mark \"Do not interrupt.\" End with a shutdown phrase to prevent cognitive leakage. Boundary is binary: Slack/email closed or you are not in deep work.\n\n**Step 5 — Reduce shallow load:** Audit meetings, email, Slack. Set a shallow-work budget (typically 30-50% for ICs) and stay under it.\n\n**Step 6 — Defend:** Internal — discomfort of being unreachable fades over 2-4 weeks. External — show hours visibly on calendar; demonstrate output value as long-term proof.\n\n## Output: Deep Work Plan\n\n```markdown\n# Deep Work Plan: <person, role>\nDiagnosis — deep hrs/day: | shallow hrs/day: | deep work not happening:\nPhilosophy — selected: | why this fits:\nStructure — block time/duration/location: | ritual: | boundary: | shutdown:\nShallow budget — %: | specific reductions:\nDefense — calendar mark: | comms norms: | output evidence to track:\n```\n\n*→ Method in Action: [Donald Knuth and the No-Email Policy, 1990](examples/donald-knuth-no-email-policy-1990.md) · [Carl Jung's Bollingen Tower Retreats](examples/carl-jung-bollingen-tower-retreats.md)*\n*→ 2026 lens: [Protecting Deep Work Amid AI Copilots (2024–2026)](examples/deep-work-amid-ai-copilots-2024-2026.md)*\n\n## Pack: Deep Work by Role\n\n| Role | Highest-leverage deep work | Common shallow intrusion |\n|---|---|---|\n| Engineer | Architecture, hard debugging | Slack, status meetings |\n| Writer | Drafting, revision | Email, research rabbit holes |\n| Researcher | Literature synthesis, experiments | Grant admin, departmental meetings |\n| Founder | Strategy, customer depth, recruiting | Investor follow-up, feedback meetings |\n| PM | Research synthesis, spec writing | Alignment meetings, status reports |\n\n## Applying It Well\n\nProtect the morning block first — cognitive freshness depletes with shallow work. Track deep-work hours as a lagging metric. Treat the shutdown ritual as non-negotiable. Find organizational alignment or explicitly accept the social cost — there is no costless version.\n\n*→ Primary sources: [references/sources.md](references/sources.md)*\n\n## Common Rationalizations\n\n**[D] = designed upfront | [O] = observed in real use. [O] entries are more valuable.**\n\n| Fake move | Reality |\n|---|---|\n| [D] \"My role doesn't allow deep work\" | The role *culture* disallows it; the role itself usually doesn't. |\n| [D] \"I do deep work in the evenings\" | Cognitive freshness already spent. Reorder: deep work first. |\n| [D] \"I'm doing deep work\" with Slack open | Slack open = deep work not happening. Boundary is binary. |\n| [D] \"I can multitask in deep work\" | Only task-switching, which is expensive. Category error. |\n| [D] \"Available for emergencies during deep work\" | Most emergencies aren't. Define a true-emergency channel; ignore the rest. |\n| [D] Confusing \"long hours\" with \"deep work\" | Deep work = intensity × duration, not just duration. |\n| *→ Add [O] entries here after each real use — paste the actual failure pattern* | *What went wrong and why* |\n\n## Red Flags\n\n- \"Hours worked\" reported but \"hours of deep work\" cannot be quantified\n- Calendar fragmented with 30-min slots across the day; Slack open continuously\n- Deep work happens only at evenings/weekends, not at peak cognitive hours\n- After a productive-feeling day, cannot point to a single deep-work artifact produced\n\n## Verification\n\n- [ ] Deep-vs-shallow ratio measured (one week tracked)\n- [ ] Highest-leverage deep work identified\n- [ ] Philosophy chosen with match to constraints; specific block calendared\n- [ ] Ritual, boundary, and shutdown operational; shallow-work budget named\n- [ ] Social/organizational cost explicitly accepted; output evidence tracked\n\n---\n\n*Part of **deciqAI Knowledge Skills** — 223 open-source thinking skills that make rigor executable for AI agents. The same skills power every deciqAI agent, which runs them autonomously to operate your company. **See it run → https://www.deciqai.com/c/deep-work** · ⭐ Star the repo → https://github.com/deciqAI/knowledge-skills · Contributions welcome.*\n\nFile v1.0.4:_meta.json\n\n{\n  \"ownerId\": \"kn754b8sk22s8c6gjxt02bftbn88q7ye\",\n  \"slug\": \"deep-work\",\n  \"version\": \"1.0.4\",\n  \"publishedAt\": 1783679086922\n}\n\nFile v1.0.4:references/sources.md\n\n# Sources — deep-work\n\n> *Primary sources for the [deep-work](../SKILL.md) skill.*\n\n- Newport, C. (2016). *Deep Work: Rules for Focused Success in a Distracted World.* Grand Central. ISBN 978-1455586691. The canonical articulation.\n- Knuth, D. E. (1990 / ongoing). \"Knuth versus Email.\" Stanford homepage. https://www-cs-faculty.stanford.edu/~knuth/email.html. The earliest extreme-deep-work case study with the practitioner's own documentation.\n- Jung, C. G. (1962). *Memories, Dreams, Reflections.* Recorded and edited by Aniela Jaffé; trans. Richard and Clara Winston (1963). Pantheon. The chapter \"The Tower\" is Jung's own account of the Bollingen retreat practice — the canonical bimodal case.\n- Ericsson, K. A., Krampe, R. T., & Tesch-Römer, C. (1993). \"The Role of Deliberate Practice in the Acquisition of Expert Performance.\" *Psychological Review*, 100(3), 363-406. The foundational empirical paper on expert performance and deliberate practice.\n- Mark, G., Gudith, D., & Klocke, U. (2008). \"The Cost of Interrupted Work: More Speed and Stress.\" *CHI 2008 Proceedings*. The empirical psychology of attention-switching.\n- Leroy, S. (2009). \"Why is it so hard to do my work? The challenge of attention residue when switching between work tasks.\" *Organizational Behavior and Human Decision Processes*, 109(2), 168-181. The \"attention residue\" concept.\n- Csikszentmihalyi, M. (1990). *Flow: The Psychology of Optimal Experience.* Harper & Row. ISBN 978-0061339202. The experiential side of deep work.\n- Newport, C. (2019). *Digital Minimalism: Choosing a Focused Life in a Noisy World.* Portfolio. ISBN 978-0525536512. The companion volume on personal-life dimensions.\n- Carr, N. (2010). *The Shallows: What the Internet Is Doing to Our Brains.* Norton. ISBN 978-0393339758. The cultural diagnosis of why deep work has become rare.\n- GitHub (2022, June 21). \"GitHub Copilot is generally available to all developers.\" https://github.blog/2022-06-21-github-copilot-is-generally-available-to-all-developers/. Marks the mainstreaming of AI copilots in daily knowledge work — the 2024–2026 context for the deep/shallow distinction.\n- Newport, C. (2024–2025). *Deep Questions* podcast and essays on AI and knowledge work. https://calnewport.com. Newport's contemporary argument that undistracted human cognition rises in value as routine output is automated.\n\nFile v1.0.4:examples/carl-jung-bollingen-tower-retreats.md\n\n# Method in Action: Carl Jung's Bollingen Tower Retreats (1923–1961)\n\n> *Example for the [deep-work](../SKILL.md) skill.*\n\nCarl Jung's Bollingen tower is the case Cal Newport chose to open *Deep Work* (2016), and it remains the cleanest historical demonstration of the **Bimodal philosophy**: a working psychiatrist who could not abandon his shallow obligations, and instead built a physical architecture for alternating between them and depth.\n\n**The diagnosis (Steps 1-2):** In the 1920s Jung's professional life in Zurich and Küsnacht was structurally shallow-saturated: a busy clinical practice with a full patient load, lectures, seminars, and heavy correspondence. This was also the period in which Jung was establishing analytical psychology as an independent school after his break with Freud — an intellectual project competing against the most formidable rival imaginable. The highest-leverage deep work was unambiguous: the sustained theoretical writing that would define archetypes, the collective unconscious, and individuation. That writing could not happen between patient sessions. Jung did not need a tracking week to see the ratio; the clinical calendar made it visible.\n\n**The philosophy choice (Step 3):** Jung could not go monastic — his clinical practice was both his income and his empirical material. He chose the bimodal split: full engagement with practice and public life in Zurich, then regular retreats to a private refuge for concentrated writing.\n\n**The practice (Step 4):** In 1922 Jung bought land at Bollingen on the upper lake of Zurich, and beginning in 1923 built a stone tower there by stages, expanding it over the following decades. The tower was deliberately spartan — no electricity; Jung chopped his own wood, drew his own water, and lit oil lamps. In *Memories, Dreams, Reflections* (1962), the chapter \"The Tower\" describes the place in Jung's own account as a site of repose and renewal where he felt most deeply himself — a purpose-built container for concentration. Newport reconstructs the working rhythm: mornings locked in a private study for undisturbed writing, afternoons given to meditation and walks, early nights. Same location, same setup, hard boundary — the full ritual structure of Step 4, implemented in stone.\n\n**Shallow reduction and defense (Steps 5-6):** Every Bollingen period was clinical income refused and patients turned away — the shallow-work budget enforced at direct financial cost. The retreats could look like withdrawal from a career; they were its engine. The output produced across four decades of this regime — the essays and books that became the *Collected Works* and established analytical psychology as a lasting school — is the long-term evidence Step 6 says to accumulate: output value as the defense of the practice.\n\nThe structural lesson mirrors Knuth's but from the opposite pole: Knuth shows the monastic extreme (eliminate the shallow channel permanently); Jung shows that a practitioner who *cannot* eliminate shallow work can still get monastic-grade depth by alternating modes — provided the deep mode has a hard physical and temporal boundary, a ritual, and an accepted cost.\n\nThree operational lessons from the Bollingen case:\n\n**First, bimodal beats waiting.** Jung never had a calendar that \"allowed\" deep work; he manufactured the allowance by pre-committing whole blocks of days. Anyone whose role genuinely requires shallow engagement — clinicians, managers, founders — should read Jung, not Knuth, as the applicable template: claim retreat units (a day, a week) rather than trying to carve depth out of an interrupt-driven day.\n\n**Second, the environment does defensive work the willpower budget cannot.** A tower with no electricity, reachable only by deliberate travel, made shallow intrusion physically impossible rather than merely discouraged. The modern equivalent is weaker but real: a separate room, a machine with no messaging clients, a location where interruption cannot follow. Build the boundary into the environment so it does not have to be re-decided hourly.\n\n**Third, deep work was not competing against the practice — it fed it.** Jung's clinical work supplied the case material his theoretical writing systematized, and the writing in turn made the practice world-famous. The bimodal split is not a tax paid by the shallow mode; run well, each mode compounds the other. That is the strongest answer to the \"my role doesn't allow it\" rationalization.\n\nThe mapped steps:\n1. Instrument: Zurich clinical calendar made the deep/shallow ratio visible — practice, lectures, correspondence consumed the day\n2. Identify: the theoretical corpus of analytical psychology, in direct competition with Freud, was the highest-leverage deep work not happening\n3. Philosophy: Bimodal — full shallow engagement in Zurich alternating with retreat periods at Bollingen\n4. Practice: the stone tower as ritual — fixed location, spartan setup, locked morning study, afternoon walks, early nights\n5. Shallow budget: patients refused and engagements declined during retreat periods, at real financial cost\n6. Defense: decades of published output — the *Collected Works* — as the standing proof that the protected time paid\n\nPrimary source: Jung, C. G. (1962). *Memories, Dreams, Reflections.* Recorded and edited by Aniela Jaffé; trans. Richard and Clara Winston (1963). Pantheon. Chapter \"The Tower.\" Secondary: Newport, C. (2016). *Deep Work: Rules for Focused Success in a Distracted World.* Grand Central. Chapter 1 and Rule #1 (Bimodal philosophy).\n\nFile v1.0.4:examples/deep-work-amid-ai-copilots-2024-2026.md\n\n# Method in Action: Protecting Deep Work Amid AI Copilots (2024–2026)\n\n> *Example for the [deep-work](../SKILL.md) skill.*\n\nBetween 2022 and 2026, generative-AI copilots moved from novelty to default fixture of knowledge work. GitHub Copilot became generally available in June 2022; ChatGPT launched in November 2022; and by 2024–2025 assistants were embedded directly into the tools where work happens — IDEs (Copilot, Cursor), office suites (Microsoft 365 Copilot, Google's Gemini in Workspace), and communication tools. The promise was more focus. The lived experience for many knowledge workers was the opposite: **another always-on stream demanding attention** — suggestions to accept or reject, chat panels to consult, notifications, and a new social pressure to \"use the AI.\" This example runs a composite knowledge worker — a senior software engineer, call her Maya — through the deep-work Process to decide how AI should relate to her focus rather than fragment it.\n\nThe core tension is exactly the deep/shallow distinction Newport drew in 2016, now with a new actor. An AI copilot can serve deep work (as a tool inside a protected block) or become shallow work (another interruption stream, another inbox). The framework's job is to keep it the former.\n\n**Step 1 — Instrument.** Maya tracks one week. Her estimate before tracking: \"maybe 4 hours a day of real focused coding.\" The tracked reality: roughly 1–1.5 hours of genuinely uninterrupted deep work per day, scattered in fragments. The new finding specific to 2024–2026: a meaningful share of her fragmentation now comes from *AI-adjacent* micro-switches — pausing mid-thought to prompt a chatbot, context-switching to read and evaluate a generated suggestion, and tab-hopping between editor and assistant. The copilot did not remove interruptions; it added a self-inflicted one that feels productive. This matches the widely-reported pattern in industry research on developer experience: perceived productivity gains from AI tools coexist with fragmented attention, and the recovery cost of task-switching (the 2008 Mark et al. and 2009 Leroy attention-residue findings) does not disappear just because the interruption is a helpful one.\n\n```\n- Deep work hours/day (tracked): ~1.25 | Shallow hours/day: ~5 | Ratio: poor\n- Surprise factor: high — AI prompting felt like focus but registered as switching\n```\n\n**Step 2 — Identify.** The highest-leverage deep work is the hard, hard-to-replicate cognitive work: system design, reasoning about a subtle concurrency bug, and the architectural decisions that shape months of downstream code. This is precisely the class of work that current AI models assist *least* well — they accelerate boilerplate, recall, and first-draft scaffolding, but the load-bearing judgment (what to build, why, and what breaks at scale) still resists being outsourced. Why isn't the deep work happening? Because the day is saturated with shallow work — and now the copilot, if used reflexively, invites her to *stay in* a shallow, reactive loop (accept/reject, re-prompt) instead of holding a hard problem in her head.\n\n**Step 3 — Choose a philosophy.** Maya's role is collaborative but has discrete focus windows, so the **Rhythmic** philosophy fits: a fixed daily deep-work block (the SKILL's recommended default for most). She adds a rule specific to the AI era: the copilot is *scoped by mode*, not banned. In the deep block, AI is allowed only as a pull tool she invokes deliberately for a bounded sub-task (e.g., \"generate the test fixtures so I don't leave flow to write boilerplate\"), never as an ambient chat she monitors. Outside the block, AI-assisted drafting and batching are welcome.\n\n**Step 4 — Build the practice.** Same time (morning, peak cognitive freshness), same location, same setup. She calendars a 90-minute block marked \"Do not interrupt,\" and closes Slack and email — the boundary is binary. The AI-specific move: **turn off ambient/automatic AI features during the block** (inline autosuggestions that interrupt her own line of reasoning, background chat notifications) while keeping the ability to *summon* the assistant on demand for a defined offload. The distinction is control: AI as a tool she reaches for, not a stream that reaches for her. She ends with a shutdown phrase to prevent cognitive leakage.\n\n**Step 5 — Reduce shallow load.** Maya audits meetings, email, and Slack, and adds an AI-native tactic: **use AI to compress shallow work rather than expand it.** She batches low-stakes correspondence and lets the assistant draft first passes of status updates, routine PR descriptions, and meeting summaries — collapsing an hour of shallow work into fifteen minutes, which *buys back* time for the deep block. This is the constructive use of the tool: AI applied to the shallow layer (its comparative advantage) to protect the deep layer (where it is weakest). She sets a shallow-work budget and stays under it.\n\n**Step 6 — Defend.** *Internal:* the discomfort of not reflexively reaching for the AI on every problem — of sitting with a hard problem unaided — fades over a few weeks, the same adaptation curve as going unreachable. Resisting the copilot for the load-bearing thinking is itself the deliberate practice that keeps her skill from atrophying; over-reliance risks deskilling on exactly the judgment that makes her valuable. *External:* she shows the deep block on her calendar and lets output — shipped architecture, hard bugs closed — stand as the long-term proof. She frames AI adoption to her team honestly: the tool multiplies her shallow-work throughput and drafts, but the hard cognitive work is still done by a focused human, and protecting that focus is what makes the AI worth having.\n\nThe mapped steps:\n1. Instrument: tracked week showed ~1.25 deep hrs/day; AI prompting was a hidden source of self-inflicted fragmentation\n2. Identify: system design and subtle debugging — the work AI assists least — as the highest-leverage deep work being crowded out\n3. Philosophy: Rhythmic daily block, with AI scoped by mode (deliberate pull-tool inside the block, not ambient stream)\n4. Practice: morning 90-min block, binary boundary, ambient AI features off but on-demand summon allowed, shutdown ritual\n5. Shallow budget: AI used to compress shallow work (drafts, summaries, boilerplate) to buy back deep-work time\n6. Defense: calendar visibility plus shipped output; internal defense against deskilling by keeping hard judgment human\n\n**The 2026 lesson.** The arrival of capable AI copilots does not repeal the deep/shallow distinction — it sharpens it. The tools are genuinely good at shallow work and first drafts, and genuinely limited at the extended, hard-to-replicate reasoning that deep work exists to produce. The failure mode is treating the copilot as a third inbox to monitor; the winning move is treating it as a tool you invoke to *shrink* the shallow layer, so the deep layer survives. As Newport himself argued through 2024–2025 in his writing and podcast on AI and productivity, the value of undistracted human cognition rises, not falls, as routine output becomes cheap to automate.\n\n*Sources: Newport, C. (2016). Deep Work: Rules for Focused Success in a Distracted World. Grand Central. · Mark, G., Gudith, D., & Klocke, U. (2008). \"The Cost of Interrupted Work: More Speed and Stress.\" CHI 2008 Proceedings. · Leroy, S. (2009). \"Why is it so hard to do my work? The challenge of attention residue when switching between work tasks.\" Organizational Behavior and Human Decision Processes, 109(2), 168-181. · GitHub. \"GitHub Copilot is generally available to all developers\" (announcement, June 21, 2022), https://github.blog/2022-06-21-github-copilot-is-generally-available-to-all-developers/. · OpenAI. \"Introducing ChatGPT\" (November 30, 2022), https://openai.com/blog/chatgpt. · Newport, C. Deep Questions podcast and essays on AI and knowledge work (2024–2025), https://calnewport.com.*\n\nFile v1.0.4:examples/donald-knuth-no-email-policy-1990.md\n\n# Method in Action: Donald Knuth and the No-Email Policy, 1990\n\n> *Example for the [deep-work](../SKILL.md) skill.*\n\nThe most extreme and well-documented case of deep-work practice in modern science is **Donald Knuth**, Professor Emeritus of Computer Science at Stanford and author of *The Art of Computer Programming* (TAOCP), the multi-volume work he has been writing since 1962 and which Bill Gates once called \"the best book on programming ever written.\"\n\nKnuth's challenge: TAOCP requires sustained, cognitively-intensive mathematical and programming work that does not yield to fragmentation. The work also requires Knuth to maintain mathematical correctness across a corpus that, by 2025, runs to several thousand published pages. In the 1980s, as email began to dominate academic life, Knuth observed that his TAOCP progress was slowing — and traced the slowdown to email's compounding effect on his attention.\n\nIn **January 1, 1990**, Knuth announced on his Stanford homepage that he was discontinuing email use. The statement (preserved at https://www-cs-faculty.stanford.edu/~knuth/email.html and unchanged in substance for 35 years) reads:\n\n> \"I have been a happy man ever since January 1, 1990, when I no longer had an email address. I'd used email since about 1975, and it seems to me that 15 years of email is plenty for one lifetime.\n>\n> Email is a wonderful thing for people whose role in life is to be on top of things. But not for me; my role is to be on the bottom of things. What I do takes long hours of studying and uninterruptible concentration. I try to learn certain areas of computer science exhaustively; then I try to digest that knowledge into a form that is accessible to people who don't have time for such study.\"\n\n— Knuth, D. E. (1990 / continuously updated). \"Knuth versus Email.\" Stanford homepage. https://www-cs-faculty.stanford.edu/~knuth/email.html\n\nThe substantive structure of Knuth's argument is precisely the Newport deep/shallow distinction (anticipating Newport's 2016 book by 26 years):\n\n- **\"To be on top of things\"** = the shallow-work mode of constant responsiveness, awareness, coordination\n- **\"To be on the bottom of things\"** = the deep-work mode of sustained, uninterruptible concentration\n- **The trade-off is structural:** Knuth claims you cannot do both. The roles require incompatible cognitive modes.\n\nKnuth's policy is not absence of communication — postal mail still reaches him, and his assistant handles correspondence. The policy is specifically refusal of the *interruption-pattern* email demands, on the grounds that the cost (to deep work) exceeds the value (of any individual email).\n\nThe empirical evidence from Knuth's output: between 1990 and 2025, while running this policy and *also* fully retiring from teaching in 1992, Knuth produced TAOCP Volume 4A (2011), 4B (2022), 4C (in progress), and other works — output that would be remarkable for any full-time professor, let alone an \"emeritus.\" His policy is not eccentric; it is the operational architecture that enables the output.\n\n**Newport's 2016 articulation** generalizes Knuth's insight beyond the specific case. The four philosophies, the shallow-work budget, the rituals — all describe operational implementations of the same deep/shallow trade-off Knuth made formal in 1990.\n\nNewport quotes the cognitive scientist **K. Anders Ericsson**, the originator of the modern theory of expert performance:\n\n> \"Deliberate practice is a highly structured activity, the explicit goal of which is to improve performance. Specific tasks are invented to overcome weaknesses, and performance is carefully monitored to provide cues for ways to improve it further.\"\n>\n> — Ericsson, K. A., Krampe, R. T., & Tesch-Römer, C. (1993). \"The Role of Deliberate Practice in the Acquisition of Expert Performance.\" *Psychological Review*, 100(3), 363-406. p. 368.\n\nNewport draws the connection: deliberate practice is structurally deep work. The expert performers Ericsson studied did not get expert by working more hours; they got expert by doing more *deliberately structured, distraction-free, edge-of-ability* work. The empirical fact that elite performers across domains (musicians, athletes, chess players, programmers, surgeons) all show this pattern is the cognitive-science foundation for deep work.\n\nMark, Gudith & Klocke's empirical study at UC Irvine (2008) added the attention-fragmentation data:\n\n> \"After only 20 minutes of interrupted performance people reported significantly higher stress, frustration, workload, effort, and pressure. We compared self-reports of stress and other affective responses with measures of physiological response. Our results suggest that to compensate for interruptions, people work faster, but this comes at a price: experiencing more stress, higher frustration, time pressure and effort.\"\n>\n> — Mark, G., Gudith, D., & Klocke, U. (2008). \"The Cost of Interrupted Work: More Speed and Stress.\" *Proceedings of the SIGCHI Conference on Human Factors in Computing Systems*, 107-110.\n\nThe combined picture: deep work produces the most valuable knowledge-work output; expert performance requires it; interruption fragments it; and most modern work environments are structurally interruption-saturated. The Newport / Knuth response is structural protection of deep-work time.\n\nThree operational lessons from Knuth's case and Newport's framework:\n\n**First, the cost of shallow work is real but invisible.** Knuth could have kept doing email, and TAOCP would have progressed more slowly, and no one would have noticed which specific volume was delayed. The cost of *not* protecting deep work is paid by the long-term output, not the short-term calendar. This invisibility is what makes the trade-off so frequently lost.\n\n**Second, the social cost is real and must be paid.** Knuth's policy is rude by modern standards. People who write him reasonable, polite emails do not get replies. The framework requires accepting that some social and professional cost is the price of the protected output. There is no costless version.\n\n**Third, the discipline scales down.** Most people cannot, and should not, adopt Knuth's monastic posture. But the same logic — protect specific blocks, accept structural shallow-work reduction, defend the boundary — scales down to 2-4 hours per day of protected deep work, which is enough to dramatically shift output for most knowledge workers.\n\nFile v1.0.4:skill-card.md\n\n## Description: <br>\nGuides agents to help users identify, schedule, and protect focused deep-work blocks for cognitively demanding work such as research, writing, engineering, design, and strategy. <br>\n\nThis skill is ready for commercial/non-commercial use. <br>\n\n## Publisher: <br>\n[deciqai](https://clawhub.ai/user/deciqai) <br>\n\n### License/Terms of Use: <br>\nMIT-0 <br>\n\n\n## Use Case: <br>\nEmployees, developers, and external knowledge workers use this skill to diagnose fragmented attention, choose a deep-work operating model, and produce a concrete plan for protected focus time. It is best suited for work with discrete focus windows and is not intended for emergencies or roles that require continuous real-time coordination. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: Productivity coaching may recommend calendar or communication boundaries that do not fit a user's role, emergency obligations, or workplace norms. <br>\nMitigation: Review suggested boundaries before applying them and adapt the plan to real coordination requirements. <br>\nRisk: The skill invites users to document personal or company-specific focus failures that may be sensitive if stored in skill files. <br>\nMitigation: Avoid adding sensitive personal, team, or company details to persisted skill files unless that storage is intended. <br>\n\n\n## Reference(s): <br>\n- [Deep Work skill page](https://clawhub.ai/deciqai/skills/deep-work) <br>\n- [Sources - deep-work](references/sources.md) <br>\n- [Donald Knuth and the No-Email Policy, 1990](examples/donald-knuth-no-email-policy-1990.md) <br>\n- [Carl Jung's Bollingen Tower Retreats](examples/carl-jung-bollingen-tower-retreats.md) <br>\n- [Protecting Deep Work Amid AI Copilots (2024-2026)](examples/deep-work-amid-ai-copilots-2024-2026.md) <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [Guidance, Markdown, Text] <br>\n**Output Format:** [Markdown plan and stepwise coaching prompts] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [Produces a Deep Work Plan template and coaching questions; no executable output.] <br>\n\n## Skill Version(s): <br>\n1.0.4 (source: server release evidence) <br>\n\n## Ethical Considerations: <br>\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment. <br>\n\nArchive v1.0.3: 6 files, 12587 bytes\n\nFiles: examples/carl-jung-bollingen-tower-retreats.md (5590b), examples/donald-knuth-no-email-policy-1990.md (6441b), references/sources.md (1845b), skill-card.md (2242b), SKILL.md (7659b), _meta.json (128b)\n\nFile v1.0.3:SKILL.md\n\n---\nname: deep-work\ndescription: \"Activate when: user says 'I can never find time for focused work', 'I feel busy but produce nothing', 'I keep getting interrupted', 'I want to protect my focus time', 'flow state', 'deliberate practice', 'Cal Newport', or asks how to make progress on hard cognitive work (research, writing, engineering, strategy). Do NOT activate when: the role is genuinely high-coordination with no discrete focus windows (ER medicine, real-time trading desk), or user is in a short-term emergency where availability must dominate.\"\n---\n\n# Deep Work\n\n## Overview\n\nCal Newport's framework (2016): **deep work** = undistracted, cognitively demanding activity that creates hard-to-replicate value; **shallow work** = logistical, responsive, easy-to-replicate work that fills modern calendars. The most valuable knowledge work is disproportionately the product of deep work; shallow work is increasingly automatable. Three foundations: attention research shows 15-25 min recovery cost per interruption; expert performance requires deliberate practice (structurally a form of deep work); the opportunity cost of shallow work is invisible — no one tracks which deep work didn't happen this week.\n\nComposes with `wu-wei` (flow as the felt experience), `metacognition` (monitoring drift out of deep mode), `okr-goal-setting` (OKRs give deep work direction), `pareto-principle` (the 20% producing 80% of value is almost always deep work).\n\n## When to Use\n\n- Output depends on hard-to-replicate cognitive work (research, engineering, writing, design, strategy)\n- Calendar fragmentation prevents the work that actually matters; weeks feel busy but produce nothing\n- High-stakes project requires extended concentration; career advancement depends on skill development\n\n**Not when:** genuinely high-coordination roles where deep work is structurally impossible; already done with deep work and shallow follow-through is now required; short-term emergency where availability dominates.\n\n## Coaching Novices (Adaptive Front Door)\n\n- **Engine mode:** user has a concrete case → run The Process directly.\n- **Coach mode:** user unfamiliar or has no concrete case → guide step by step.\n\nIn Coach mode, respond one step at a time. Each [WAIT] is a hard stop — output only that step's question, then stop.\n\n1. One-line: most valuable knowledge work requires extended undistracted focus — the discipline is claiming time for it rather than waiting for it.\n2. Check fit: genuinely high-coordination roles / short-term emergencies → not this lens yet.\n3. Elicit the specific work that requires depth — what's not getting done?\n> **[WAIT — do not advance until user responds]**\n4. One question at a time: what's your deep-vs-shallow ratio? What's the highest-leverage deep work? What's the cost of not doing it?\n> **[WAIT — do not advance until user responds]**\n5. Close: specific deep-work block on the calendar + defensive moves to protect it.\n> **[WAIT — do not advance until user responds]**\n\n## The Process\n\n**Step 1 — Instrument:** Track one week. Most workers estimate 4-5 hrs/day deep; measurement shows 0.5-2 hrs in fragments.\n```\n- Deep work hours/day (tracked): | Shallow hours/day: | Ratio: | Surprise factor:\n```\n**Step 2 — Identify:** What specific deep work, if done well, produces the most valuable output? Why isn't it happening? What barriers?\n\n**Step 3 — Choose a philosophy:** Monastic (eliminate shallow entirely); Bimodal (alternating deep/shallow periods); Rhythmic (fixed daily block — best default for most); Journalistic (switch in whenever a gap appears — requires strong attention discipline, worst for beginners).\n\n**Step 4 — Build the practice:** Same time + location + setup (ritual). Calendar the block, mark \"Do not interrupt.\" End with a shutdown phrase to prevent cognitive leakage. Boundary is binary: Slack/email closed or you are not in deep work.\n\n**Step 5 — Reduce shallow load:** Audit meetings, email, Slack. Set a shallow-work budget (typically 30-50% for ICs) and stay under it.\n\n**Step 6 — Defend:** Internal — discomfort of being unreachable fades over 2-4 weeks. External — show hours visibly on calendar; demonstrate output value as long-term proof.\n\n## Output: Deep Work Plan\n\n```markdown\n# Deep Work Plan: <person, role>\nDiagnosis — deep hrs/day: | shallow hrs/day: | deep work not happening:\nPhilosophy — selected: | why this fits:\nStructure — block time/duration/location: | ritual: | boundary: | shutdown:\nShallow budget — %: | specific reductions:\nDefense — calendar mark: | comms norms: | output evidence to track:\n```\n\n*→ Method in Action: [Donald Knuth and the No-Email Policy, 1990](examples/donald-knuth-no-email-policy-1990.md) · [Carl Jung's Bollingen Tower Retreats](examples/carl-jung-bollingen-tower-retreats.md)*\n\n## Pack: Deep Work by Role\n\n| Role | Highest-leverage deep work | Common shallow intrusion |\n|---|---|---|\n| Engineer | Architecture, hard debugging | Slack, status meetings |\n| Writer | Drafting, revision | Email, research rabbit holes |\n| Researcher | Literature synthesis, experiments | Grant admin, departmental meetings |\n| Founder | Strategy, customer depth, recruiting | Investor follow-up, feedback meetings |\n| PM | Research synthesis, spec writing | Alignment meetings, status reports |\n\n## Applying It Well\n\nProtect the morning block first — cognitive freshness depletes with shallow work. Track deep-work hours as a lagging metric. Treat the shutdown ritual as non-negotiable. Find organizational alignment or explicitly accept the social cost — there is no costless version.\n\n*→ Primary sources: [references/sources.md](references/sources.md)*\n\n## Common Rationalizations\n\n**[D] = designed upfront | [O] = observed in real use. [O] entries are more valuable.**\n\n| Fake move | Reality |\n|---|---|\n| [D] \"My role doesn't allow deep work\" | The role *culture* disallows it; the role itself usually doesn't. |\n| [D] \"I do deep work in the evenings\" | Cognitive freshness already spent. Reorder: deep work first. |\n| [D] \"I'm doing deep work\" with Slack open | Slack open = deep work not happening. Boundary is binary. |\n| [D] \"I can multitask in deep work\" | Only task-switching, which is expensive. Category error. |\n| [D] \"Available for emergencies during deep work\" | Most emergencies aren't. Define a true-emergency channel; ignore the rest. |\n| [D] Confusing \"long hours\" with \"deep work\" | Deep work = intensity × duration, not just duration. |\n| *→ Add [O] entries here after each real use — paste the actual failure pattern* | *What went wrong and why* |\n\n## Red Flags\n\n- \"Hours worked\" reported but \"hours of deep work\" cannot be quantified\n- Calendar fragmented with 30-min slots across the day; Slack open continuously\n- Deep work happens only at evenings/weekends, not at peak cognitive hours\n- After a productive-feeling day, cannot point to a single deep-work artifact produced\n\n## Verification\n\n- [ ] Deep-vs-shallow ratio measured (one week tracked)\n- [ ] Highest-leverage deep work identified\n- [ ] Philosophy chosen with match to constraints; specific block calendared\n- [ ] Ritual, boundary, and shutdown operational; shallow-work budget named\n- [ ] Social/organizational cost explicitly accepted; output evidence tracked\n\n---\n\n*Part of **deciqAI Knowledge Skills** — 164 open-source thinking skills that make rigor executable for AI agents. The same skills power every deciqAI agent, which runs them autonomously to operate your company. **See it run → https://www.deciqai.com/c/deep-work** · ⭐ Star the repo → https://github.com/deciqAI/knowledge-skills · Contributions welcome.*\n\nFile v1.0.3:_meta.json\n\n{\n  \"ownerId\": \"kn754b8sk22s8c6gjxt02bftbn88q7ye\",\n  \"slug\": \"deep-work\",\n  \"version\": \"1.0.3\",\n  \"publishedAt\": 1783508348826\n}\n\nFile v1.0.3:references/sources.md\n\n# Sources — deep-work\n\n> *Primary sources for the [deep-work](../SKILL.md) skill.*\n\n- Newport, C. (2016). *Deep Work: Rules for Focused Success in a Distracted World.* Grand Central. ISBN 978-1455586691. The canonical articulation.\n- Knuth, D. E. (1990 / ongoing). \"Knuth versus Email.\" Stanford homepage. https://www-cs-faculty.stanford.edu/~knuth/email.html. The earliest extreme-deep-work case study with the practitioner's own documentation.\n- Jung, C. G. (1962). *Memories, Dreams, Reflections.* Recorded and edited by Aniela Jaffé; trans. Richard and Clara Winston (1963). Pantheon. The chapter \"The Tower\" is Jung's own account of the Bollingen retreat practice — the canonical bimodal case.\n- Ericsson, K. A., Krampe, R. T., & Tesch-Römer, C. (1993). \"The Role of Deliberate Practice in the Acquisition of Expert Performance.\" *Psychological Review*, 100(3), 363-406. The foundational empirical paper on expert performance and deliberate practice.\n- Mark, G., Gudith, D., & Klocke, U. (2008). \"The Cost of Interrupted Work: More Speed and Stress.\" *CHI 2008 Proceedings*. The empirical psychology of attention-switching.\n- Leroy, S. (2009). \"Why is it so hard to do my work? The challenge of attention residue when switching between work tasks.\" *Organizational Behavior and Human Decision Processes*, 109(2), 168-181. The \"attention residue\" concept.\n- Csikszentmihalyi, M. (1990). *Flow: The Psychology of Optimal Experience.* Harper & Row. ISBN 978-0061339202. The experiential side of deep work.\n- Newport, C. (2019). *Digital Minimalism: Choosing a Focused Life in a Noisy World.* Portfolio. ISBN 978-0525536512. The companion volume on personal-life dimensions.\n- Carr, N. (2010). *The Shallows: What the Internet Is Doing to Our Brains.* Norton. ISBN 978-0393339758. The cultural diagnosis of why deep work has become rare.\n\nFile v1.0.3:examples/carl-jung-bollingen-tower-retreats.md\n\n# Method in Action: Carl Jung's Bollingen Tower Retreats (1923–1961)\n\n> *Example for the [deep-work](../SKILL.md) skill.*\n\nCarl Jung's Bollingen tower is the case Cal Newport chose to open *Deep Work* (2016), and it remains the cleanest historical demonstration of the **Bimodal philosophy**: a working psychiatrist who could not abandon his shallow obligations, and instead built a physical architecture for alternating between them and depth.\n\n**The diagnosis (Steps 1-2):** In the 1920s Jung's professional life in Zurich and Küsnacht was structurally shallow-saturated: a busy clinical practice with a full patient load, lectures, seminars, and heavy correspondence. This was also the period in which Jung was establishing analytical psychology as an independent school after his break with Freud — an intellectual project competing against the most formidable rival imaginable. The highest-leverage deep work was unambiguous: the sustained theoretical writing that would define archetypes, the collective unconscious, and individuation. That writing could not happen between patient sessions. Jung did not need a tracking week to see the ratio; the clinical calendar made it visible.\n\n**The philosophy choice (Step 3):** Jung could not go monastic — his clinical practice was both his income and his empirical material. He chose the bimodal split: full engagement with practice and public life in Zurich, then regular retreats to a private refuge for concentrated writing.\n\n**The practice (Step 4):** In 1922 Jung bought land at Bollingen on the upper lake of Zurich, and beginning in 1923 built a stone tower there by stages, expanding it over the following decades. The tower was deliberately spartan — no electricity; Jung chopped his own wood, drew his own water, and lit oil lamps. In *Memories, Dreams, Reflections* (1962), the chapter \"The Tower\" describes the place in Jung's own account as a site of repose and renewal where he felt most deeply himself — a purpose-built container for concentration. Newport reconstructs the working rhythm: mornings locked in a private study for undisturbed writing, afternoons given to meditation and walks, early nights. Same location, same setup, hard boundary — the full ritual structure of Step 4, implemented in stone.\n\n**Shallow reduction and defense (Steps 5-6):** Every Bollingen period was clinical income refused and patients turned away — the shallow-work budget enforced at direct financial cost. The retreats could look like withdrawal from a career; they were its engine. The output produced across four decades of this regime — the essays and books that became the *Collected Works* and established analytical psychology as a lasting school — is the long-term evidence Step 6 says to accumulate: output value as the defense of the practice.\n\nThe structural lesson mirrors Knuth's but from the opposite pole: Knuth shows the monastic extreme (eliminate the shallow channel permanently); Jung shows that a practitioner who *cannot* eliminate shallow work can still get monastic-grade depth by alternating modes — provided the deep mode has a hard physical and temporal boundary, a ritual, and an accepted cost.\n\nThree operational lessons from the Bollingen case:\n\n**First, bimodal beats waiting.** Jung never had a calendar that \"allowed\" deep work; he manufactured the allowance by pre-committing whole blocks of days. Anyone whose role genuinely requires shallow engagement — clinicians, managers, founders — should read Jung, not Knuth, as the applicable template: claim retreat units (a day, a week) rather than trying to carve depth out of an interrupt-driven day.\n\n**Second, the environment does defensive work the willpower budget cannot.** A tower with no electricity, reachable only by deliberate travel, made shallow intrusion physically impossible rather than merely discouraged. The modern equivalent is weaker but real: a separate room, a machine with no messaging clients, a location where interruption cannot follow. Build the boundary into the environment so it does not have to be re-decided hourly.\n\n**Third, deep work was not competing against the practice — it fed it.** Jung's clinical work supplied the case material his theoretical writing systematized, and the writing in turn made the practice world-famous. The bimodal split is not a tax paid by the shallow mode; run well, each mode compounds the other. That is the strongest answer to the \"my role doesn't allow it\" rationalization.\n\nThe mapped steps:\n1. Instrument: Zurich clinical calendar made the deep/shallow ratio visible — practice, lectures, correspondence consumed the day\n2. Identify: the theoretical corpus of analytical psychology, in direct competition with Freud, was the highest-leverage deep work not happening\n3. Philosophy: Bimodal — full shallow engagement in Zurich alternating with retreat periods at Bollingen\n4. Practice: the stone tower as ritual — fixed location, spartan setup, locked morning study, afternoon walks, early nights\n5. Shallow budget: patients refused and engagements declined during retreat periods, at real financial cost\n6. Defense: decades of published output — the *Collected Works* — as the standing proof that the protected time paid\n\nPrimary source: Jung, C. G. (1962). *Memories, Dreams, Reflections.* Recorded and edited by Aniela Jaffé; trans. Richard and Clara Winston (1963). Pantheon. Chapter \"The Tower.\" Secondary: Newport, C. (2016). *Deep Work: Rules for Focused Success in a Distracted World.* Grand Central. Chapter 1 and Rule #1 (Bimodal philosophy).\n\nFile v1.0.3:examples/donald-knuth-no-email-policy-1990.md\n\n# Method in Action: Donald Knuth and the No-Email Policy, 1990\n\n> *Example for the [deep-work](../SKILL.md) skill.*\n\nThe most extreme and well-documented case of deep-work practice in modern science is **Donald Knuth**, Professor Emeritus of Computer Science at Stanford and author of *The Art of Computer Programming* (TAOCP), the multi-volume work he has been writing since 1962 and which Bill Gates once called \"the best book on programming ever written.\"\n\nKnuth's challenge: TAOCP requires sustained, cognitively-intensive mathematical and programming work that does not yield to fragmentation. The work also requires Knuth to maintain mathematical correctness across a corpus that, by 2025, runs to several thousand published pages. In the 1980s, as email began to dominate academic life, Knuth observed that his TAOCP progress was slowing — and traced the slowdown to email's compounding effect on his attention.\n\nIn **January 1, 1990**, Knuth announced on his Stanford homepage that he was discontinuing email use. The statement (preserved at https://www-cs-faculty.stanford.edu/~knuth/email.html and unchanged in substance for 35 years) reads:\n\n> \"I have been a happy man ever since January 1, 1990, when I no longer had an email address. I'd used email since about 1975, and it seems to me that 15 years of email is plenty for one lifetime.\n>\n> Email is a wonderful thing for people whose role in life is to be on top of things. But not for me; my role is to be on the bottom of things. What I do takes long hours of studying and uninterruptible concentration. I try to learn certain areas of computer science exhaustively; then I try to digest that knowledge into a form that is accessible to people who don't have time for such study.\"\n\n— Knuth, D. E. (1990 / continuously updated). \"Knuth versus Email.\" Stanford homepage. https://www-cs-faculty.stanford.edu/~knuth/email.html\n\nThe substantive structure of Knuth's argument is precisely the Newport deep/shallow distinction (anticipating Newport's 2016 book by 26 years):\n\n- **\"To be on top of things\"** = the shallow-work mode of constant responsiveness, awareness, coordination\n- **\"To be on the bottom of things\"** = the deep-work mode of sustained, uninterruptible concentration\n- **The trade-off is structural:** Knuth claims you cannot do both. The roles require incompatible cognitive modes.\n\nKnuth's policy is not absence of communication — postal mail still reaches him, and his assistant handles correspondence. The policy is specifically refusal of the *interruption-pattern* email demands, on the grounds that the cost (to deep work) exceeds the value (of any individual email).\n\nThe empirical evidence from Knuth's output: between 1990 and 2025, while running this policy and *also* fully retiring from teaching in 1992, Knuth produced TAOCP Volume 4A (2011), 4B (2022), 4C (in progress), and other works — output that would be remarkable for any full-time professor, let alone an \"emeritus.\" His policy is not eccentric; it is the operational architecture that enables the output.\n\n**Newport's 2016 articulation** generalizes Knuth's insight beyond the specific case. The four philosophies, the shallow-work budget, the rituals — all describe operational implementations of the same deep/shallow trade-off Knuth made formal in 1990.\n\nNewport quotes the cognitive scientist **K. Anders Ericsson**, the originator of the modern theory of expert performance:\n\n> \"Deliberate practice is a highly structured activity, the explicit goal of which is to improve performance. Specific tasks are invented to overcome weaknesses, and performance is carefully monitored to provide cues for ways to improve it further.\"\n>\n> — Ericsson, K. A., Krampe, R. T., & Tesch-Römer, C. (1993). \"The Role of Deliberate Practice in the Acquisition of Expert Performance.\" *Psychological Review*, 100(3), 363-406. p. 368.\n\nNewport draws the connection: deliberate practice is structurally deep work. The expert performers Ericsson studied did not get expert by working more hours; they got expert by doing more *deliberately structured, distraction-free, edge-of-ability* work. The empirical fact that elite performers across domains (musicians, athletes, chess players, programmers, surgeons) all show this pattern is the cognitive-science foundation for deep work.\n\nMark, Gudith & Klocke's empirical study at UC Irvine (2008) added the attention-fragmentation data:\n\n> \"After only 20 minutes of interrupted performance people reported significantly higher stress, frustration, workload, effort, and pressure. We compared self-reports of stress and other affective responses with measures of physiological response. Our results suggest that to compensate for interruptions, people work faster, but this comes at a price: experiencing more stress, higher frustration, time pressure and effort.\"\n>\n> — Mark, G., Gudith, D., & Klocke, U. (2008). \"The Cost of Interrupted Work: More Speed and Stress.\" *Proceedings of the SIGCHI Conference on Human Factors in Computing Systems*, 107-110.\n\nThe combined picture: deep work produces the most valuable knowledge-work output; expert performance requires it; interruption fragments it; and most modern work environments are structurally interruption-saturated. The Newport / Knuth response is structural protection of deep-work time.\n\nThree operational lessons from Knuth's case and Newport's framework:\n\n**First, the cost of shallow work is real but invisible.** Knuth could have kept doing email, and TAOCP would have progressed more slowly, and no one would have noticed which specific volume was delayed. The cost of *not* protecting deep work is paid by the long-term output, not the short-term calendar. This invisibility is what makes the trade-off so frequently lost.\n\n**Second, the social cost is real and must be paid.** Knuth's policy is rude by modern standards. People who write him reasonable, polite emails do not get replies. The framework requires accepting that some social and professional cost is the price of the protected output. There is no costless version.\n\n**Third, the discipline scales down.** Most people cannot, and should not, adopt Knuth's monastic posture. But the same logic — protect specific blocks, accept structural shallow-work reduction, defend the boundary — scales down to 2-4 hours per day of protected deep work, which is enough to dramatically shift output for most knowledge workers.\n\nFile v1.0.3:skill-card.md\n\n## Description: <br>\nHelps agents coach users through planning focused, cognitively demanding work and producing a practical Deep Work Plan. <br>\n\nThis skill is ready for commercial/non-commercial use. <br>\n\n## Publisher: <br>\n[deciqai](https://clawhub.ai/user/deciqai) <br>\n\n### License/Terms of Use: <br>\nMIT-0 <br>\n\n\n## Use Case: <br>\nEmployees, external users, and knowledge-work teams use this skill to diagnose shallow-work pressure, choose a focus strategy, and define calendar, communication, and tracking practices for valuable deep work. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: Advice to reduce availability or communication channels may conflict with roles where responsiveness is required. <br>\nMitigation: Apply the skill's fit checks first and avoid using this lens during emergencies or genuinely high-coordination work. <br>\nRisk: Users may overapply productivity advice without considering team norms or operational obligations. <br>\nMitigation: Review the proposed Deep Work Plan before acting on it and align calendar blocks, communication boundaries, and escalation channels with the user's role. <br>\n\n\n## Reference(s): <br>\n- [Sources - deep-work](references/sources.md) <br>\n- [Donald Knuth and the No-Email Policy, 1990](examples/donald-knuth-no-email-policy-1990.md) <br>\n- [Carl Jung's Bollingen Tower Retreats](examples/carl-jung-bollingen-tower-retreats.md) <br>\n- [Knuth versus Email](https://www-cs-faculty.stanford.edu/~knuth/email.html) <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [guidance, markdown] <br>\n**Output Format:** [Markdown plan with structured coaching prompts] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [Produces a Deep Work Plan covering diagnosis, work philosophy, schedule structure, shallow-work budget, and defense practices.] <br>\n\n## Skill Version(s): <br>\n1.0.3 (source: server-resolved release metadata) <br>\n\n## Ethical Considerations: <br>\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment. <br>\n\nArchive v1.0.2: 6 files, 12595 bytes\n\nFiles: examples/carl-jung-bollingen-tower-retreats.md (5590b), examples/donald-knuth-no-email-policy-1990.md (6441b), references/sources.md (1845b), skill-card.md (2217b), SKILL.md (7758b), _meta.json (128b)\n\nFile v1.0.2:SKILL.md\n\n---\nname: deep-work\ndescription: \"Activate when: user says 'I can never find time for focused work', 'I feel busy but produce nothing', 'I keep getting interrupted', 'I want to protect my focus time', 'flow state', 'deliberate practice', 'Cal Newport', or asks how to make progress on hard cognitive work (research, writing, engineering, strategy). Do NOT activate when: the role is genuinely high-coordination with no discrete focus windows (ER medicine, real-time trading desk), or user is in a short-term emergency where availability must dominate.\"\n---\n\n# Deep Work\n\n## Overview\n\nCal Newport's framework (2016): **deep work** = undistracted, cognitively demanding activity that creates hard-to-replicate value; **shallow work** = logistical, responsive, easy-to-replicate work that fills modern calendars. The most valuable knowledge work is disproportionately the product of deep work; shallow work is increasingly automatable. Three foundations: attention research shows 15-25 min recovery cost per interruption; expert performance requires deliberate practice (structurally a form of deep work); the opportunity cost of shallow work is invisible — no one tracks which deep work didn't happen this week.\n\nComposes with `wu-wei` (flow as the felt experience), `metacognition` (monitoring drift out of deep mode), `okr-goal-setting` (OKRs give deep work direction), `pareto-principle` (the 20% producing 80% of value is almost always deep work).\n\n## When to Use\n\n- Output depends on hard-to-replicate cognitive work (research, engineering, writing, design, strategy)\n- Calendar fragmentation prevents the work that actually matters; weeks feel busy but produce nothing\n- High-stakes project requires extended concentration; career advancement depends on skill development\n\n**Not when:** genuinely high-coordination roles where deep work is structurally impossible; already done with deep work and shallow follow-through is now required; short-term emergency where availability dominates.\n\n## Coaching Novices (Adaptive Front Door)\n\n- **Engine mode:** user has a concrete case → run The Process directly.\n- **Coach mode:** user unfamiliar or has no concrete case → guide step by step.\n\nIn Coach mode, respond one step at a time. Each [WAIT] is a hard stop — output only that step's question, then stop.\n\n1. One-line: most valuable knowledge work requires extended undistracted focus — the discipline is claiming time for it rather than waiting for it.\n2. Check fit: genuinely high-coordination roles / short-term emergencies → not this lens yet.\n3. Elicit the specific work that requires depth — what's not getting done?\n> **[WAIT — do not advance until user responds]**\n4. One question at a time: what's your deep-vs-shallow ratio? What's the highest-leverage deep work? What's the cost of not doing it?\n> **[WAIT — do not advance until user responds]**\n5. Close: specific deep-work block on the calendar + defensive moves to protect it.\n> **[WAIT — do not advance until user responds]**\n\n## The Process\n\n**Step 1 — Instrument:** Track one week. Most workers estimate 4-5 hrs/day deep; measurement shows 0.5-2 hrs in fragments.\n```\n- Deep work hours/day (tracked): | Shallow hours/day: | Ratio: | Surprise factor:\n```\n**Step 2 — Identify:** What specific deep work, if done well, produces the most valuable output? Why isn't it happening? What barriers?\n\n**Step 3 — Choose a philosophy:** Monastic (eliminate shallow entirely); Bimodal (alternating deep/shallow periods); Rhythmic (fixed daily block — best default for most); Journalistic (switch in whenever a gap appears — requires strong attention discipline, worst for beginners).\n\n**Step 4 — Build the practice:** Same time + location + setup (ritual). Calendar the block, mark \"Do not interrupt.\" End with a shutdown phrase to prevent cognitive leakage. Boundary is binary: Slack/email closed or you are not in deep work.\n\n**Step 5 — Reduce shallow load:** Audit meetings, email, Slack. Set a shallow-work budget (typically 30-50% for ICs) and stay under it.\n\n**Step 6 — Defend:** Internal — discomfort of being unreachable fades over 2-4 weeks. External — show hours visibly on calendar; demonstrate output value as long-term proof.\n\n## Output: Deep Work Plan\n\n```markdown\n# Deep Work Plan: <person, role>\nDiagnosis — deep hrs/day: | shallow hrs/day: | deep work not happening:\nPhilosophy — selected: | why this fits:\nStructure — block time/duration/location: | ritual: | boundary: | shutdown:\nShallow budget — %: | specific reductions:\nDefense — calendar mark: | comms norms: | output evidence to track:\n```\n\n*→ Method in Action: [Donald Knuth and the No-Email Policy, 1990](examples/donald-knuth-no-email-policy-1990.md) · [Carl Jung's Bollingen Tower Retreats](examples/carl-jung-bollingen-tower-retreats.md)*\n\n## Pack: Deep Work by Role\n\n| Role | Highest-leverage deep work | Common shallow intrusion |\n|---|---|---|\n| Engineer | Architecture, hard debugging | Slack, status meetings |\n| Writer | Drafting, revision | Email, research rabbit holes |\n| Researcher | Literature synthesis, experiments | Grant admin, departmental meetings |\n| Founder | Strategy, customer depth, recruiting | Investor follow-up, feedback meetings |\n| PM | Research synthesis, spec writing | Alignment meetings, status reports |\n\n## Applying It Well\n\nProtect the morning block first — cognitive freshness depletes with shallow work. Track deep-work hours as a lagging metric. Treat the shutdown ritual as non-negotiable. Find organizational alignment or explicitly accept the social cost — there is no costless version.\n\n*→ Primary sources: [references/sources.md](references/sources.md)*\n\n## Common Rationalizations\n\n**[D] = designed upfront | [O] = observed in real use. [O] entries are more valuable.**\n\n| Fake move | Reality |\n|---|---|\n| [D] \"My role doesn't allow deep work\" | The role *culture* disallows it; the role itself usually doesn't. |\n| [D] \"I do deep work in the evenings\" | Cognitive freshness already spent. Reorder: deep work first. |\n| [D] \"I'm doing deep work\" with Slack open | Slack open = deep work not happening. Boundary is binary. |\n| [D] \"I can multitask in deep work\" | Only task-switching, which is expensive. Category error. |\n| [D] \"Available for emergencies during deep work\" | Most emergencies aren't. Define a true-emergency channel; ignore the rest. |\n| [D] Confusing \"long hours\" with \"deep work\" | Deep work = intensity × duration, not just duration. |\n| *→ Add [O] entries here after each real use — paste the actual failure pattern* | *What went wrong and why* |\n\n## Red Flags\n\n- \"Hours worked\" reported but \"hours of deep work\" cannot be quantified\n- Calendar fragmented with 30-min slots across the day; Slack open continuously\n- Deep work happens only at evenings/weekends, not at peak cognitive hours\n- After a productive-feeling day, cannot point to a single deep-work artifact produced\n\n## Verification\n\n- [ ] Deep-vs-shallow ratio measured (one week tracked)\n- [ ] Highest-leverage deep work identified\n- [ ] Philosophy chosen with match to constraints; specific block calendared\n- [ ] Ritual, boundary, and shutdown operational; shallow-work budget named\n- [ ] Social/organizational cost explicitly accepted; output evidence tracked\n\n---\n\n*Part of **deciqAI Knowledge Skills** — 163 open-source thinking skills that make rigor executable for AI agents. The same skills power every deciqAI agent, which runs them autonomously to operate your company. **See it run → https://www.deciqai.com/skills/deep-work?utm_source=clawhub&utm_medium=marketplace&utm_campaign=knowledge-skills&utm_content=deep-work** · ⭐ Star the repo → https://github.com/deciqAI/knowledge-skills · Contributions welcome.*\n\nFile v1.0.2:_meta.json\n\n{\n  \"ownerId\": \"kn754b8sk22s8c6gjxt02bftbn88q7ye\",\n  \"slug\": \"deep-work\",\n  \"version\": \"1.0.2\",\n  \"publishedAt\": 1783471443457\n}\n\nFile v1.0.2:references/sources.md\n\n# Sources — deep-work\n\n> *Primary sources for the [deep-work](../SKILL.md) skill.*\n\n- Newport, C. (2016). *Deep Work: Rules for Focused Success in a Distracted World.* Grand Central. ISBN 978-1455586691. The canonical articulation.\n- Knuth, D. E. (1990 / ongoing). \"Knuth versus Email.\" Stanford homepage. https://www-cs-faculty.stanford.edu/~knuth/email.html. The earliest extreme-deep-work case study with the practitioner's own documentation.\n- Jung, C. G. (1962). *Memories, Dreams, Reflections.* Recorded and edited by Aniela Jaffé; trans. Richard and Clara Winston (1963). Pantheon. The chapter \"The Tower\" is Jung's own account of the Bollingen retreat practice — the canonical bimodal case.\n- Ericsson, K. A., Krampe, R. T., & Tesch-Römer, C. (1993). \"The Role of Deliberate Practice in the Acquisition of Expert Performance.\" *Psychological Review*, 100(3), 363-406. The foundational empirical paper on expert performance and deliberate practice.\n- Mark, G., Gudith, D., & Klocke, U. (2008). \"The Cost of Interrupted Work: More Speed and Stress.\" *CHI 2008 Proceedings*. The empirical psychology of attention-switching.\n- Leroy, S. (2009). \"Why is it so hard to do my work? The challenge of attention residue when switching between work tasks.\" *Organizational Behavior and Human Decision Processes*, 109(2), 168-181. The \"attention residue\" concept.\n- Csikszentmihalyi, M. (1990). *Flow: The Psychology of Optimal Experience.* Harper & Row. ISBN 978-0061339202. The experiential side of deep work.\n- Newport, C. (2019). *Digital Minimalism: Choosing a Focused Life in a Noisy World.* Portfolio. ISBN 978-0525536512. The companion volume on personal-life dimensions.\n- Carr, N. (2010). *The Shallows: What the Internet Is Doing to Our Brains.* Norton. ISBN 978-0393339758. The cultural diagnosis of why deep work has become rare.\n\nFile v1.0.2:examples/carl-jung-bollingen-tower-retreats.md\n\n# Method in Action: Carl Jung's Bollingen Tower Retreats (1923–1961)\n\n> *Example for the [deep-work](../SKILL.md) skill.*\n\nCarl Jung's Bollingen tower is the case Cal Newport chose to open *Deep Work* (2016), and it remains the cleanest historical demonstration of the **Bimodal philosophy**: a working psychiatrist who could not abandon his shallow obligations, and instead built a physical architecture for alternating between them and depth.\n\n**The diagnosis (Steps 1-2):** In the 1920s Jung's professional life in Zurich and Küsnacht was structurally shallow-saturated: a busy clinical practice with a full patient load, lectures, seminars, and heavy correspondence. This was also the period in which Jung was establishing analytical psychology as an independent school after his break with Freud — an intellectual project competing against the most formidable rival imaginable. The highest-leverage deep work was unambiguous: the sustained theoretical writing that would define archetypes, the collective unconscious, and individuation. That writing could not happen between patient sessions. Jung did not need a tracking week to see the ratio; the clinical calendar made it visible.\n\n**The philosophy choice (Step 3):** Jung could not go monastic — his clinical practice was both his income and his empirical material. He chose the bimodal split: full engagement with practice and public life in Zurich, then regular retreats to a private refuge for concentrated writing.\n\n**The practice (Step 4):** In 1922 Jung bought land at Bollingen on the upper lake of Zurich, and beginning in 1923 built a stone tower there by stages, expanding it over the following decades. The tower was deliberately spartan — no electricity; Jung chopped his own wood, drew his own water, and lit oil lamps. In *Memories, Dreams, Reflections* (1962), the chapter \"The Tower\" describes the place in Jung's own account as a site of repose and renewal where he felt most deeply himself — a purpose-built container for concentration. Newport reconstructs the working rhythm: mornings locked in a private study for undisturbed writing, afternoons given to meditation and walks, early nights. Same location, same setup, hard boundary — the full ritual structure of Step 4, implemented in stone.\n\n**Shallow reduction and defense (Steps 5-6):** Every Bollingen period was clinical income refused and patients turned away — the shallow-work budget enforced at direct financial cost. The retreats could look like withdrawal from a career; they were its engine. The output produced across four decades of this regime — the essays and books that became the *Collected Works* and established analytical psychology as a lasting school — is the long-term evidence Step 6 says to accumulate: output value as the defense of the practice.\n\nThe structural lesson mirrors Knuth's but from the opposite pole: Knuth shows the monastic extreme (eliminate the shallow channel permanently); Jung shows that a practitioner who *cannot* eliminate shallow work can still get monastic-grade depth by alternating modes — provided the deep mode has a hard physical and temporal boundary, a ritual, and an accepted cost.\n\nThree operational lessons from the Bollingen case:\n\n**First, bimodal beats waiting.** Jung never had a calendar that \"allowed\" deep work; he manufactured the allowance by pre-committing whole blocks of days. Anyone whose role genuinely requires shallow engagement — clinicians, managers, founders — should read Jung, not Knuth, as the applicable template: claim retreat units (a day, a week) rather than trying to carve depth out of an interrupt-driven day.\n\n**Second, the environment does defensive work the willpower budget cannot.** A tower with no electricity, reachable only by deliberate travel, made shallow intrusion physically impossible rather than merely discouraged. The modern equivalent is weaker but real: a separate room, a machine with no messaging clients, a location where interruption cannot follow. Build the boundary into the environment so it does not have to be re-decided hourly.\n\n**Third, deep work was not competing against the practice — it fed it.** Jung's clinical work supplied the case material his theoretical writing systematized, and the writing in turn made the practice world-famous. The bimodal split is not a tax paid by the shallow mode; run well, each mode compounds the other. That is the strongest answer to the \"my role doesn't allow it\" rationalization.\n\nThe mapped steps:\n1. Instrument: Zurich clinical calendar made the deep/shallow ratio visible — practice, lectures, correspondence consumed the day\n2. Identify: the theoretical corpus of analytical psychology, in direct competition with Freud, was the highest-leverage deep work not happening\n3. Philosophy: Bimodal — full shallow engagement in Zurich alternating with retreat periods at Bollingen\n4. Practice: the stone tower as ritual — fixed location, spartan setup, locked morning study, afternoon walks, early nights\n5. Shallow budget: patients refused and engagements declined during retreat periods, at real financial cost\n6. Defense: decades of published output — the *Collected Works* — as the standing proof that the protected time paid\n\nPrimary source: Jung, C. G. (1962). *Memories, Dreams, Reflections.* Recorded and edited by Aniela Jaffé; trans. Richard and Clara Winston (1963). Pantheon. Chapter \"The Tower.\" Secondary: Newport, C. (2016). *Deep Work: Rules for Focused Success in a Distracted World.* Grand Central. Chapter 1 and Rule #1 (Bimodal philosophy).\n\nFile v1.0.2:examples/donald-knuth-no-email-policy-1990.md\n\n# Method in Action: Donald Knuth and the No-Email Policy, 1990\n\n> *Example for the [deep-work](../SKILL.md) skill.*\n\nThe most extreme and well-documented case of deep-work practice in modern science is **Donald Knuth**, Professor Emeritus of Computer Science at Stanford and author of *The Art of Computer Programming* (TAOCP), the multi-volume work he has been writing since 1962 and which Bill Gates once called \"the best book on programming ever written.\"\n\nKnuth's challenge: TAOCP requires sustained, cognitively-intensive mathematical and programming work that does not yield to fragmentation. The work also requires Knuth to maintain mathematical correctness across a corpus that, by 2025, runs to several thousand published pages. In the 1980s, as email began to dominate academic life, Knuth observed that his TAOCP progress was slowing — and traced the slowdown to email's compounding effect on his attention.\n\nIn **January 1, 1990**, Knuth announced on his Stanford homepage that he was discontinuing email use. The statement (preserved at https://www-cs-faculty.stanford.edu/~knuth/email.html and unchanged in substance for 35 years) reads:\n\n> \"I have been a happy man ever since January 1, 1990, when I no longer had an email address. I'd used email since about 1975, and it seems to me that 15 years of email is plenty for one lifetime.\n>\n> Email is a wonderful thing for people whose role in life is to be on top of things. But not for me; my role is to be on the bottom of things. What I do takes long hours of studying and uninterruptible concentration. I try to learn certain areas of computer science exhaustively; then I try to digest that knowledge into a form that is accessible to people who don't have time for such study.\"\n\n— Knuth, D. E. (1990 / continuously updated). \"Knuth versus Email.\" Stanford homepage. https://www-cs-faculty.stanford.edu/~knuth/email.html\n\nThe substantive structure of Knuth's argument is precisely the Newport deep/shallow distinction (anticipating Newport's 2016 book by 26 years):\n\n- **\"To be on top of things\"** = the shallow-work mode of constant responsiveness, awareness, coordination\n- **\"To be on the bottom of things\"** = the deep-work mode of sustained, uninterruptible concentration\n- **The trade-off is structural:** Knuth claims you cannot do both. The roles require incompatible cognitive modes.\n\nKnuth's policy is not absence of communication — postal mail still reaches him, and his assistant handles correspondence. The policy is specifically refusal of the *interruption-pattern* email demands, on the grounds that the cost (to deep work) exceeds the value (of any individual email).\n\nThe empirical evidence from Knuth's output: between 1990 and 2025, while running this policy and *also* fully retiring from teaching in 1992, Knuth produced TAOCP Volume 4A (2011), 4B (2022), 4C (in progress), and other works — output that would be remarkable for any full-time professor, let alone an \"emeritus.\" His policy is not eccentric; it is the operational architecture that enables the output.\n\n**Newport's 2016 articulation** generalizes Knuth's insight beyond the specific case. The four philosophies, the shallow-work budget, the rituals — all describe operational implementations of the same deep/shallow trade-off Knuth made formal in 1990.\n\nNewport quotes the cognitive scientist **K. Anders Ericsson**, the originator of the modern theory of expert performance:\n\n> \"Deliberate practice is a highly structured activity, the explicit goal of which is to improve performance. Specific tasks are invented to overcome weaknesses, and performance is carefully monitored to provide cues for ways to improve it further.\"\n>\n> — Ericsson, K. A., Krampe, R. T., & Tesch-Römer, C. (1993). \"The Role of Deliberate Practice in the Acquisition of Expert Performance.\" *Psychological Review*, 100(3), 363-406. p. 368.\n\nNewport draws the connection: deliberate practice is structurally deep work. The expert performers Ericsson studied did not get expert by working more hours; they got expert by doing more *deliberately structured, distraction-free, edge-of-ability* work. The empirical fact that elite performers across domains (musicians, athletes, chess players, programmers, surgeons) all show this pattern is the cognitive-science foundation for deep work.\n\nMark, Gudith & Klocke's empirical study at UC Irvine (2008) added the attention-fragmentation data:\n\n> \"After only 20 minutes of interrupted performance people reported significantly higher stress, frustration, workload, effort, and pressure. We compared self-reports of stress and other affective responses with measures of physiological response. Our results suggest that to compensate for interruptions, people work faster, but this comes at a price: experiencing more stress, higher frustration, time pressure and effort.\"\n>\n> — Mark, G., Gudith, D., & Klocke, U. (2008). \"The Cost of Interrupted Work: More Speed and Stress.\" *Proceedings of the SIGCHI Conference on Human Factors in Computing Systems*, 107-110.\n\nThe combined picture: deep work produces the most valuable knowledge-work output; expert performance requires it; interruption fragments it; and most modern work environments are structurally interruption-saturated. The Newport / Knuth response is structural protection of deep-work time.\n\nThree operational lessons from Knuth's case and Newport's framework:\n\n**First, the cost of shallow work is real but invisible.** Knuth could have kept doing email, and TAOCP would have progressed more slowly, and no one would have noticed which specific volume was delayed. The cost of *not* protecting deep work is paid by the long-term output, not the short-term calendar. This invisibility is what makes the trade-off so frequently lost.\n\n**Second, the social cost is real and must be paid.** Knuth's policy is rude by modern standards. People who write him reasonable, polite emails do not get replies. The framework requires accepting that some social and professional cost is the price of the protected output. There is no costless version.\n\n**Third, the discipline scales down.** Most people cannot, and should not, adopt Knuth's monastic posture. But the same logic — protect specific blocks, accept structural shallow-work reduction, defend the boundary — scales down to 2-4 hours per day of protected deep work, which is enough to dramatically shift output for most knowledge workers.\n\nFile v1.0.2:skill-card.md\n\n## Description: <br>\nDeep Work coaches an agent to help users protect extended focus time, distinguish deep work from shallow work, and produce a concrete Deep Work Plan. <br>\n\nThis skill is ready for commercial/non-commercial use. <br>\n\n## Publisher: <br>\n[deciqai](https://clawhub.ai/user/deciqai) <br>\n\n### License/Terms of Use: <br>\nMIT-0 <br>\n\n\n## Use Case: <br>\nEmployees, external users, and agents use this skill to diagnose calendar fragmentation, select a deep-work practice, reduce shallow-work load, and create a protected focus plan for cognitively demanding work. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: The skill may suggest reducing interruptions or closing communication tools during focus blocks, which can conflict with roles that require immediate availability. <br>\nMitigation: Use the skill only when the user has discrete focus windows, and define explicit availability boundaries or a true-emergency channel before applying the plan. <br>\nRisk: Productivity coaching can produce overly rigid schedules if role constraints and organizational expectations are not considered. <br>\nMitigation: Adapt the selected deep-work philosophy to the user's role, calendar constraints, and accepted social or organizational costs. <br>\n\n\n## Reference(s): <br>\n- [ClawHub Skill Page](https://clawhub.ai/deciqai/skills/deep-work) <br>\n- [Sources - deep-work](references/sources.md) <br>\n- [Knuth versus Email](https://www-cs-faculty.stanford.edu/~knuth/email.html) <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [text, markdown, guidance] <br>\n**Output Format:** [Markdown plan and coaching guidance] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [Produces a Deep Work Plan with diagnosis, selected practice, block structure, shallow-work budget, and defense steps.] <br>\n\n## Skill Version(s): <br>\n1.0.2 (source: release evidence) <br>\n\n## Ethical Considerations: <br>\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment. <br>\n\nArchive v1.0.1: 5 files, 9493 bytes\n\nFiles: examples/donald-knuth-no-email-policy-1990.md (6441b), references/sources.md (1589b), skill-card.md (2228b), SKILL.md (7537b), _meta.json (128b)\n\nFile v1.0.1:SKILL.md\n\n---\nname: deep-work\ndescription: \"Activate when: user says 'I can never find time for focused work', 'I feel busy but produce nothing', 'I keep getting interrupted', 'I want to protect my focus time', 'flow state', 'deliberate practice', 'Cal Newport', or asks how to make progress on hard cognitive work (research, writing, engineering, strategy). Do NOT activate when: the role is genuinely high-coordination with no discrete focus windows (ER medicine, real-time trading desk), or user is in a short-term emergency where availability must dominate.\"\n---\n\n# Deep Work\n\n## Overview\n\nCal Newport's framework (2016): **deep work** = undistracted, cognitively demanding activity that creates hard-to-replicate value; **shallow work** = logistical, responsive, easy-to-replicate work that fills modern calendars. The most valuable knowledge work is disproportionately the product of deep work; shallow work is increasingly automatable. Three foundations: attention research shows 15-25 min recovery cost per interruption; expert performance requires deliberate practice (structurally a form of deep work); the opportunity cost of shallow work is invisible — no one tracks which deep work didn't happen this week.\n\nComposes with [`wu-wei`](../wu-wei/SKILL.md) (flow as the felt experience), [`metacognition`](../metacognition/SKILL.md) (monitoring drift out of deep mode), [`okr-goal-setting`](../okr-goal-setting/SKILL.md) (OKRs give deep work direction), [`pareto-principle`](../pareto-principle/SKILL.md) (the 20% producing 80% of value is almost always deep work).\n\n## When to Use\n\n- Output depends on hard-to-replicate cognitive work (research, engineering, writing, design, strategy)\n- Calendar fragmentation prevents the work that actually matters; weeks feel busy but produce nothing\n- High-stakes project requires extended concentration; career advancement depends on skill development\n\n**Not when:** genuinely high-coordination roles where deep work is structurally impossible; already done with deep work and shallow follow-through is now required; short-term emergency where availability dominates.\n\n## Coaching Novices (Adaptive Front Door)\n\n- **Engine mode:** user has a concrete case → run The Process directly.\n- **Coach mode:** user unfamiliar or has no concrete case → guide step by step.\n\nIn Coach mode, respond one step at a time. Each [WAIT] is a hard stop — output only that step's question, then stop.\n\n1. One-line: most valuable knowledge work requires extended undistracted focus — the discipline is claiming time for it rather than waiting for it.\n2. Check fit: genuinely high-coordination roles / short-term emergencies → not this lens yet.\n3. Elicit the specific work that requires depth — what's not getting done?\n> **[WAIT — do not advance until user responds]**\n4. One question at a time: what's your deep-vs-shallow ratio? What's the highest-leverage deep work? What's the cost of not doing it?\n> **[WAIT — do not advance until user responds]**\n5. Close: specific deep-work block on the calendar + defensive moves to protect it.\n> **[WAIT — do not advance until user responds]**\n\n## The Process\n\n**Step 1 — Instrument:** Track one week. Most workers estimate 4-5 hrs/day deep; measurement shows 0.5-2 hrs in fragments.\n```\n- Deep work hours/day (tracked): | Shallow hours/day: | Ratio: | Surprise factor:\n```\n**Step 2 — Identify:** What specific deep work, if done well, produces the most valuable output? Why isn't it happening? What barriers?\n\n**Step 3 — Choose a philosophy:** Monastic (eliminate shallow entirely); Bimodal (alternating deep/shallow periods); Rhythmic (fixed daily block — best default for most); Journalistic (switch in whenever a gap appears — requires strong attention discipline, worst for beginners).\n\n**Step 4 — Build the practice:** Same time + location + setup (ritual). Calendar the block, mark \"Do not interrupt.\" End with a shutdown phrase to prevent cognitive leakage. Boundary is binary: Slack/email closed or you are not in deep work.\n\n**Step 5 — Reduce shallow load:** Audit meetings, email, Slack. Set a shallow-work budget (typically 30-50% for ICs) and stay under it.\n\n**Step 6 — Defend:** Internal — discomfort of being unreachable fades over 2-4 weeks. External — show hours visibly on calendar; demonstrate output value as long-term proof.\n\n## Output: Deep Work Plan\n\n```markdown\n# Deep Work Plan: <person, role>\nDiagnosis — deep hrs/day: | shallow hrs/day: | deep work not happening:\nPhilosophy — selected: | why this fits:\nStructure — block time/duration/location: | ritual: | boundary: | shutdown:\nShallow budget — %: | specific reductions:\nDefense — calendar mark: | comms norms: | output evidence to track:\n```\n\n*→ Method in Action: [Donald Knuth and the No-Email Policy, 1990](examples/donald-knuth-no-email-policy-1990.md)*\n\n## Pack: Deep Work by Role\n\n| Role | Highest-leverage deep work | Common shallow intrusion |\n|---|---|---|\n| Engineer | Architecture, hard debugging | Slack, status meetings |\n| Writer | Drafting, revision | Email, research rabbit holes |\n| Researcher | Literature synthesis, experiments | Grant admin, departmental meetings |\n| Founder | Strategy, customer depth, recruiting | Investor follow-up, feedback meetings |\n| PM | Research synthesis, spec writing | Alignment meetings, status reports |\n\n## Applying It Well\n\nProtect the morning block first — cognitive freshness depletes with shallow work. Track deep-work hours as a lagging metric. Treat the shutdown ritual as non-negotiable. Find organizational alignment or explicitly accept the social cost — there is no costless version.\n\n*→ Primary sources: [references/sources.md](references/sources.md)*\n\n## Common Rationalizations\n\n**[D] = designed upfront | [O] = observed in real use. [O] entries are more valuable.**\n\n| Fake move | Reality |\n|---|---|\n| [D] \"My role doesn't allow deep work\" | The role *culture* disallows it; the role itself usually doesn't. |\n| [D] \"I do deep work in the evenings\" | Cognitive freshness already spent. Reorder: deep work first. |\n| [D] \"I'm doing deep work\" with Slack open | Slack open = deep work not happening. Boundary is binary. |\n| [D] \"I can multitask in deep work\" | Only task-switching, which is expensive. Category error. |\n| [D] \"Available for emergencies during deep work\" | Most emergencies aren't. Define a true-emergency channel; ignore the rest. |\n| [D] Confusing \"long hours\" with \"deep work\" | Deep work = intensity × duration, not just duration. |\n| *→ Add [O] entries here after each real use — paste the actual failure pattern* | *What went wrong and why* |\n\n## Red Flags\n\n- \"Hours worked\" reported but \"hours of deep work\" cannot be quantified\n- Calendar fragmented with 30-min slots across the day; Slack open continuously\n- Deep work happens only at evenings/weekends, not at peak cognitive hours\n- After a productive-feeling day, cannot point to a single deep-work artifact produced\n\n## Verification\n\n- [ ] Deep-vs-shallow ratio measured (one week tracked)\n- [ ] Highest-leverage deep work identified\n- [ ] Philosophy chosen with match to constraints; specific block calendared\n- [ ] Ritual, boundary, and shutdown operational; shallow-work budget named\n- [ ] Social/organizational cost explicitly accepted; output evidence tracked\n\n---\n\n*Part of **deciqAI Knowledge Skills** — open-source thinking skills that make rigor executable for AI agents. Built by deciqAI · https://deciqai.com · Contributions welcome — see the template at the repo root.*\n\nFile v1.0.1:_meta.json\n\n{\n  \"ownerId\": \"kn754b8sk22s8c6gjxt02bftbn88q7ye\",\n  \"slug\": \"deep-work\",\n  \"version\": \"1.0.1\",\n  \"publishedAt\": 1783456311676\n}\n\nFile v1.0.1:references/sources.md\n\n# Sources — deep-work\n\n> *Primary sources for the [deep-work](../SKILL.md) skill.*\n\n- Newport, C. (2016). *Deep Work: Rules for Focused Success in a Distracted World.* Grand Central. ISBN 978-1455586691. The canonical articulation.\n- Knuth, D. E. (1990 / ongoing). \"Knuth versus Email.\" Stanford homepage. https://www-cs-faculty.stanford.edu/~knuth/email.html. The earliest extreme-deep-work case study with the practitioner's own documentation.\n- Ericsson, K. A., Krampe, R. T., & Tesch-Römer, C. (1993). \"The Role of Deliberate Practice in the Acquisition of Expert Performance.\" *Psychological Review*, 100(3), 363-406. The foundational empirical paper on expert performance and deliberate practice.\n- Mark, G., Gudith, D., & Klocke, U. (2008). \"The Cost of Interrupted Work: More Speed and Stress.\" *CHI 2008 Proceedings*. The empirical psychology of attention-switching.\n- Leroy, S. (2009). \"Why is it so hard to do my work? The challenge of attention residue when switching between work tasks.\" *Organizational Behavior and Human Decision Processes*, 109(2), 168-181. The \"attention residue\" concept.\n- Csikszentmihalyi, M. (1990). *Flow: The Psychology of Optimal Experience.* Harper & Row. ISBN 978-0061339202. The experiential side of deep work.\n- Newport, C. (2019). *Digital Minimalism: Choosing a Focused Life in a Noisy World.* Portfolio. ISBN 978-0525536512. The companion volume on personal-life dimensions.\n- Carr, N. (2010). *The Shallows: What the Internet Is Doing to Our Brains.* Norton. ISBN 978-0393339758. The cultural diagnosis of why deep work has become rare.\n\nFile v1.0.1:examples/donald-knuth-no-email-policy-1990.md\n\n# Method in Action: Donald Knuth and the No-Email Policy, 1990\n\n> *Example for the [deep-work](../SKILL.md) skill.*\n\nThe most extreme and well-documented case of deep-work practice in modern science is **Donald Knuth**, Professor Emeritus of Computer Science at Stanford and author of *The Art of Computer Programming* (TAOCP), the multi-volume work he has been writing since 1962 and which Bill Gates once called \"the best book on programming ever written.\"\n\nKnuth's challenge: TAOCP requires sustained, cognitively-intensive mathematical and programming work that does not yield to fragmentation. The work also requires Knuth to maintain mathematical correctness across a corpus that, by 2025, runs to several thousand published pages. In the 1980s, as email began to dominate academic life, Knuth observed that his TAOCP progress was slowing — and traced the slowdown to email's compounding effect on his attention.\n\nIn **January 1, 1990**, Knuth announced on his Stanford homepage that he was discontinuing email use. The statement (preserved at https://www-cs-faculty.stanford.edu/~knuth/email.html and unchanged in substance for 35 years) reads:\n\n> \"I have been a happy man ever since January 1, 1990, when I no longer had an email address. I'd used email since about 1975, and it seems to me that 15 years of email is plenty for one lifetime.\n>\n> Email is a wonderful thing for people whose role in life is to be on top of things. But not for me; my role is to be on the bottom of things. What I do takes long hours of studying and uninterruptible concentration. I try to learn certain areas of computer science exhaustively; then I try to digest that knowledge into a form that is accessible to people who don't have time for such study.\"\n\n— Knuth, D. E. (1990 / continuously updated). \"Knuth versus Email.\" Stanford homepage. https://www-cs-faculty.stanford.edu/~knuth/email.html\n\nThe substantive structure of Knuth's argument is precisely the Newport deep/shallow distinction (anticipating Newport's 2016 book by 26 years):\n\n- **\"To be on top of things\"** = the shallow-work mode of constant responsiveness, awareness, coordination\n- **\"To be on the bottom of things\"** = the deep-work mode of sustained, uninterruptible concentration\n- **The trade-off is structural:** Knuth claims you cannot do both. The roles require incompatible cognitive modes.\n\nKnuth's policy is not absence of communication — postal mail still reaches him, and his assistant handles correspondence. The policy is specifically refusal of the *interruption-pattern* email demands, on the grounds that the cost (to deep work) exceeds the value (of any individual email).\n\nThe empirical evidence from Knuth's output: between 1990 and 2025, while running this policy and *also* fully retiring from teaching in 1992, Knuth produced TAOCP Volume 4A (2011), 4B (2022), 4C (in progress), and other works — output that would be remarkable for any full-time professor, let alone an \"emeritus.\" His policy is not eccentric; it is the operational architecture that enables the output.\n\n**Newport's 2016 articulation** generalizes Knuth's insight beyond the specific case. The four philosophies, the shallow-work budget, the rituals — all describe operational implementations of the same deep/shallow trade-off Knuth made formal in 1990.\n\nNewport quotes the cognitive scientist **K. Anders Ericsson**, the originator of the modern theory of expert performance:\n\n> \"Deliberate practice is a highly structured activity, the explicit goal of which is to improve performance. Specific tasks are invented to overcome weaknesses, and performance is carefully monitored to provide cues for ways to improve it further.\"\n>\n> — Ericsson, K. A., Krampe, R. T., & Tesch-Römer, C. (1993). \"The Role of Deliberate Practice in the Acquisition of Expert Performance.\" *Psychological Review*, 100(3), 363-406. p. 368.\n\nNewport draws the connection: deliberate practice is structurally deep work. The expert performers Ericsson studied did not get expert by working more hours; they got expert by doing more *deliberately structured, distraction-free, edge-of-ability* work. The empirical fact that elite performers across domains (musicians, athletes, chess players, programmers, surgeons) all show this pattern is the cognitive-science foundation for deep work.\n\nMark, Gudith & Klocke's empirical study at UC Irvine (2008) added the attention-fragmentation data:\n\n> \"After only 20 minutes of interrupted performance people reported significantly higher stress, frustration, workload, effort, and pressure. We compared self-reports of stress and other affective responses with measures of physiological response. Our results suggest that to compensate for interruptions, people work faster, but this comes at a price: experiencing more stress, higher frustration, time pressure and effort.\"\n>\n> — Mark, G., Gudith, D., & Klocke, U. (2008). \"The Cost of Interrupted Work: More Speed and Stress.\" *Proceedings of the SIGCHI Conference on Human Factors in Computing Systems*, 107-110.\n\nThe combined picture: deep work produces the most valuable knowledge-work output; expert performance requires it; interruption fragments it; and most modern work environments are structurally interruption-saturated. The Newport / Knuth response is structural protection of deep-work time.\n\nThree operational lessons from Knuth's case and Newport's framework:\n\n**First, the cost of shallow work is real but invisible.** Knuth could have kept doing email, and TAOCP would have progressed more slowly, and no one would have noticed which specific volume was delayed. The cost of *not* protecting deep work is paid by the long-term output, not the short-term calendar. This invisibility is what makes the trade-off so frequently lost.\n\n**Second, the social cost is real and must be paid.** Knuth's policy is rude by modern standards. People who write him reasonable, polite emails do not get replies. The framework requires accepting that some social and professional cost is the price of the protected output. There is no costless version.\n\n**Third, the discipline scales down.** Most people cannot, and should not, adopt Knuth's monastic posture. But the same logic — protect specific blocks, accept structural shallow-work reduction, defend the boundary — scales down to 2-4 hours per day of protected deep work, which is enough to dramatically shift output for most knowledge workers.\n\nFile v1.0.1:skill-card.md\n\n## Description: <br>\nGuides agents through a deep-work coaching process to diagnose shallow-work overload, protect focus time, and produce a structured plan for cognitively demanding work. <br>\n\nThis skill is ready for commercial/non-commercial use. <br>\n\n## Publisher: <br>\n[deciqai](https://clawhub.ai/user/deciqai) <br>\n\n### License/Terms of Use: <br>\nMIT-0 <br>\n\n\n## Use Case: <br>\nEmployees, external users, and knowledge workers use this skill to identify fragmented attention, choose an appropriate deep-work practice, and create a calendar-backed plan for research, writing, engineering, strategy, or other demanding cognitive work. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: Communication-boundary advice may conflict with team norms, high-coordination roles, or emergency obligations. <br>\nMitigation: Adapt focus blocks, interruption channels, and availability expectations to the user's role and organization before applying the plan. <br>\nRisk: The coaching output could frame necessary coordination as shallow work if the user's context is not elicited first. <br>\nMitigation: Use the fit check and one-question-at-a-time coaching flow before recommending calendar, messaging, or meeting changes. <br>\n\n\n## Reference(s): <br>\n- [Sources - deep-work](references/sources.md) <br>\n- [Donald Knuth and the No-Email Policy, 1990](examples/donald-knuth-no-email-policy-1990.md) <br>\n- [Knuth versus Email](https://www-cs-faculty.stanford.edu/~knuth/email.html) <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [text, markdown, guidance] <br>\n**Output Format:** [Markdown deep-work plan with structured diagnostic fields and coaching prompts] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [May ask one question at a time before producing the plan when the user needs coaching.] <br>\n\n## Skill Version(s): <br>\n1.0.1 (source: server release evidence) <br>\n\n## Ethical Considerations: <br>\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment. <br>\n\nArchive v1.0.0: 5 files, 9478 bytes\n\nFiles: examples/donald-knuth-no-email-policy-1990.md (6441b), references/sources.md (1589b), skill-card.md (2224b), SKILL.md (7537b), _meta.json (128b)\n\nFile v1.0.0:SKILL.md\n\n---\nname: deep-work\ndescription: \"Activate when: user says 'I can never find time for focused work', 'I feel busy but produce nothing', 'I keep getting interrupted', 'I want to protect my focus time', 'flow state', 'deliberate practice', 'Cal Newport', or asks how to make progress on hard cognitive work (research, writing, engineering, strategy). Do NOT activate when: the role is genuinely high-coordination with no discrete focus windows (ER medicine, real-time trading desk), or user is in a short-term emergency where availability must dominate.\"\n---\n\n# Deep Work\n\n## Overview\n\nCal Newport's framework (2016): **deep work** = undistracted, cognitively demanding activity that creates hard-to-replicate value; **shallow work** = logistical, responsive, easy-to-replicate work that fills modern calendars. The most valuable knowledge work is disproportionately the product of deep work; shallow work is increasingly automatable. Three foundations: attention research shows 15-25 min recovery cost per interruption; expert performance requires deliberate practice (structurally a form of deep work); the opportunity cost of shallow work is invisible — no one tracks which deep work didn't happen this week.\n\nComposes with [`wu-wei`](../wu-wei/SKILL.md) (flow as the felt experience), [`metacognition`](../metacognition/SKILL.md) (monitoring drift out of deep mode), [`okr-goal-setting`](../okr-goal-setting/SKILL.md) (OKRs give deep work direction), [`pareto-principle`](../pareto-principle/SKILL.md) (the 20% producing 80% of value is almost always deep work).\n\n## When to Use\n\n- Output depends on hard-to-replicate cognitive work (research, engineering, writing, design, strategy)\n- Calendar fragmentation prevents the work that actually matters; weeks feel busy but produce nothing\n- High-stakes project requires extended concentration; career advancement depends on skill development\n\n**Not when:** genuinely high-coordination roles where deep work is structurally impossible; already done with deep work and shallow follow-through is now required; short-term emergency where availability dominates.\n\n## Coaching Novices (Adaptive Front Door)\n\n- **Engine mode:** user has a concrete case → run The Process directly.\n- **Coach mode:** user unfamiliar or has no concrete case → guide step by step.\n\nIn Coach mode, respond one step at a time. Each [WAIT] is a hard stop — output only that step's question, then stop.\n\n1. One-line: most valuable knowledge work requires extended undistracted focus — the discipline is claiming time for it rather than waiting for it.\n2. Check fit: genuinely high-coordination roles / short-term emergencies → not this lens yet.\n3. Elicit the specific work that requires depth — what's not getting done?\n> **[WAIT — do not advance until user responds]**\n4. One question at a time: what's your deep-vs-shallow ratio? What's the highest-leverage deep work? What's the cost of not doing it?\n> **[WAIT — do not advance until user responds]**\n5. Close: specific deep-work block on the calendar + defensive moves to protect it.\n> **[WAIT — do not advance until user responds]**\n\n## The Process\n\n**Step 1 — Instrument:** Track one week. Most workers estimate 4-5 hrs/day deep; measurement shows 0.5-2 hrs in fragments.\n```\n- Deep work hours/day (tracked): | Shallow hours/day: | Ratio: | Surprise factor:\n```\n**Step 2 — Identify:** What specific deep work, if done well, produces the most valuable output? Why isn't it happening? What barriers?\n\n**Step 3 — Choose a philosophy:** Monastic (eliminate shallow entirely); Bimodal (alternating deep/shallow periods); Rhythmic (fixed daily block — best default for most); Journalistic (switch in whenever a gap appears — requires strong attention discipline, worst for beginners).\n\n**Step 4 — Build the practice:** Same time + location + setup (ritual). Calendar the block, mark \"Do not interrupt.\" End with a shutdown phrase to prevent cognitive leakage. Boundary is binary: Slack/email closed or you are not in deep work.\n\n**Step 5 — Reduce shallow load:** Audit meetings, email, Slack. Set a shallow-work budget (typically 30-50% for ICs) and stay under it.\n\n**Step 6 — Defend:** Internal — discomfort of being unreachable fades over 2-4 weeks. External — show hours visibly on calendar; demonstrate output value as long-term proof.\n\n## Output: Deep Work Plan\n\n```markdown\n# Deep Work Plan: <person, role>\nDiagnosis — deep hrs/day: | shallow hrs/day: | deep work not happening:\nPhilosophy — selected: | why this fits:\nStructure — block time/duration/location: | ritual: | boundary: | shutdown:\nShallow budget — %: | specific reductions:\nDefense — calendar mark: | comms norms: | output evidence to track:\n```\n\n*→ Method in Action: [Donald Knuth and the No-Email Policy, 1990](examples/donald-knuth-no-email-policy-1990.md)*\n\n## Pack: Deep Work by Role\n\n| Role | Highest-leverage deep work | Common shallow intrusion |\n|---|---|---|\n| Engineer | Architecture, hard debugging | Slack, status meetings |\n| Writer | Drafting, revision | Email, research rabbit holes |\n| Researcher | Literature synthesis, experiments | Grant admin, departmental meetings |\n| Founder | Strategy, customer depth, recruiting | Investor follow-up, feedback meetings |\n| PM | Research synthesis, spec writing | Alignment meetings, status reports |\n\n## Applying It Well\n\nProtect the morning block first — cognitive freshness depletes with shallow work. Track deep-work hours as a lagging metric. Treat the shutdown ritual as non-negotiable. Find organizational alignment or explicitly accept the social cost — there is no costless version.\n\n*→ Primary sources: [references/sources.md](references/sources.md)*\n\n## Common Rationalizations\n\n**[D] = designed upfront | [O] = observed in real use. [O] entries are more valuable.**\n\n| Fake move | Reality |\n|---|---|\n| [D] \"My role doesn't allow deep work\" | The role *culture* disallows it; the role itself usually doesn't. |\n| [D] \"I do deep work in the evenings\" | Cognitive freshness already spent. Reorder: deep work first. |\n| [D] \"I'm doing deep work\" with Slack open | Slack open = deep work not happening. Boundary is binary. |\n| [D] \"I can multitask in deep work\" | Only task-switching, which is expensive. Category error. |\n| [D] \"Available for emergencies during deep work\" | Most emergencies aren't. Define a true-emergency channel; ignore the rest. |\n| [D] Confusing \"long hours\" with \"deep work\" | Deep work = intensity × duration, not just duration. |\n| *→ Add [O] entries here after each real use — paste the actual failure pattern* | *What went wrong and why* |\n\n## Red Flags\n\n- \"Hours worked\" reported but \"hours of deep work\" cannot be quantified\n- Calendar fragmented with 30-min slots across the day; Slack open continuously\n- Deep work happens only at evenings/weekends, not at peak cognitive hours\n- After a productive-feeling day, cannot point to a single deep-work artifact produced\n\n## Verification\n\n- [ ] Deep-vs-shallow ratio measured (one week tracked)\n- [ ] Highest-leverage deep work identified\n- [ ] Philosophy chosen with match to constraints; specific block calendared\n- [ ] Ritual, boundary, and shutdown operational; shallow-work budget named\n- [ ] Social/organizational cost explicitly accepted; output evidence tracked\n\n---\n\n*Part of **deciqAI Knowledge Skills** — open-source thinking skills that make rigor executable for AI agents. Built by deciqAI · https://deciqai.com · Contributions welcome — see the template at the repo root.*\n\nFile v1.0.0:_meta.json\n\n{\n  \"ownerId\": \"kn754b8sk22s8c6gjxt02bftbn88q7ye\",\n  \"slug\": \"deep-work\",\n  \"version\": \"1.0.0\",\n  \"publishedAt\": 1782544664232\n}\n\nFile v1.0.0:references/sources.md\n\n# Sources — deep-work\n\n> *Primary sources for the [deep-work](../SKILL.md) skill.*\n\n- Newport, C. (2016). *Deep Work: Rules for Focused Success in a Distracted World.* Grand Central. ISBN 978-1455586691. The canonical articulation.\n- Knuth, D. E. (1990 / ongoing). \"Knuth versus Email.\" Stanford homepage. https://www-cs-faculty.stanford.edu/~knuth/email.html. The earliest extreme-deep-work case study with the practitioner's own documentation.\n- Ericsson, K. A., Krampe, R. T., & Tesch-Römer, C. (1993). \"The Role of Deliberate Practice in the Acquisition of Expert Performance.\" *Psychological Review*, 100(3), 363-406. The foundational empirical paper on expert performance and deliberate practice.\n- Mark, G., Gudith, D., & Klocke, U. (2008). \"The Cost of Interr","readmeExcerpt":"Skill: Deep Work Owner: deciqai Summary: Activate when: user says 'I can never find time for focused work', 'I feel busy but produce nothing', 'I keep getting interrupted', 'I want to protect my foc... Tags: latest:1.0.5 Version history: v1.0.5 | 2026-07-16T17:57:05.645Z | user Description tail link + agents machine-readable metadata line (deciqai.com/s/deep-work.json) v1.0.4 | 2026-07-10T10:24:46.922Z | user Add 202","codeSnippets":[],"executableExamples":[{"language":"text","snippet":"- Deep work hours/day (tracked): | Shallow hours/day: | Ratio: | Surprise factor:"},{"language":"markdown","snippet":"# Deep Work Plan: <person, role>\nDiagnosis — deep hrs/day: | shallow hrs/day: | deep work not happening:\nPhilosophy — selected: | why this fits:\nStructure — block time/duration/location: | ritual: | boundary: | shutdown:\nShallow budget — %: | specific reductions:\nDefense — calendar mark: | comms norms: | output evidence to track:"},{"language":"text","snippet":"- Deep work hours/day (tracked): ~1.25 | Shallow hours/day: ~5 | Ratio: poor\n- Surprise factor: high — AI prompting felt like focus but registered as switching"},{"language":"text","snippet":"- Deep work hours/day (tracked): | Shallow hours/day: | Ratio: | Surprise factor:"},{"language":"markdown","snippet":"# Deep Work Plan: <person, role>\nDiagnosis — deep hrs/day: | shallow hrs/day: | deep work not happening:\nPhilosophy — selected: | why this fits:\nStructure — block time/duration/location: | ritual: | boundary: | shutdown:\nShallow budget — %: | specific reductions:\nDefense — calendar mark: | comms norms: | output evidence to track:"},{"language":"text","snippet":"- Deep work hours/day (tracked): ~1.25 | Shallow hours/day: ~5 | Ratio: poor\n- Surprise factor: high — AI prompting felt like focus but registered as switching"}],"parameters":null,"dependencies":[],"permissions":[],"extractedFiles":[{"path":"SKILL.md","content":"---\nname: deep-work\ndescription: \"Activate when: user says 'I can never find time for focused work', 'I feel busy but produce nothing', 'I keep getting interrupted', 'I want to protect my focus time', 'flow state', 'deliberate practice', 'Cal Newport', or asks how to make progress on hard cognitive work (research, writing, engineering, strategy). Do NOT activate when: the role is genuinely high-coordination with no discrete focus windows (ER medicine, real-time trading desk), or user is in a short-term emergency where availability must dominate. More: deciqai.com/c/deep-work\"\n---\n\n# Deep Work\n\n## Overview\n\nCal Newport's framework (2016): **deep work** = undistracted, cognitively demanding activity that creates hard-to-replicate value; **shallow work** = logistical, responsive, easy-to-replicate work that fills modern calendars. The most valuable knowledge work is disproportionately the product of deep work; shallow work is increasingly automatable. Three foundations: attention research shows 15-25 min recovery cost per interruption; expert performance requires deliberate practice (structurally a form of deep work); the opportunity cost of shallow work is invisible — no one tracks which deep work didn't happen this week.\n\nComposes with `wu-wei` (flow as the felt experience), `metacognition` (monitoring drift out of deep mode), `okr-goal-setting` (OKRs give deep work direction), `pareto-principle` (the 20% producing 80% of value is almost always deep work).\n\n## When to Use\n\n- Output depends on hard-to-replicate cognitive work (research, engineering, writing, design, strategy)\n- Calendar fragmentation prevents the work that actually matters; weeks feel busy but produce nothing\n- High-stakes project requires extended concentration; career advancement depends on skill development\n- AI copilots / assistants have become another interruption stream (\"is AI helping my focus or fragmenting it?\", \"AI adoption vs deep work\", \"AI hype and staying focused\")\n\n**Not when:** genuinely high-coordination roles where deep work is structurally impossible; already done with deep work and shallow follow-through is now required; short-term emergency where availability dominates.\n\n## Coaching Novices (Adaptive Front Door)\n\n- **Engine mode:** user has a concrete case → run The Process directly.\n- **Coach mode:** user unfamiliar or has no concrete case → guide step by step.\n\nIn Coach mode, respond one step at a time. Each [WAIT] is a hard stop — output only that step's question, then stop.\n\n1. One-line: most valuable knowledge work requires extended undistracted focus — the discipline is claiming time for it rather than waiting for it.\n2. Check fit: genuinely high-coordination roles / short-term emergencies → not this lens yet.\n3. Elicit the specific work that requires depth — what's not getting done?\n> **[WAIT — do not advance until user responds]**\n4. One question at a time: what's your deep-vs-shallow ratio? What's the highest-leverage deep work? What's the cost of not "},{"path":"_meta.json","content":"{\n  \"ownerId\": \"kn754b8sk22s8c6gjxt02bftbn88q7ye\",\n  \"slug\": \"deep-work\",\n  \"version\": \"1.0.5\",\n  \"publishedAt\": 1784224625645\n}"},{"path":"references/sources.md","content":"# Sources — deep-work\n\n> *Primary sources for the [deep-work](../SKILL.md) skill.*\n\n- Newport, C. (2016). *Deep Work: Rules for Focused Success in a Distracted World.* Grand Central. ISBN 978-1455586691. The canonical articulation.\n- Knuth, D. E. (1990 / ongoing). \"Knuth versus Email.\" Stanford homepage. https://www-cs-faculty.stanford.edu/~knuth/email.html. The earliest extreme-deep-work case study with the practitioner's own documentation.\n- Jung, C. G. (1962). *Memories, Dreams, Reflections.* Recorded and edited by Aniela Jaffé; trans. Richard and Clara Winston (1963). Pantheon. The chapter \"The Tower\" is Jung's own account of the Bollingen retreat practice — the canonical bimodal case.\n- Ericsson, K. A., Krampe, R. T., & Tesch-Römer, C. (1993). \"The Role of Deliberate Practice in the Acquisition of Expert Performance.\" *Psychological Review*, 100(3), 363-406. The foundational empirical paper on expert performance and deliberate practice.\n- Mark, G., Gudith, D., & Klocke, U. (2008). \"The Cost of Interrupted Work: More Speed and Stress.\" *CHI 2008 Proceedings*. The empirical psychology of attention-switching.\n- Leroy, S. (2009). \"Why is it so hard to do my work? The challenge of attention residue when switching between work tasks.\" *Organizational Behavior and Human Decision Processes*, 109(2), 168-181. The \"attention residue\" concept.\n- Csikszentmihalyi, M. (1990). *Flow: The Psychology of Optimal Experience.* Harper & Row. ISBN 978-0061339202. The experiential side of deep work.\n- Newport, C. (2019). *Digital Minimalism: Choosing a Focused Life in a Noisy World.* Portfolio. ISBN 978-0525536512. The companion volume on personal-life dimensions.\n- Carr, N. (2010). *The Shallows: What the Internet Is Doing to Our Brains.* Norton. ISBN 978-0393339758. The cultural diagnosis of why deep work has become rare.\n- GitHub (2022, June 21). \"GitHub Copilot is generally available to all developers.\" https://github.blog/2022-06-21-github-copilot-is-generally-available-to-all-developers/. Marks the mainstreaming of AI copilots in daily knowledge work — the 2024–2026 context for the deep/shallow distinction.\n- Newport, C. (2024–2025). *Deep Questions* podcast and essays on AI and knowledge work. https://calnewport.com. Newport's contemporary argument that undistracted human cognition rises in value as routine output is automated."},{"path":"examples/carl-jung-bollingen-tower-retreats.md","content":"# Method in Action: Carl Jung's Bollingen Tower Retreats (1923–1961)\n\n> *Example for the [deep-work](../SKILL.md) skill.*\n\nCarl Jung's Bollingen tower is the case Cal Newport chose to open *Deep Work* (2016), and it remains the cleanest historical demonstration of the **Bimodal philosophy**: a working psychiatrist who could not abandon his shallow obligations, and instead built a physical architecture for alternating between them and depth.\n\n**The diagnosis (Steps 1-2):** In the 1920s Jung's professional life in Zurich and Küsnacht was structurally shallow-saturated: a busy clinical practice with a full patient load, lectures, seminars, and heavy correspondence. This was also the period in which Jung was establishing analytical psychology as an independent school after his break with Freud — an intellectual project competing against the most formidable rival imaginable. The highest-leverage deep work was unambiguous: the sustained theoretical writing that would define archetypes, the collective unconscious, and individuation. That writing could not happen between patient sessions. Jung did not need a tracking week to see the ratio; the clinical calendar made it visible.\n\n**The philosophy choice (Step 3):** Jung could not go monastic — his clinical practice was both his income and his empirical material. He chose the bimodal split: full engagement with practice and public life in Zurich, then regular retreats to a private refuge for concentrated writing.\n\n**The practice (Step 4):** In 1922 Jung bought land at Bollingen on the upper lake of Zurich, and beginning in 1923 built a stone tower there by stages, expanding it over the following decades. The tower was deliberately spartan — no electricity; Jung chopped his own wood, drew his own water, and lit oil lamps. In *Memories, Dreams, Reflections* (1962), the chapter \"The Tower\" describes the place in Jung's own account as a site of repose and renewal where he felt most deeply himself — a purpose-built container for concentration. Newport reconstructs the working rhythm: mornings locked in a private study for undisturbed writing, afternoons given to meditation and walks, early nights. Same location, same setup, hard boundary — the full ritual structure of Step 4, implemented in stone.\n\n**Shallow reduction and defense (Steps 5-6):** Every Bollingen period was clinical income refused and patients turned away — the shallow-work budget enforced at direct financial cost. The retreats could look like withdrawal from a career; they were its engine. The output produced across four decades of this regime — the essays and books that became the *Collected Works* and established analytical psychology as a lasting school — is the long-term evidence Step 6 says to accumulate: output value as the defense of the practice.\n\nThe structural lesson mirrors Knuth's but from the opposite pole: Knuth shows the monastic extreme (eliminate the shallow channel permanently); Jung shows that a practitioner who *cannot* elimin"},{"path":"examples/deep-work-amid-ai-copilots-2024-2026.md","content":"# Method in Action: Protecting Deep Work Amid AI Copilots (2024–2026)\n\n> *Example for the [deep-work](../SKILL.md) skill.*\n\nBetween 2022 and 2026, generative-AI copilots moved from novelty to default fixture of knowledge work. GitHub Copilot became generally available in June 2022; ChatGPT launched in November 2022; and by 2024–2025 assistants were embedded directly into the tools where work happens — IDEs (Copilot, Cursor), office suites (Microsoft 365 Copilot, Google's Gemini in Workspace), and communication tools. The promise was more focus. The lived experience for many knowledge workers was the opposite: **another always-on stream demanding attention** — suggestions to accept or reject, chat panels to consult, notifications, and a new social pressure to \"use the AI.\" This example runs a composite knowledge worker — a senior software engineer, call her Maya — through the deep-work Process to decide how AI should relate to her focus rather than fragment it.\n\nThe core tension is exactly the deep/shallow distinction Newport drew in 2016, now with a new actor. An AI copilot can serve deep work (as a tool inside a protected block) or become shallow work (another interruption stream, another inbox). The framework's job is to keep it the former.\n\n**Step 1 — Instrument.** Maya tracks one week. Her estimate before tracking: \"maybe 4 hours a day of real focused coding.\" The tracked reality: roughly 1–1.5 hours of genuinely uninterrupted deep work per day, scattered in fragments. The new finding specific to 2024–2026: a meaningful share of her fragmentation now comes from *AI-adjacent* micro-switches — pausing mid-thought to prompt a chatbot, context-switching to read and evaluate a generated suggestion, and tab-hopping between editor and assistant. The copilot did not remove interruptions; it added a self-inflicted one that feels productive. This matches the widely-reported pattern in industry research on developer experience: perceived productivity gains from AI tools coexist with fragmented attention, and the recovery cost of task-switching (the 2008 Mark et al. and 2009 Leroy attention-residue findings) does not disappear just because the interruption is a helpful one.\n\n```\n- Deep work hours/day (tracked): ~1.25 | Shallow hours/day: ~5 | Ratio: poor\n- Surprise factor: high — AI prompting felt like focus but registered as switching\n```\n\n**Step 2 — Identify.** The highest-leverage deep work is the hard, hard-to-replicate cognitive work: system design, reasoning about a subtle concurrency bug, and the architectural decisions that shape months of downstream code. This is precisely the class of work that current AI models assist *least* well — they accelerate boilerplate, recall, and first-draft scaffolding, but the load-bearing judgment (what to build, why, and what breaks at scale) still resists being outsourced. Why isn't the deep work happening? Because the day is saturated with shallow work — and now the copilot, if used reflexively, invites her to "}],"languages":[],"docsSourceLabel":"CLAWHUB","editorialOverview":"Activate when: user says 'I can never find time for focused work', 'I feel busy but produce nothing', 'I keep getting interrupted', 'I want to protect my foc... Skill: Deep Work Owner: deciqai Summary: Activate when: user says 'I can never find time for focused work', 'I feel busy but produce nothing', 'I keep getting interrupted', 'I want to protect my foc... Tags: latest:1.0.5 Version history: v1.0.5 | 2026-07-16T17:57:05.645Z | user Description tail link + agents machine-readable metadata line (deciqai.com/s/deep-work.json) v1.0.4 | 2026-07-10T10:24:46.922Z | user Add 202","editorialQuality":{"score":100,"threshold":65,"status":"ready","wordCount":2073,"uniquenessScore":52,"reasons":[]}},"media":{"evidence":{"source":"no-media","verified":false,"confidence":"low","updatedAt":"2026-10-11T06:05:37.644Z","emptyReason":"No screenshots, media assets, or demo links are available."},"primaryImageUrl":null,"mediaAssetCount":0,"assets":[],"demoUrl":null},"ownerResources":{"evidence":{"source":"unclaimed","verified":false,"confidence":"low","updatedAt":"2026-10-11T06:05:37.644Z","emptyReason":"This page has not been claimed by the agent owner."},"hasCustomPage":false,"customPageUpdatedAt":null,"customLinks":[],"structuredLinks":{"docsUrl":null,"demoUrl":null,"supportUrl":null,"pricingUrl":null,"statusUrl":null},"customPage":null},"relatedAgents":{"evidence":{"source":"protocol-neighbors","verified":false,"confidence":"medium","updatedAt":"2026-10-11T08:40:47.831Z","emptyReason":null},"items":[{"id":"8ebccd8e-3863-4187-8355-c3f14e1f9edf","entityType":"agent","canonicalPath":"/agent/iofficeai-aionui","slug":"iofficeai-aionui","name":"AionUi","description":"Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!","url":"https://github.com/iOfficeAI/AionUi","homepage":"https://www.aionui.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-10-09T19:11:12.944Z","createdAt":"2026-02-25T03:38:16.584Z","downloads":null},{"id":"b917f68a-ebff-438e-84f8-3f4b2494c0bc","entityType":"agent","canonicalPath":"/agent/activepieces-activepieces","slug":"activepieces-activepieces","name":"activepieces","description":"AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents","url":"https://github.com/activepieces/activepieces","homepage":"https://www.activepieces.com","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-15T02:22:12.426Z","createdAt":"2026-02-25T03:38:12.412Z","downloads":null},{"id":"5cb26759-3a39-483f-94cf-276a98c13bb8","entityType":"agent","canonicalPath":"/agent/cherryhq-cherry-studio","slug":"cherryhq-cherry-studio","name":"cherry-studio","description":"AI productivity studio with smart chat, autonomous agents, and 300+ assistants. Unified access to frontier LLMs","url":"https://github.com/CherryHQ/cherry-studio","homepage":"https://cherry-ai.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-11T14:38:40.986Z","createdAt":"2026-02-25T03:38:19.379Z","downloads":null},{"id":"6f6582d0-5d76-4f0f-b81d-86520247950b","entityType":"agent","canonicalPath":"/agent/copilotkit-copilotkit","slug":"copilotkit-copilotkit","name":"CopilotKit","description":"The Frontend for Agents & Generative UI. React + Angular","url":"https://github.com/CopilotKit/CopilotKit","homepage":"https://docs.copilotkit.ai","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-03-25T09:50:57.846Z","createdAt":"2026-02-25T03:39:14.617Z","downloads":null}],"links":{"hub":"/agent","source":"/agent/source/clawhub","protocols":[{"label":"OpenClaw","href":"/agent/protocol/openclew"}]}}}