Agent Skillsmohitagw15856/pm-claude-skills › deep-work-blocking

deep-work-blocking

GitHub

帮助用户设计可持续的深度工作块,匹配真实精力高峰,设定防御规则抵御干扰,并建立进入仪式以减少启动损耗。适用于解决时间被会议侵占、计划无法执行或专注力浪费的问题。

exports/openclaw/deep-work-blocking/SKILL.md mohitagw15856/pm-claude-skills

Trigger Scenarios

我的日历没有留出思考时间 我安排了深度工作时间但总是被打断 如何安排深度工作才能不被会议吃掉 我设置了时间块但最后都浪费了

Install

npx skills add mohitagw15856/pm-claude-skills --skill deep-work-blocking -g -y
More Options

Non-standard path

npx skills add https://github.com/mohitagw15856/pm-claude-skills/tree/main/exports/openclaw/deep-work-blocking -g -y

Use without installing

npx skills use mohitagw15856/pm-claude-skills@deep-work-blocking

指定 Agent (Claude Code)

npx skills add mohitagw15856/pm-claude-skills --skill deep-work-blocking -a claude-code -g -y

安装 repo 全部 skill

npx skills add mohitagw15856/pm-claude-skills --all -g -y

预览 repo 内 skill

npx skills add mohitagw15856/pm-claude-skills --list

SKILL.md

Frontmatter
{
    "name": "deep-work-blocking",
    "homepage": "https:\/\/mohitagw15856.github.io\/pm-claude-skills\/skill\/deep-work-blocking.html",
    "metadata": {
        "openclaw": {
            "emoji": "🧠"
        }
    },
    "description": "Protect focus time that actually survives the week — the block placement matched to real energy hours, the defense rules (what moves a block, what never), the entry ritual that beats the blank-stare start, and the honest sizing that stops 8-hour fantasy blocks. Use when asked block focus time that keeps getting eaten, when should I schedule deep work, my calendar has no room to think, or I block time and then waste it. Produces the block design, the defense tiers, the entry ritual, and the meeting-culture negotiation."
}

Deep Work Blocking Skill

Focus blocks fail three ways: placed wrong (2pm slump hosting the hardest work), defended badly (the block that moves for every invite is decoration with a border color), and entered badly (twenty minutes of warmup-shuffling inside a 90-minute block is a 70-minute block wearing a lie). The design fixes all three: blocks land on the user's actual high-energy hours (energy-scheduling supplies the map), carry explicit defense tiers (what outranks them — almost nothing — and the decline scripts), and start with an entry ritual — the named task waiting, the environment pre-set — because a block is a container, and containers need contents chosen before the clock starts.

What This Skill Produces

  • The block design — count, length (90–120 min beats the 8-hour fantasy), and placement on real energy hours
  • The defense tiers — what moves a block (genuine emergencies, defined), what never does, and the decline scripts
  • The entry ritual — the task named the day before, the environment checklist, the first-five-minutes rule
  • The culture negotiation — making blocks legible to the team (the shared norm beats the solo fight)

Required Inputs

Ask for these if not provided:

  • The energy reality — when the user's genuinely sharp hours fall (the honest answer, not the aspirational one); blocks on slump hours produce guilt, not work
  • The calendar's constraints — the immovable meetings, the team's collaboration hours, the time zone spread; blocks live in the real grid
  • The work that needs the blocks — the big-three outcomes (weekly-review-ritual) the blocks exist to serve; blocks without assigned work become email time with the door closed
  • The interruption culture — can a block survive here socially? The negotiation section scales to the actual environment

