The AI Eisenhower Matrix Coach skill for Claude

The AI Eisenhower Matrix Coach is a free skill from the skill library of TheSEO. A skill is an instruction file, SKILL.md, that gives an AI assistant a fixed method for one task. Not an app you have to keep up, no subscription, no link to your calendar: one text file of 1,364 words that tells Claude how to place every task, decision or project in the Eisenhower matrix and then go straight on to concrete action.

You download the zip at the top of this page, put it in your Claude environment, and from that moment on Claude sorts your work according to this logic. What such a file is exactly and how it works, you can read in what Claude skills are.

The problem the skill solves is one you feel at the moments you need it most: everything looks urgent, the list grows faster than it shrinks, and at the end of the week the important work has once again not been done. The mechanism underneath is old and well described: urgent things push themselves forward, important things do not. Anyone without a system to separate the two lets the calendar be filled by whoever shouts loudest. Eisenhower's matrix is that system, and this skill makes it applicable to any list you care to paste.

The role the file gives Claude is worded strikingly precisely: a strict but warm prioritisation coach, who does not work as a minute-taker but as a coach who chooses, dares to delete and forces you to look honestly at your week. You notice that difference in the output. A minute-taker sets your list out neatly; this coach says your quadrant 3 is too big, that you are carrying somebody else's agenda, and that the work you called important has been slipping for weeks. It does not judge, it shows, and that is exactly how the file puts it.

It belongs to the skill library that we give away from our AI and automation service, with no account, no newsletter and no sales email afterwards. We would rather you used it and never called than sat through a demo first. And for anyone who wants to understand the model itself before putting an AI on it: the full explanation of the matrix, with background and examples, is in our article about the Eisenhower matrix.

A task list without judgement is a dumping ground, and the method of this skill reads like an analysis of everything that goes wrong in such a dumping ground. Four patterns keep coming back.

Everything feels urgent. Without a definition the feeling wins, and the feeling says the same thing at every email and every phone call: now. Which is why the definitions come first, in step two, before a single task is placed. Urgent is a time limit within 48 hours or a direct deadline set by others. Important is a contribution to a goal, a value, revenue, health or a long-term project. And behind that sits the strictest sentence in the file: not everything is important.

The list has no consequence. Putting a task on a list feels like progress, but nothing changes as long as there is no action attached. So every quadrant gets a fixed action attached: quadrant 1 gets a time block today or tomorrow, quadrant 2 a specific day and time in the week, quadrant 3 a name or an automation, and quadrant 4 is deleted.

The important work always loses. Quadrant 2, important but not urgent, is where the growth sits: strategy, health, learning, relationships. It is also the only quadrant without a deadline, so it slips endlessly. This coach pushes back actively: if quadrant 2 is empty it says so honestly and proposes three quadrant 2 tasks that have to go in the calendar this week.

Somebody else's priorities disguise themselves as yours. Many meetings, ad hoc requests and phone calls are urgent for somebody else, not important for you. That is quadrant 3, and the file names it: other people's priorities disguised as the user's own. The counting step makes it visible: if most of your tasks sit in quadrant 1 or 3, you are living reactively or carrying somebody else's agenda, and you get told so.

In diff form: what goes out and what comes back in its place.

A skill is only as good as its instructions, so we simply describe them here. The file opens with frontmatter that says when Claude should pick the skill up, and that list is broader than you would expect. Not only at Eisenhower matrix or quadrant analysis, but above all at the sentences people really say: what should I do first, I have too much on my plate, everything is urgent, I never get to deep work, what do I drop, what do I delegate. Overloaded weeks, firefighting and the feeling of running behind are named as triggers too. Say something like that to Claude while the skill is loaded and you get it automatically.

Then comes the role description that sets the tone for everything: a strict but warm prioritisation coach, not a minute-taker. The four quadrants are fixed and the file explicitly forbids inventing extra quadrants or half labels. Quadrant 1, urgent and important: do it, now, yourself, and too many tasks here means you are living reactively. Quadrant 2, important but not urgent: schedule and protect, because this is where the deep work, the strategy, the health and the growth sit. Quadrant 3, urgent but not important: delegate or automate, other people's priorities in disguise. Quadrant 4, neither: delete, no excuse to keep it.

The method counts six steps and the file says pointedly: skip no step. First ask for the input, and with vague input ask two sharp questions, not five. Then set the definitions of urgent and important explicitly. Then place every task, with one line per task: the task, the quadrant number and the reason in at most twelve words. Then the action per quadrant. Then point out the pattern: count how many tasks sit in each quadrant and say honestly what that says about your week, including three proposals for quadrant 2 if it turns out to be empty. And last the day start: three blocks of 90 minutes for tomorrow, of which at least one block is quadrant 2.

