Agent skill

Deep Work Optimizer

by FerroxLabs in FerroxLabs/wayland

Synthesizes Deep Work (Newport), Flow State (Csikszentmihalyi), Maker's Schedule (Graham), and Biological Prime Time into The Focus Protocol - a system for maximizing cognitively demanding output.

Apache-2.0Auto-check passedProductivity & Automation

Install Deep Work Optimizer

skills CLI
$ npx skills add FerroxLabs/wayland --skill deep-work-optimizer -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install FerroxLabs/wayland deep-work-optimizer --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/FerroxLabs/wayland.git skills-src && mkdir -p .claude/skills && cp -r skills-src/src/process/resources/skills-library/bodies/skills/productivity/deep-work-optimizer .claude/skills/deep-work-optimizer && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
deep-work-optimizer
GitHub stars
608
Token cost
~4.3k tokens
SKILL.md length
1,285 words
Files
1
Skills in repo
1,194
Repo updated
First seen
Licence
Apache-2.0

At a glance

Synthesizes Deep Work (Newport), Flow State (Csikszentmihalyi), Maker's Schedule (Graham), and Biological Prime Time into The Focus Protocol - a system for maximizing cognitively demanding output.

  • Works in 8 steps: What kind of deep work do you do?… → How much of your day is currently spent… → What are your biggest focus killers?… → …
  • The user asks about deep work optimizer
  • SKILL.md covers When to Use, Questions to Ask First, The Focus Protocol and Source Methodology Comparison, plus 7 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Deep Work Optimizer is an agent skill from FerroxLabs/wayland. Synthesizes Deep Work (Newport), Flow State (Csikszentmihalyi), Maker's Schedule (Graham), and Biological Prime Time into The Focus Protocol - a system for maximizing cognitively demanding output. Use when the user asks about deep work optimizer, related techniques, best practices, or needs guidance in this domain. Do NOT use when the request is outside the scope of deep work optimizer or requires a different specialized skill.

Its SKILL.md is about 4.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Productivity & Automation, covering Focus and ADHD support. The repository describes itself as: Wayland - The AI Agent That Perceives. Reasons. Acts. Evolves. The licence is Apache-2.0.

When your agent uses it

  • The user asks about deep work optimizer
  • Related techniques
  • Needs guidance in this domain
  • The request is outside the scope of deep work optimizer

Example prompts

  • “Use the deep-work-optimizer skill to synthesiz Deep Work (Newport), Flow State (Csikszentmihalyi), Maker's Schedule (Graham), and Biological Prime…”
  • “/deep-work-optimizer”

Workflow steps

8 steps, taken from the first numbered list in SKILL.md.

  1. What kind of deep work do you do? (Writing, programming, analysis, design, research, strategic thinking, creative work?)
  2. How much of your day is currently spent in focused, uninterrupted work? Be honest - most people overestimate.
  3. What are your biggest focus killers? (Notifications, colleagues, meetings, internal restlessness, social media, email?)
  4. What does your typical day look like? Walk me through a normal day hour by hour.
  5. When do you feel most mentally sharp? (Morning, midday, afternoon, evening, late night?)
  6. How much control do you have over your schedule? (Fully autonomous, mostly meetings, reactive/on-call, hybrid?)
  7. What is your work environment? (Private office, shared office, open plan, home office, coffee shops, varies?)
  8. Have you experienced flow states? What were you doing?

What it can do on your machine

Read from SKILL.md and the folder at commit 4c030c7. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are template).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Deep Work Optimizer loads about 4.3k tokens when it runs. Until then it costs about 113 tokens; SKILL.md has 1,285 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~113
When it runs · the whole SKILL.md, loaded when a task matches
~4.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from FerroxLabs/wayland at commit 4c030c7, republished under its Apache-2.0 licence (© FerroxLabs). 1,285 words, ~4,283 tokens.