Framework: The Blocking Rules

  1. Size honestly, place on peaks: 90–120 minutes is the sustainable unit (attention's real budget); two such blocks is a strong day. The 8-hour focus fantasy collapses by 11am and discredits the practice. Placement follows the energy map — the best hours go to the hardest work first, before the calendar's entropy claims them (recurring-meeting-pruner reclaims supply this space).
  2. Defense tiers, pre-decided: Tier 1 (never moves): the two weekly anchor blocks — invites get the script: "I have a commitment then — Thursday 2pm works?" (a block IS a commitment; the script just declines to itemize it). Tier 2 (moves for named things): the flex blocks, moved forward in the same week, never deleted. The emergency definition is written: production-down and boss-says-now qualify; "quick sync?" does not.
  3. The entry ritual kills the warmup tax: the day before, the block gets its named task ("draft sections 2–3," not "work on the doc") · entry checklist: notifications off, the one document open, phone elsewhere · the first-five-minutes rule: start on the named task immediately, badly if necessary — momentum converts; browsing "to warm up" evaporates blocks whole.
  4. Blocks are legible, not secret: the calendar shows "Focus block" (visible, normalized), the team knows the pattern ("mornings I'm deep, afternoons I'm reachable" — working-agreements material), and the async norms (async-update-format) carry what would have interrupted. The solo fight against a synchronous culture loses; the negotiated norm holds.
  5. The block reviews itself: each block ends with 60 seconds — did the named task move? If blocks keep producing nothing, the diagnosis tree runs: wrong hours (re-place), wrong sizing (shrink), vague tasks (the naming discipline), or leaks (the defense failed — count what actually interrupted). Blocks that fail silently get quietly deleted by their owner within a month; the review is the early-warning.

Output Format

Deep Work Design: [name] — [N] blocks/week

The Blocks

[Day × time × tier · placed on: (the energy map's peaks) · serving: (the big three)]

Defense

[Tier 1 anchors + the decline script · Tier 2 flex + the same-week-move rule · the written emergency definition]

The Entry Ritual

[Named-task-the-day-before · the environment checklist · the first-five-minutes rule]

The Culture Layer

[The calendar's public label · the team norm proposed · where the interruptions route instead]

Quality Checks

  • Blocks are 90–120 min on honest energy peaks
  • Every block has a tier and the scripts exist
  • Tomorrow's block already has its named task
  • The team-legibility norm is proposed, not just personal stealth
  • The 60-second self-review closes each block

Anti-Patterns

  • Do not block the fantasy 8 hours — two real units beat one heroic collapse
  • Do not place deep work on slump hours because they're free — free and useless is why they're free
  • Do not enter without a named task — an unassigned block is email with ambiance
  • Do not defend by itemizing — "I have a commitment" is complete; justification invites negotiation
  • Do not fight the culture solo forever — the negotiated norm is the sustainable version of the fight

Version History

  • 471c606 Current 2026-07-22 13:20

Same Skill Collection

exports/openclaw/360-feedback-template/SKILL.md
exports/openclaw/401k-plan-decoder/SKILL.md
exports/openclaw/ab-test-planner/SKILL.md
exports/openclaw/ab-test-readout/SKILL.md
exports/openclaw/accessibility-audit/SKILL.md
exports/openclaw/account-plan/SKILL.md
exports/openclaw/acquirer-red-team/SKILL.md
exports/openclaw/ad-copy/SKILL.md
exports/openclaw/aeo-optimizer/SKILL.md
exports/openclaw/agenda-or-cancel/SKILL.md
exports/openclaw/agent-design-review/SKILL.md
exports/openclaw/agent-observability-spec/SKILL.md
exports/openclaw/agent-spec/SKILL.md
exports/openclaw/ai-ethics-review/SKILL.md
exports/openclaw/ai-eval-plan/SKILL.md
exports/openclaw/ai-feature-prd/SKILL.md
exports/openclaw/ai-product-canvas/SKILL.md
exports/openclaw/air-quality/SKILL.md
exports/openclaw/altitude-shifter/SKILL.md
exports/openclaw/ambiguity-resolver/SKILL.md
exports/openclaw/analyst-relations-brief/SKILL.md
exports/openclaw/announcement-card/SKILL.md
exports/openclaw/api-docs-writer/SKILL.md
exports/openclaw/api-test-plan/SKILL.md
exports/openclaw/api-versioning-strategy/SKILL.md
exports/openclaw/apology-letter/SKILL.md
exports/openclaw/architecture-decision-record/SKILL.md
exports/openclaw/architecture-diagram/SKILL.md
exports/openclaw/archive-strategy/SKILL.md
exports/openclaw/assumption-bounty/SKILL.md
exports/openclaw/assumption-mapper/SKILL.md
exports/openclaw/async-update-format/SKILL.md
exports/openclaw/auto-repair-estimate-decoder/SKILL.md
exports/openclaw/autopilot-charter/SKILL.md
exports/openclaw/benefits-decoder/SKILL.md
exports/openclaw/bid-tender-review/SKILL.md
exports/openclaw/board-deck-narrative/SKILL.md
exports/openclaw/board-minutes/SKILL.md
exports/openclaw/board-pre-read/SKILL.md
exports/openclaw/bom-cost-review/SKILL.md
exports/openclaw/bookkeeping-categorization/SKILL.md
exports/openclaw/boolean-search-builder/SKILL.md
exports/openclaw/brag-doc/SKILL.md
exports/openclaw/brainstorming/SKILL.md
exports/openclaw/brief-builder/SKILL.md
exports/openclaw/briefing-note/SKILL.md
exports/openclaw/budget-builder/SKILL.md
exports/openclaw/budget-variance-analysis/SKILL.md
exports/openclaw/bug-diagnosis/SKILL.md
exports/openclaw/bug-report/SKILL.md

Metadata

Files
0
Version
471c606
Hash
3b55a4a8
Indexed
2026-07-22 13:20

- 위키
Copyright © 2011-2026 iteam. Current version is 2.155.2. UTC+08:00, 2026-07-29 14:49
浙ICP备14020137号-1 $방문자$