The output format is fixed in a template you can copy straight into a note or a dashboard, with fixed headings for the definitions, the four quadrants, the pattern of the week, the top three actions for tomorrow and one question back. The tone is nailed down too: direct, short sentences, saying honestly when quadrant 4 quietly fills the largest part of the week, no over-the-top motivational language, no long disclaimers, and no lists with more than five items unless you give a lot of input yourself.

It closes with a complete example of input and output, the same example you saw above in FIG.01. Want to learn to write such an instruction file yourself? The method is in writing a SKILL.md.

The SKILL.md names its sources and instructs Claude to acknowledge them if you ask. The basis comes from a speech by President Dwight D. Eisenhower in 1954, in which he divided his problems into two kinds and added the observation that, in his words, "the urgent are not important, and the important are never urgent". That is the heart of everything this skill does: urgency and importance are two different axes, and anyone who mixes them up lets their calendar be filled by fires while the real work is left undone.

The matrix as we know it now, with the four quadrants, comes from Stephen R. Covey. In The 7 Habits of Highly Effective People from 1989 he worked Eisenhower's principle out into the quadrant model, with an emphasis this skill adopts one to one: quadrant 2, the important but not urgent work, is where the growth sits, and it is at the same time the quadrant that always loses without protection. There is a nod to the modern explanation by Brett and Kate McKay from 2013 as well, as an accessible way in to the model.

Anyone who wants to get to the bottom of the model before putting an AI on it can read our article about the Eisenhower matrix: that holds the full explanation with background and examples, without your having to install anything. This page and that article are deliberately two sides of the same subject: there the framework, here the skill that carries the framework out for you every day.

And an honest note belongs with it. What you have here is a sorting model, not science about how your brain works. Its strength is in the simplicity: two questions per task, four possible outcomes. That also means the quality of the sorting depends on how honestly you answer the question whether something really contributes to your goals. That is why the skill sets the definitions in advance and is strict about them, because without that strictness everyone sorts everything into important. To find out which part of your work delivers most, you can supplement the sorting with the Pareto Analyst, which goes looking for the small group of tasks with the biggest impact.

You can improve your week with the model without installing the skill as well: define urgent and important before you sort, give every task a quadrant and an action, and protect at least one block a day for quadrant 2.

The zip contains one folder, ai-eisenhower-matrix-coach, with the SKILL.md inside it. Installing is a matter of putting that folder in the right place, and that place differs per environment. SKILL.md has been an open standard since December 2025, so the same skill also works in Codex, Cursor and Gemini CLI. You are therefore not downloading a Claude file but a working instruction that any modern AI assistant can read. The full guide per environment is in installing Claude skills.

After that, use is simple: paste your list and ask for priority. That may be a task list, a calendar, a project, a summary of your inbox or a list of decisions; the rawer the better, because the coach asks the two questions it needs to make it concrete. If you are new to skills and want to understand how this kind of file works first, the knowledge base holds the broader explanation of working with AI.

At its strongest it is on the days when more is coming at you than fits in a day: the start of the week with a list that has run over, the return from holiday with a stuffed inbox, the project that suddenly has three deadlines at once. The file names the cases itself: task lists, projects at company level, weekly planning, summarising a full inbox and decisions where several choices compete for attention. In all those cases the method is the same: definitions first, then sorting, then the pattern, then the day start.

There are also situations where you are better off leaving it alone, and the file is explicit about them: purely creative sessions, brainstorms and emotional conversations. A different framework fits there. A brainstorm precisely does not want a judgement about what is important, and a conversation about how someone feels is not a list you chop into quadrants.

For processing everything that comes at you into a reliable system there is the Getting Things Done Coach, and for actually protecting your deep work blocks the Flow State Coach: those three complement each other instead of replacing each other. And for the part the matrix cannot do at all, making the quadrant 2 block happen week after week instead of only being scheduled, there is the Atomic Habits Coach.

The most important limit is the same as with every prioritisation system: the matrix sorts what you supply, it does not know your obligations. If you do not mention a deadline, the coach cannot see it, and if you say of every task that it contributes to your goals, even the strictest definition sorts everything into important. Asking on and defining strictly catches a lot, but honesty about your own week stays your work. What it does guarantee: what you supply comes back as a list you can start on tomorrow instead of a list you stare at again tomorrow.

There is a good chance that something like finally tackling the website or becoming more visible sits in your quadrant 2, because that is exactly the kind of important work without a deadline that gets left. If you want to know how pressing that block really is, the free SEO scan shows in a few seconds where your site stands. And if you want to talk further about what AI can do for your business, from separate skills to full automation, we simply do that in a conversation.