Download SKILL.mdSave it as .claude/skills/deep-work-optimizer/SKILL.md (or your agent's skills folder).
name
deep-work-optimizer
description
Synthesizes Deep Work (Newport), Flow State (Csikszentmihalyi), Maker's Schedule (Graham), and Biological Prime Time into The Focus Protocol - a system for maximizing cognitively demanding output. Use when the user asks about deep work optimizer, related techniques, best practices, or needs guidance in this domain. Do NOT use when the request is outside the scope of deep work optimizer or requires a different specialized skill.
license
Apache-2.0
metadata.author
foundry-skills
metadata.version
1.0.0
metadata.tags
time-management frameworks habits guide beginner-friendly analysis research performing-arts
metadata.category
productivity
metadata.subcategory
methodology-frameworks
metadata.disclaimer
none
metadata.difficulty
advanced

Deep Work Optimizer

You are an expert in cognitive performance and focused work. You understand that the ability to concentrate intensely on cognitively demanding tasks is both increasingly rare and increasingly valuable. You help users design their work environment, schedule, and rituals to maximize deep, focused output by drawing from the best research on concentration, flow, and chronobiology.

When to Use

Use this skill when:

  • User asks about deep work optimizer techniques or best practices
  • User needs guidance on deep work optimizer concepts
  • User wants to implement or improve their approach to deep work optimizer

Do NOT use when:

  • The request falls outside the scope of deep work optimizer
  • User needs a different specialized skill for their specific situation
  • The topic requires professional consultation beyond general guidance

Questions to Ask First

Before designing any focus system, gather this information:

  1. What kind of deep work do you do? (Writing, programming, analysis, design, research, strategic thinking, creative work?)
  2. How much of your day is currently spent in focused, uninterrupted work? Be honest - most people overestimate.
  3. What are your biggest focus killers? (Notifications, colleagues, meetings, internal restlessness, social media, email?)
  4. What does your typical day look like? Walk me through a normal day hour by hour.
  5. When do you feel most mentally sharp? (Morning, midday, afternoon, evening, late night?)
  6. How much control do you have over your schedule? (Fully autonomous, mostly meetings, reactive/on-call, hybrid?)
  7. What is your work environment? (Private office, shared office, open plan, home office, coffee shops, varies?)
  8. Have you experienced flow states? What were you doing?

The Focus Protocol

Our framework synthesizes four approaches to deep cognitive work into a practical system that accounts for your biology, your environment, and the nature of your work.

The Three Pillars
PILLAR 1: PROTECT  - Guard your best hours from interruption
PILLAR 2: PREPARE  - Design rituals and environment for rapid depth
PILLAR 3: SUSTAIN  - Manage energy to extend focus capacity over time

Source Methodology Comparison

ApproachBest ForKey InsightLimitation
Deep Work (Cal Newport)Knowledge workers; career strategyDeep work is rare and valuable; schedule it like your most important meetingBiased toward academic/writing work; less guidance for collaborative deep work
Flow State (Csikszentmihalyi)Creative and skilled workFlow occurs when challenge matches skill; clear goals + immediate feedback + appropriate difficultyFlow is a state, not a strategy; cannot force it; not all work can produce flow
Maker's Schedule (Paul Graham)Programmers, writers, designersMakers need half-day blocks minimum; a single meeting can destroy a full day of outputAssumes you can control your calendar; ignores biological rhythms
Biological Prime Time (Sam Carpenter)Anyone; energy managementYour cognitive capacity fluctuates predictably across the day; match work type to energy levelIndividual variation requires self-tracking; oversimplifies complex chronobiology

Pillar 1: Protect Your Focus Time

Identify Your Biological Prime Time

Your brain has predictable peaks and valleys throughout the day. Most people follow one of these patterns:

EARLY CHRONOTYPE ("Morning Lark"):
Peak 1: 8:00 - 11:30 AM (strongest cognitive period)
Dip:    1:00 - 2:30 PM  (post-lunch trough)
Peak 2: 3:00 - 5:00 PM  (secondary peak)

INTERMEDIATE CHRONOTYPE:
Peak 1: 9:30 AM - 12:30 PM
Dip:    2:00 - 3:30 PM
Peak 2: 4:00 - 6:00 PM

LATE CHRONOTYPE ("Night Owl"):
Peak 1: 11:00 AM - 2:00 PM
Dip:    3:00 - 4:30 PM
Peak 2: 7:00 - 11:00 PM (often the strongest period)
Track Your Own Pattern

For one week, rate your mental clarity every hour on a 1-5 scale. Do not change your routine; just observe. After a week, your peaks and valleys will be obvious. This is your Biological Prime Time.

The Schedule Architecture

Once you know your peaks, apply the Maker's Schedule principle: protect your peak hours in uninterrupted blocks.

PEAK HOURS:     Deep Work blocks (minimum 90 minutes, ideally 2-4 hours)
                No meetings. No email. No chat. No exceptions.

DIP HOURS:      Shallow work (email, administrative tasks, routine meetings)
                This work must get done; do it when your brain is least capable of depth.

SECONDARY PEAK: Moderate-depth work or second deep work session
                Good for review, editing, lighter creative work, or collaborative deep work.

TRANSITION:     Buffer time between modes (15-30 minutes)
                Your brain cannot switch instantly from shallow to deep.
Deep Work Scheduling Philosophies

Choose the philosophy that fits your life (from Newport):

MONASTIC:     Eliminate or radically minimize all shallow work
              Best for: Academics, novelists, researchers with minimal obligations
              Example: No email. No social media. Full days of deep work.

BIMODAL:      Dedicate defined stretches (days or weeks) to deep work, others to shallow
              Best for: Professors, consultants, anyone with seasonal work patterns
              Example: Tues/Wed/Thurs = deep work days. Mon/Fri = meetings and admin.

RHYTHMIC:     Same time every day is deep work, protected as habit
              Best for: Most knowledge workers with daily obligations
              Example: 8:00-11:30 AM is deep work, every day, non-negotiable.

JOURNALISTIC: Fit deep work into any available gap in schedule
              Best for: Experienced deep workers with unpredictable schedules
              Warning: This requires a trained ability to shift into deep focus rapidly.
              Not recommended for beginners.

Pillar 2: Prepare for Depth

The Deep Work Ritual

A consistent pre-work ritual reduces the activation energy needed to enter deep focus. Design yours to include:

1. LOCATION:    Where will you work? (Same place each time if possible)
2. DURATION:    How long will this session last? (Set it before you start)
3. STRUCTURE:   What are the rules? (No internet? Phone off? Door closed?)
4. FUEL:        What supports you? (Coffee prepared? Water bottle? Snack ready?)
5. INTENTION:   What specific thing will you produce? (Not "work on project" but
                "write the introduction section" or "implement the auth module")
Example Rituals
WRITER'S RITUAL:
- Close all apps except writing tool
- Put phone in another room
- Set a 90-minute timer
- Write a one-sentence intention on a sticky note
- Begin with yesterday's last paragraph (builds momentum)

PROGRAMMER'S RITUAL:
- Close email, Slack, and all browser tabs
- Open only IDE and relevant documentation
- Review the specific issue or feature to implement
- Write a brief comment describing the approach before coding
- Set a visible timer for 2 hours

STRATEGIST'S RITUAL:
- Go to a different location (conference room, library, coffee shop)
- Bring only a notebook and one printed document
- No laptop (removes digital distraction entirely)
- Write the question to answer at the top of the page
- Set a 60-minute timer
Environment Design

Your physical space should signal "focus mode" to your brain:

Visual: Remove visible distractions. Clean desk surface. Face away from foot traffic. Auditory: Noise-cancelling headphones, white noise, or silence. If music, only instrumental and consistent (do not browse playlists). Digital: Close all unnecessary apps. Use website blockers during deep work. Turn off ALL notifications. Social: Communicate your focus time to others. Use a visible signal (headphones on, door closed, status set to DND). Establish a social contract: "If my headphones are on, it is not urgent."

The Focus Trigger Stack

Build a sequence of small actions that prime your brain for depth:

1. Same physical location (spatial trigger)
2. Same beverage (sensory trigger)
3. Same startup ritual (behavioral trigger)
4. Same music/sound (auditory trigger)
5. State your intention out loud or in writing (cognitive trigger)

Over time, this stack becomes a Pavlovian trigger for deep concentration.

Pillar 3: Sustain Focus Over Time

Understanding Ultradian Rhythms

Your brain operates in approximately 90-minute cycles of high and low alertness (ultradian rhythms). After 90 minutes of intense focus, cognitive performance drops regardless of willpower.

THE 90-MINUTE FOCUS CYCLE:
[0-20 min]    Warm-up phase: entering depth
[20-60 min]   Peak focus: highest quality output
[60-90 min]   Sustained focus: good but declining
[90-110 min]  Diminishing returns: take a break
[110+ min]    Counterproductive: errors increase, creativity drops
The Sustainable Focus Schedule
SESSION 1:  90 minutes deep work
BREAK 1:    20 minutes genuine rest (not phone scrolling)
SESSION 2:  90 minutes deep work
BREAK 2:    30-60 minutes (lunch, walk, social)
SESSION 3:  60-90 minutes deep work (secondary peak hours)
BREAK 3:    20 minutes rest

TOTAL DEEP WORK: 4-5 hours per day (this is the realistic maximum for most people)

Most people can sustain 3-5 hours of truly deep work per day. Attempting more leads to diminishing returns and burnout. Newport's research suggests even elite performers (concert pianists, chess grandmasters) rarely exceed 4-5 hours of deliberate practice daily.

What Counts as a Real Break
REAL REST (restores focus):          NOT REST (depletes further):
- Walking outside                    - Checking email
- Stretching or light movement       - Browsing social media
- Casual conversation                - Reading news
- Looking at nature or distance      - Watching videos
- Doing nothing (intentionally)      - Shopping online
- Brief meditation or breathing      - Answering messages
- Napping (10-20 minutes)           - Doing more "light" work
Show full SKILL.md (527 more words)Show less
Flow State Conditions

Flow (from Csikszentmihalyi) is the optimal state of deep focus where time seems to disappear and output quality peaks. You cannot force flow, but you can create the conditions for it:

REQUIRED CONDITIONS:
1. Clear goals:        Know exactly what you are trying to produce
2. Immediate feedback: See results of your work in real time
3. Challenge-skill match: Task difficulty is 4% above current skill level
                         Too easy = boredom; too hard = anxiety

SUPPORTING CONDITIONS:
4. No interruptions:   External disruptions break flow instantly
5. Deep involvement:   Intrinsic interest in the work
6. Sense of control:   Autonomy over how you approach the task
7. Merged action and awareness: You become one with the activity
When Flow Is Not the Goal

Not all deep work needs flow. Analytical work, editing, debugging, and review require focused attention but may not produce the euphoric flow state. That is fine. The Focus Protocol optimizes for sustained concentration, not just peak experiences.

Build Your Personal System

The Focus Audit

Before changing anything, measure your current state:

For one week, track:
- Hours of uninterrupted focus per day: ___
- Longest single focus session: ___
- Number of times interrupted per session: ___
- Peak energy hours: ___
- Biggest distraction source: ___
- How focus time is currently scheduled: ___
Designing Your Focus Protocol
MY BIOLOGICAL PRIME TIME:
Peak 1: ___ to ___
Dip:    ___ to ___
Peak 2: ___ to ___

MY DEEP WORK PHILOSOPHY:
[ ] Monastic  [ ] Bimodal  [ ] Rhythmic  [ ] Journalistic

MY PROTECTED DEEP WORK BLOCKS:
Block 1: ___ to ___ (location: ___)
Block 2: ___ to ___ (location: ___)

MY RITUAL:
Before starting, I will:
1. _______________
2. _______________
3. _______________
4. _______________

MY FOCUS RULES:
- Phone: _______________
- Email/chat: _______________
- Notifications: _______________
- Signal to others: _______________

MY BREAK PROTOCOL:
After each 90-min session: _______________
After two sessions: _______________
Common Problems and Solutions
ProblemRoot CauseSolution
Cannot start focusingNo ritual; too many optionsUse the Focus Trigger Stack; start with one specific sub-task
Constantly checking phoneDopamine habit; phone within reachPhone in another room; use app blockers; track phone pickups
Meetings destroy the dayNo protected time; reactive schedulingBlock deep work in calendar first; batch meetings into one day
Guilty for not responding instantlyCultural expectation of availabilityNegotiate response time expectations; set auto-reply during deep work
Exhausted after 2 hoursNormal; expecting too much4-5 hours of deep work is elite performance; respect your limits
Deep work feels boringChallenge-skill mismatchIncrease difficulty; work on more meaningful problems
Cannot sustain across the weekNo recovery; weekend workSchedule at least one full rest day; protect sleep
Gradual Implementation

Do not try to go from zero deep work to four hours overnight:

Week 1:   One 30-minute deep work session per day
Week 2:   One 60-minute session per day
Week 3:   One 90-minute session per day
Week 4:   Two 90-minute sessions per day
Week 5+:  Full Focus Protocol (3-5 hours across 2-3 sessions)

Measuring Deep Work Output

Track both quantity and quality:

QUANTITY: Hours of deep work per day and per week
QUALITY: Tangible output per session (words written, features shipped, problems solved)

WEEKLY REVIEW:
Total deep work hours: ___
Average daily deep work: ___
Best session this week: ___
What I produced: ___
What I will protect better next week: ___

Further Reading

For deeper exploration of the source methodologies:

  • Deep Work by Cal Newport - The case for focused work as a competitive advantage
  • Flow by Mihaly Csikszentmihalyi - The psychology of optimal experience
  • Maker's Schedule, Manager's Schedule by Paul Graham - The essay on protecting creative time (available online)
  • The Body Clock Guide (various authors) - Circadian and ultradian rhythm research
  • Hyperfocus by Chris Bailey - Practical techniques for directing attention

The Focus Protocol synthesizes these approaches into a system you can implement immediately, customized to your biology, work type, and schedule constraints.

Process

  1. Gather information. Ask the user clarifying questions to understand their specific situation, goals, and constraints
  2. Analyze context. Review the information provided and identify key factors relevant to deep work optimizer
  3. Develop recommendations. Apply domain expertise to create actionable guidance tailored to the user's needs
  4. Present structured output. Deliver findings in the output format below with clear next steps
  5. Address follow-ups. Answer additional questions and refine recommendations based on feedback

Output Format

template
## Deep Work Optimizer Analysis

### Assessment
[Key findings and observations]

### Recommendations
1. [Primary recommendation]
2. [Secondary recommendation]
3. [Additional suggestions]

### Action Items
- [ ] [First action step]
- [ ] [Second action step]
- [ ] [Follow-up task]

Edge Cases

  • Incomplete information: Ask clarifying questions before proceeding with recommendations
  • Conflicting requirements: Prioritize the most critical constraint and note trade-offs
  • Out of scope requests: Redirect to appropriate specialized skill or professional resource
  • Beginner vs advanced: Adjust depth and terminology based on user's experience level

Example

Input: "Help me with deep work optimizer for my current situation"

Output:

Based on your situation, here is a structured approach to deep work optimizer:

  1. Assessment: Evaluate your current state and identify key areas for improvement
  2. Strategy: Develop a targeted plan based on best practices
  3. Implementation: Execute the plan with specific, measurable steps
  4. Review: Monitor progress and adjust as needed

© FerroxLabs, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in src/process/resources/skills-library/bodies/skills/productivity/deep-work-optimizer of FerroxLabs/wayland.

Open the folder on GitHubat commit 4c030c7

Compare with similar skills

Deep Work Optimizer next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Deep Work Optimizer compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Deep Work Optimizer this skillFerroxLabs/wayland608—~4.3kAutomated safety check: PassApache-2.0
I Have AdhdTanStack/ai3.2k5 repos~1.8kAutomated safety check: PassMIT
Attention Kindalexgreensh/attention-span1.3k—~2kAutomated safety check: PassAGPL-3.0
Remind Meshaheer-00/claude-adhd104—~1.1kAutomated safety check: PassNone
Daily Focus Boardgithub/awesome-copilot40k—~3kAutomated safety check: PassMIT
Attention Controlaaddrick/attention-control117—~3.6kAutomated safety check: PassMIT

Similar skills

  • I Have Adhd

    TanStack/ai

    A skill your agent uses when the user invokes /i-have-adhd, says they have ADHD, or asks for ADHD-friendly output.

    3.2k GitHub starsUsed in 5 repos~1.8k tokens
    Productivity & AutomationAuto-check passed
  • Attention Kind

    alexgreensh/attention-span

    Answer in the ADHD-friendly Attention-kind style for the rest of this chat.

    1.3k GitHub stars~2k tokensUpdated 1 mo ago
    Productivity & AutomationAuto-check passed
  • Remind Me

    shaheer-00/claude-adhd

    Surface unfinished or forgotten tasks, ideas, and open questions from the user's past Claude Code sessions, manage custom reminders, run focus sessions, and match tasks to the user's energy.

    104 GitHub stars~1.1k tokensUpdated 27 days ago
    Productivity & AutomationAuto-check passed
  • Daily Focus Board

    github/awesome-copilot

    Official

    Builds a warm, browser-based daily focus board the user updates by talking to their agent, with Eisenhower priorities, a brain-dump box and kind not-today carryover.

    40k GitHub stars~3k tokensUpdated today
    Productivity & AutomationAuto-check passed
  • Attention Control

    aaddrick/attention-control

    Shape output for a reader with ADHD, then write each sentence in controlled English: action first, one word one meaning, active voice, simple tenses, state restated every turn.

    117 GitHub stars~3.6k tokensUpdated 1 mo ago
    Productivity & AutomationAuto-check passed
  • Fable Fable

    mrtooher/fable-mode

    Run fable-mode execution discipline on Claude Fable 5.1 — the top of the escalation ladder and the strongest staged run available.

    870 GitHub stars~1.1k tokensUpdated 1 mo ago
    Productivity & AutomationAuto-check passed

More from FerroxLabs/wayland

All 1,194 skills in this repo
  • Star Office Helper

    FerroxLabs/wayland

    Install, start, connect, and troubleshoot visualization companion projects for Aion/OpenClaw, with Star-Office-UI as the default recommendation.

    608 GitHub stars~2.2k tokensUpdated yesterday
    Auto-check: notes
  • Openclaw Setup

    FerroxLabs/wayland

    OpenClaw usage expert: Helps you install, deploy, configure, and use OpenClaw personal AI assistant.

    608 GitHub stars~1.9k tokensUpdated yesterday
    Auto-check passed
  • Tvcontrol Setup

    FerroxLabs/wayland

    Set up TVControl end to end: install the connector, start TradingView Desktop with its control port open, load a watchlist export, add the indicators they use, and leave a working chart.

    608 GitHub stars~5.7k tokensUpdated yesterday
    Auto-check passed
  • Ab Testing Specialist

    FerroxLabs/wayland

    End-to-end guide for designing, running, and analyzing A/B tests including experiment design, statistical significance, sample size calculation, common pitfalls, and advanced testing patterns.

    608 GitHub stars~3.7k tokensUpdated yesterday
    Auto-check passed
  • Academic Writer

    FerroxLabs/wayland

    Complete academic writing guide covering thesis and dissertation structure, journal article format using IMRaD, literature review methodology, citation management, the peer review process, and…

    608 GitHub stars~4.5k tokensUpdated yesterday
    Auto-check passed
  • Accessibility Auditor

    FerroxLabs/wayland

    Web accessibility expertise covering WCAG 2.2 conformance, audit methodology, ARIA patterns, keyboard navigation, screen reader testing, focus management, form accessibility, and automated vs manual…

    608 GitHub stars~4.1k tokensUpdated yesterday
    Auto-check passed

Questions about Deep Work Optimizer

What does Deep Work Optimizer do?

Synthesizes Deep Work (Newport), Flow State (Csikszentmihalyi), Maker's Schedule (Graham), and Biological Prime Time into The Focus Protocol - a system for maximizing cognitively demanding output. Deep Work Optimizer is an agent skill from FerroxLabs/wayland. Synthesizes Deep Work (Newport), Flow State (Csikszentmihalyi), Maker's Schedule (Graham), and Biological Prime Time into The Focus Protocol - a system for maximizing cognitively demanding output.

When should I use Deep Work Optimizer?

Deep Work Optimizer fits situations like: the user asks about deep work optimizer; related techniques; needs guidance in this domain; the request is outside the scope of deep work optimizer.

How do I install Deep Work Optimizer in Claude Code?

Run `npx skills add FerroxLabs/wayland --skill deep-work-optimizer -a claude-code`. Or copy the skill folder (src/process/resources/skills-library/bodies/skills/productivity/deep-work-optimizer in FerroxLabs/wayland) into .claude/skills/deep-work-optimizer in your project. Claude Code loads it when a task matches its description.

How do I install Deep Work Optimizer in Codex?

Run `npx skills add FerroxLabs/wayland --skill deep-work-optimizer -a codex`. Or copy the skill folder (src/process/resources/skills-library/bodies/skills/productivity/deep-work-optimizer in FerroxLabs/wayland) into .agents/skills/deep-work-optimizer in your project. Codex loads it when a task matches its description.

Can I use Deep Work Optimizer in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add FerroxLabs/wayland --skill deep-work-optimizer -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/deep-work-optimizer, .gemini/skills/deep-work-optimizer, .github/skills/deep-work-optimizer and .opencode/skills/deep-work-optimizer in your project.

What does Deep Work Optimizer need to run?

SKILL.md names no scripts, command-line tools or credentials: Deep Work Optimizer is instructions for the agent only.

Does Deep Work Optimizer access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Deep Work Optimizer safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Deep Work Optimizer use?

Deep Work Optimizer is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Deep Work Optimizer use?

About 4.3k tokens (SKILL.md is roughly 17k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Deep Work Optimizer?

Skills that share tags, products or a category with Deep Work Optimizer: I Have Adhd (TanStack/ai, 3.2k stars), Attention Kind (alexgreensh/attention-span, 1.3k stars), Remind Me (shaheer-00/claude-adhd, 104 stars) and Daily Focus Board (github/awesome-copilot, 40k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Deep Work Optimizer?

FerroxLabs (a GitHub user) maintains it in FerroxLabs/wayland, which has 608 GitHub stars. The repository holds 1,194 skills in this directory. The repository was last updated on October 6, 2026.

Source: FerroxLabs/wayland on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.