Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsCommunityBlog
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

Back to skills

Eisenhower Matrix

ASecurity

Prioritize tasks by urgency and importance—focus on important but not urgent work to prevent firefighting

22 stars
0 votes
0 copies
0 views
Added 9/20/2026
businessrustgoreactapisecurity

Works with

cliapi

Security Analysis

A100/100

Scanned 9/20/2026

Install to Claude Code

$npx -y skills add lev-os/agents --skill eisenhower-matrix --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Eisenhower Matrix?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Eisenhower Matrix
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/lev-os-eisenhower-matrix/badge)](https://www.skillsdirectory.com/skills/lev-os-eisenhower-matrix)

More formats (shields.io, HTML) on the badges page.

Download Zip
Files
SKILL.md
---
name: eisenhower-matrix
description: Prioritize tasks by urgency and importance—focus on important but not urgent work to prevent firefighting
---

# Eisenhower Matrix

## One-Liner
Prioritize tasks by urgency and importance—focus on important but not urgent work to prevent firefighting.

## Core Insight
The Eisenhower Matrix (also called Urgent-Important Matrix) categorizes tasks along two dimensions: urgency (deadline pressure) and importance (impact on goals). This creates four quadrants that dictate different handling strategies. The key insight: **important but not urgent** work gets crowded out by urgent tasks, yet it's where strategy, prevention, and growth happen. Most people are reactive (Quadrant 1) or distracted (Quadrants 3-4) instead of proactive (Quadrant 2).

**Attributed to**: Dwight D. Eisenhower, 34th U.S. President, known for saying "What is important is seldom urgent, and what is urgent is seldom important."

## Mental Model
```
                URGENT              |         NOT URGENT
                                    |
IMPORTANT   Quadrant 1: CRISIS      |   Quadrant 2: STRATEGY
            • Do immediately        |   • Schedule & protect
            • Firefighting          |   • Prevention & growth
            • Deadlines             |   • Where mastery happens
            • Emergencies           |   • Planning, learning
            Example: Server down    |   Example: System design
                                    |
            ────────────────────────┼─────────────────────────
                                    |
NOT         Quadrant 3: DISTRACTION |   Quadrant 4: WASTE
IMPORTANT   • Delegate or deflect   |   • Eliminate ruthlessly
            • Others' priorities    |   • Time sinks
            • Interruptions         |   • Mindless tasks
            • Busy work             |   • Escapism
            Example: Most meetings  |   Example: Social media
                                    |
```

**Goal**: Minimize Quadrant 1 (crises), eliminate Quadrants 3-4 (waste), maximize Quadrant 2 (strategy).

## When to Use
- **Daily planning**: Decide what to work on today
- **Weekly review**: Allocate time across quadrants
- **Saying no**: Justify declining requests
- **Delegation**: Identify what others should handle
- **Time audits**: Diagnose where time actually goes
- **Preventing burnout**: Shift from reactive to proactive mode

**Apply when**: Feeling overwhelmed, constantly firefighting, unsure what to prioritize, saying yes to everything, making no progress on important goals.

**Don't apply when**: True emergencies requiring immediate action (Quadrant 1), tasks where urgency = importance (product launch day).

## Execution Steps

### 1. List All Tasks
Brain dump everything on your plate:
- Meetings, emails, projects
- Requests from others
- Long-term goals
- "Should do" items

**No filtering yet**—just capture exhaustively.

### 2. Define "Important"
**Important = moves you toward your goals**

Ask for each task: "If this doesn't happen, do my objectives fail?"

**Examples of Important**:
- Strategic planning for Q2
- Hiring critical team member
- Learning new skill for career growth
- Building relationships with key stakeholders
- Designing system architecture
- Preventive maintenance

**Examples of Not Important**:
- Checking social media
- Attending meetings with no agenda
- Perfecting slide deck formatting
- Rearranging task management system
- Reading every email immediately

### 3. Define "Urgent"
**Urgent = has a deadline or consequences for delay**

Ask: "What happens if this waits until tomorrow? Next week?"

**Examples of Urgent**:
- Production outage (immediate deadline)
- Client demo in 2 hours
- Payroll due today
- Critical bug in released software
- Regulatory compliance deadline

**Examples of Not Urgent**:
- Improving team processes
- Reading industry research
- Networking
- Exercise and health
- Long-term skill building

### 4. Categorize Into Quadrants

**Quadrant 1: Urgent + Important (CRISIS)**
- Production emergencies
- Critical bugs affecting customers
- Deadline-driven deliverables
- Crises and disasters

**Handling Strategy**: Do immediately. But investigate: Why did this become a crisis? Often Q1 tasks result from neglecting Q2 work.

**Quadrant 2: Important + Not Urgent (STRATEGY)**
- Strategic planning
- Relationship building
- Skill development
- Process improvement
- Preventive maintenance
- Design and architecture
- Exercise, health, rest

**Handling Strategy**: Schedule dedicated time. **This is the only quadrant that reduces future Q1 crises.** Protect this time ruthlessly.

**Quadrant 3: Urgent + Not Important (DISTRACTION)**
- Most meetings
- Many emails
- Others' priorities
- Interruptions
- Requests that don't align with your goals

**Handling Strategy**: Delegate, decline, or defer. These feel important because they're urgent, but they don't move your goals forward.

**Quadrant 4: Not Urgent + Not Important (WASTE)**
- Mindless browsing
- Excessive social media
- Busy work
- Trivial tasks
- Time-wasting "productivity" systems
- Perfectionism on unimportant work

**Handling Strategy**: Eliminate. These are pure time sinks with no ROI.

### 5. Apply Handling Strategies

**For Q1 (Crisis - Do)**:
- Handle immediately
- Then ask: "How do I prevent this from recurring?" (Q2 work)
- Set aside time after crisis to build prevention

**For Q2 (Strategy - Schedule)**:
- Block calendar time (non-negotiable)
- Treat like appointments
- Do these BEFORE urgent tasks crowd them out
- Typical targets: 60-80% of your time should be Q2

**For Q3 (Distraction - Delegate/Decline)**:
- Delegate: Can someone else do this?
- Decline: Politely say no with explanation
- Defer: Move to later when less busy
- Batch: Combine many small Q3 tasks into one time block

**For Q4 (Waste - Eliminate)**:
- Delete from list
- Use blocking tools (website blockers, app limits)
- Replace with Q2 activities
- Be honest: Most Q4 time is procrastination

### 6. Time Audit
Track where time actually goes for 1 week:

| Quadrant | Target % | Actual % | Gap |
|----------|----------|----------|-----|
| Q1 Crisis | 20-25% | ___% | |
| Q2 Strategy | 60-80% | ___% | |
| Q3 Distraction | 0-15% | ___% | |
| Q4 Waste | 0-5% | ___% | |

**Most people's actual**:
- Q1: 40-50% (constant firefighting)
- Q2: 15-20% (neglected)
- Q3: 25-35% (can't say no)
- Q4: 10-15% (procrastination)

**Goal**: Shift from Q1/Q3/Q4 → Q2

### 7. Build Q2 Habits
**Weekly Planning** (Q2 activity):
- Sunday evening or Monday morning
- Block Q2 time for the week ahead
- Identify potential Q1 crises and prevent them
- Say no to Q3/Q4 in advance

**Daily Review** (Q2 activity):
- Start day with Q2 work (before email/Slack)
- Check: Is today's plan Q2-heavy or Q1-reactive?
- End day: Did I spend time on important non-urgent work?

## Real-World Examples

**Software Engineer's Week**

**Quadrant 1** (25% - handle immediately):
- Production outage at 3am → fix now
- Security vulnerability disclosed → patch immediately
- Demo to CEO tomorrow → finish today

**Quadrant 2** (65% - schedule & protect):
- Design new system architecture (Mon 9-12)
- Code review and mentoring (Tue afternoon)
- Learn new framework for upcoming project (Wed morning)
- Refactor technical debt to prevent Q1 issues (Thu)
- 1-on-1s with reports, career development (Fri)

**Quadrant 3** (10% - delegate or batch):
- Meeting with no clear agenda → decline or send delegate
- "Quick question" Slack messages → batch into 2pm-3pm window
- Status update email → delegate to PM

**Quadrant 4** (0% - eliminate):
- Perfecting code formatting beyond linting
- Checking Hacker News repeatedly
- Reorganizing file structure for the 5th time

**Product Manager's Prioritization**

**Q1**: Customer escalation requiring immediate response
**Q2**: User research, roadmap planning, stakeholder alignment, strategic thinking
**Q3**: Ad-hoc requests from sales, low-priority meetings, formatting documents
**Q4**: Endless slide polishing, reading every industry blog, Twitter

**Shift from 50% Q1 → 20% Q1 by**:
- Investing Q2 time in process improvements
- Building better escalation workflows (prevents crises)
- Training team on common scenarios (reduces urgent requests)

## Common Pitfalls

**Urgency Addiction**
- Dopamine hit from "putting out fires"
- Feel productive doing urgent tasks
- Neglect important strategic work
- Result: Chronic firefighting mode

**Quadrant 3 Confusion**
- "This urgent email must be important!"
- Conflating urgency with importance
- Saying yes to others' priorities
- Result: Busy but not effective

**Perfectionism in Q4**
- Spending hours on unimportant tasks
- "This needs to be perfect" for low-impact work
- Procrastination disguised as productivity

**Planning Fallacy**
- Scheduling 100% Q1/Q2, no buffer for interruptions
- Reality: Some Q3/Q4 is unavoidable
- Build in 20-30% slack for unplanned work

**False Dichotomy**
- Thinking tasks are purely one quadrant
- Reality: Tasks have components across quadrants
- Example: Project has Q1 (deadline) and Q2 (learning) aspects

## Integration with Other Frameworks

**Complements**:
- **Getting Things Done (GTD)**: Eisenhower classifies after GTD captures/clarifies
- **Time Blocking**: Schedule Q2 time blocks on calendar
- **Pareto Principle (80/20)**: Q2 work is often the 20% that generates 80% of results
- **Deep Work**: Q2 work requires deep focus, Q1 is reactive/shallow

**Contrasts**:
- **Lean/Agile "Ship Fast"**: Can over-index on Q1 urgency, neglect Q2 architecture
- **Inbox Zero**: Email processing can become Q3/Q4 distraction from Q2 work

**Sequence**:
1. Eisenhower Matrix: Categorize work by importance/urgency
2. Time Blocking: Schedule Q2 time
3. GTD: Organize Q1/Q3 tasks into trusted system
4. Weekly Review: Adjust quadrant allocations based on outcomes

## Key Takeaways

1. **Urgency ≠ Importance**: The most urgent tasks are often the least important. Learn to distinguish.

2. **Q2 is the Leverage Quadrant**: Strategy, prevention, growth all happen in Q2. This is where compound returns come from.

3. **Q1 Crises Come from Neglecting Q2**: Most fires could be prevented with Q2 planning, maintenance, and relationship building.

4. **Saying No is Essential**: Every Q3 yes is a Q2 no. Protect your Q2 time ruthlessly.

5. **Time Audit Reveals Truth**: Track where time actually goes. Most people wildly overestimate Q2 time.

6. **Batch the Urgent-Unimportant**: Q3 tasks are inevitable. Batch them into dedicated time blocks to minimize context switching.

7. **Eliminate Q4 Ruthlessly**: These tasks don't deserve time boxing or delegation—they deserve deletion.

**The Ultimate Question**:
"Am I being busy (Q1/Q3) or effective (Q2)?"

If you spend 60%+ of your time on important but not urgent work (Q2), crises decrease, capabilities compound, and goals are achieved systematically rather than frantically.

Attribution

lev-oslev-os
View sourceMore from lev-os →
SSkills DirectorySkills Directory

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

Related Skills

Solution Architect

Designs system architecture, component specifications, and technical integration strategy. Use when: designing solutions, system architecture, technology stack, or integration approaches.

192 votes

Akorchak:Venture Assessment

Generate a comprehensive VC investment assessment report for a company

72 votes

Stock Analysis

Analyze stocks and cryptocurrencies using Yahoo Finance data. Supports portfolio management (create, add, remove assets), crypto analysis (Top 20 by market cap), and periodic performance reports (daily/weekly/monthly/quarterly/yearly). 8 analysis dimensions for stocks, 3 for crypto. Use for stock analysis, portfolio tracking, earnings reactions, or crypto monitoring.

6511 votes

Just Fucking Cancel

Find and cancel unwanted subscriptions by analyzing bank transactions. Detects recurring charges, calculates annual waste, and helps you cancel with direct URLs and browser automation. Use when: 'cancel subscriptions', 'audit subscriptions', 'find recurring charges', 'what am I paying for', 'save money', 'subscription cleanup', 'stop wasting money'. Supports CSV import (Apple Card, Chase, Amex, Citi, Bank of America, Capital One, Mint, Copilot) OR Plaid API for automatic transaction pull. Out...

6511 votes

Telegram Compose

Compose rich, readable Telegram messages using HTML formatting via direct Telegram API. Use when: (1) Sending any Telegram message beyond a simple one-line reply, (2) Creating structured messages with sections, lists, or status updates, (3) Need formatting unavailable via Clawdbot's Markdown conversion (underline, spoilers, expandable blockquotes, user mentions by ID), (4) Sending alerts, reports, summaries, or notifications to Telegram, (5) Want professional, scannable message formatting wit...

6511 votes
View all in business →