EN
Language · same page NLNederlands/ai-en-automatisatie/ai-swot-analyse-skill-voor-claude/ ENEnglish (UK)/en/ai-and-automation/ai-swot-analyse-skill-voor-claude/ ESEspañolnot translated yet We do not remember your choice and never redirect you automatically.
About this choice

We only save your display preference in a preference cookie, for up to 180 days on this device. No CRM or advertising data. Your tracking consent stays unchanged. If cookies are blocked, your choice may not be saved.

~/skills/ai-swot-analysis[ok] loaded
INS.SKILL · FREE FOR CLAUDE, ALSO FOR CODEX AND CURSOR

The SWOT analysis skill for Claude

You tell Claude what your business does, why you need the analysis and what's happening in your market, and you get back a SWOT analysis that goes further than four lists. Every strength, weakness, opportunity and threat comes with a reason, then the skill crosses them in the confrontation matrix, and it finishes with an action plan whose first step can happen this week. What it isn't sure of, it doesn't present as fact but flags as an assumption. Without a follow-up, a SWOT is just a list, and this file is built to force that follow-up.

Download the skill ↓ View all skills 2.6 KB · zip with SKILL.md · MIT licence · no account needed
$ installation, line by lineFIG.00
~/.claude/skills
theseo ~ %
  inflating: ai-swot-analysis/SKILL.md
theseo ~ %
  ---
  name: ai-swot-analysis
  description: Creates a complete SWOT analysis with a confrontation matrix and a concrete action plan. Use this…
theseo ~ %
[ok] skill active · 751 words of instructions loaded

the rules above come from the zip on this page · SKILL.md is 5,391 bytes

~/skills/ai-swot-analysis/01-demonstration[run]
Section 01 · The demonstration

Situation in, strategy out

reg. S.001

This is what a session with the skill looks like, here with a made-up but recognisable example: an installation company weighing up whether to add heat pumps to its offering. The input is a few sentences of everyday language, not a filled-in form. Notice what happens to the uncertain points: they get the label assumption and are handed back to the user to confirm.

FIG.01: From situation to confrontation[#----] sheet 1/5
~/strategy · claude + ai-swot-analysis
you > build a SWOT: should I add heat pumps to my installation business?
context.txtyour answers to three questions Bergman Installatietechniek, 8 people, mostly boiler maintenance for private households and residents' associations. Goal: decide whether we'll start offering heat pumps next year. Biggest development: customers keep asking for them and two engineers want to train in it. Biggest doubt: the schedule is already full.
claude · building the analysis through the five steps...
[1/5]goal sharpened · in one sentence: decide whether heat pumps join the offering next year. Without a goal a SWOT becomes a list with no direction
[2/5]internal side · strengths and weaknesses filled in: things you have influence over, such as team, knowledge and reputation, each point with a why
[3/5]external side · opportunities and threats filled in: what comes from outside, such as demand, regulation and competition. Uncertain point flagged as [ASSUMPTION]
[4/5]confrontation matrix · internal crossed with external: grow, defend, improve, survive
[5/5]action plan · the two most important confrontations translated into actions, with a first step for this week
swot.mdshown in shortened form Strength S1: two engineers want to train in heat pumps. Why it counts: the scarcity is in people, not in demand. Weakness Z1: the schedule is full. Why it counts: without room, every new service becomes a promise you can't keep. Opportunity K1: customers are already asking about heat pumps themselves. [ASSUMPTION] that this demand holds up: confirm this with your own enquiries. Confrontation GROW: S1 meets K1. This is the offensive route: training first, offering second. Action plan, first step this week: ask the two engineers which training they have in mind and how much time it costs.
[#####] 5/5 done · every [ASSUMPTION] waits for your confirmation: the analysis doesn't pretend to know your business better than you do
5S.01 · steps in the method
4S.02 · directions in the confrontation matrix
5S.03 · edge cases the skill covers
0S.04 · euros, MIT licence, no account
S.01 to S.04 · properties of the skill file, not results or usage figures.
$ cat 01-wat-de-skill-is.md
DOC.01

What the SWOT analysis skill is

The SWOT analysis skill is a free skill from our skill library. A skill is an instruction file, SKILL.md, that gives an AI assistant a fixed way of working for one task. No software, no subscription, no connection to your systems: a single 751-word text file that tells Claude how a SWOT analysis should be built, which questions it needs to ask beforehand, how many points go in each quadrant, and that it may never stop before the confrontation matrix and the action plan are in place. You download the zip at the top of this page, put it in your Claude environment, and from that moment Claude builds strategic analyses along this logic. You can read exactly what a file like this is and how it works at what are Claude skills NL.

You'll recognise the problem this skill solves if you've ever built a SWOT. You open an empty template with four boxes, dutifully fill in some points, and after an hour you're staring at four lists you basically already knew. Strengths like good service, opportunities like social media. No decision follows, so the document disappears into a folder and the choice you made it for gets taken on gut feeling anyway. The tool isn't the problem: SWOT has been one of the most used analysis frameworks for decades. The problem is that almost nobody does the second half, crossing the quadrants, and it's exactly that second half this skill is built on.

It's written for anyone who has to choose a direction: business owners weighing up a new service, marketers building the case for a yearly plan, teams preparing a launch, and also professionals who want to review their own career, because a personal SWOT is listed as a separate edge case in the file. It's part of the skill library we make available for free from our AI and automation service, with no account and no sales email afterwards.

One thing you should know beforehand: the skill analyses, it doesn't decide. It sets out the options sharply, crosses them and says where the risk and the opportunity lie, but the choice stays yours. And the quality of the analysis stands or falls with the honesty of your input. Whoever hides their weaknesses still gets them pointed out, because calling things out is stated literally in the instructions, but whoever doesn't know their market gets assumptions back instead of certainties.

$ cat 02-waarom-de-meeste-swots-stranden.md
DOC.02

Why most SWOT analyses stall

The SKILL.md includes a list of common mistakes, and that list is essentially a summary of why most SWOT analyses never lead to a decision. Four patterns keep recurring.

The points are vague. We deliver quality isn't a strength, it's an opinion. For every point it demands a short justification: why is this a strength, what shows it, and why does it matter for the goal of this analysis. A point that can't carry a why doesn't make it into the document.

Internal and external get mixed up. Competition isn't a weakness and customer satisfaction isn't an opportunity. Strengths and weaknesses are things you have influence over: team, product, money, knowledge, reputation. Opportunities and threats come from outside: market, customer behaviour, technology, regulation, competitors. The skill keeps that split strict, because the confrontation matrix only works if the axes are clean.

The analysis stops at the list. This is the biggest one. Four filled quadrants feel like a finished product, but nothing follows from them. The confrontation matrix, crossing internal with external, is the step that turns a list into a strategy, and it's exactly the step that gets skipped in practice. In this skill it's compulsory: step four of five, not optional.

Everything has to sound positive. The moment the owner fills it in themselves, a SWOT tends to turn into a marketing leaflet. The skill's tone instruction is explicitly written against this: clear and honest, naming weaknesses without discouraging, and calling it out when everything looks like a strength.

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

~/skills/ai-swot-analysis/02-quadrants[ok]
Section 02 · The four quadrants

Internal above, external below

reg. S.002

The four quadrants from the FIG.01 example, as the skill fills them: five to seven points per quadrant in the real document, three per quadrant here for illustration. The axis split is half the work: above the line is what you have influence over, below the line is what comes from outside. The mono lines with a hash are the justification the skill demands for every point.

FIG.02: The quadrants fill up[##---] sheet 2/5
▲ INTERNAL · what you have influence over: team, product, money, knowledge, reputation
S · STRENGTHShelps your goal
S1 · two engineers want to trainthe scarcity is in people, not in demand
S2 · established customer base with maintenance contractsa warm route in to test the new offering
S3 · reputation for fixing breakdowns fasttrust is the barrier for big purchases
Z · WEAKNESSESworks against your goal
Z1 · schedule is fullwithout room, every new service becomes a promise you can't keep
Z2 · no experience yet with heat pump installationsthe learning curve costs margin on the first jobs
Z3 · website shows nothing of the new offeringanyone searching now only finds boiler maintenance
▼ EXTERNAL · what comes from outside: market, customer behaviour, technology, regulation, competitors
K · OPPORTUNITIESexternal · tailwind
K1 · customers are already asking about heat pumps themselvesdemand doesn't need creating, just answering [ASSUMPTION: confirm with your own enquiries]
K2 · existing contracts as a starting pointselling advice to someone who already trusts you is the shortest route
K3 · engineers willing to train are scarce in the marketwhoever has the team has the head start
B · THREATSexternal · headwind
B1 · bigger installers already offer itwaiting makes the gap bigger, not smaller
B2 · rules and subsidies around heating keep changingwhat you offer has to stay in line with current regulation
B3 · staff are hard to findhits Z1 directly: full is full, next year too
five to seven points per quadrant in the real document · every point carries its own why · uncertainties flagged as an assumption
$ less ai-swot-analysis/SKILL.md # 751 words of instructions
DOC.03

What's actually in the SKILL.md

A skill is only as good as its instructions, so we simply describe them here. The file opens with a frontmatter stating when Claude should pick up the skill. Not only for the literal questions like build a SWOT or strength weakness analysis, but also for phrasings with no framework in them at all: should I even do this, help me choose, analyse my business. Anyone who asks something like that while the skill is loaded gets it automatically, and that's deliberate: the people who need a SWOT most rarely ask for it in those exact words.

After that, the file sets out the division of roles. The user provides context about the situation, the goal and the market, and sharpens Claude's points with their own knowledge. If there's too little context, Claude asks a few targeted questions, fills in the four quadrants with justification, builds the confrontation matrix and delivers the action plan. The input checklist has three questions: what the business or person does and for whom, what the analysis is for (a decision, a launch, a yearly plan or a career step), and what the biggest market development or competitor is. If the user has little to offer, the skill starts with clear assumptions and flags them as an assumption, so the user can confirm or adjust them.

The core is the five-step method. First the goal in one sentence, because without a goal it becomes a list with no direction. Then the internal side: strengths and weaknesses, five to seven points per quadrant, each with a short justification. Then the external side: opportunities and threats, with the same requirement. Then the confrontation matrix, where internal is crossed with external into four directions: grow, defend, improve and survive. And finally the action plan: the two most important confrontations translated into concrete actions, with a first step for this week.

What stands out in the file is how much space the edge cases get: five of them. Little information: work with flagged assumptions. Too many points: pick the strongest five to seven. A personal SWOT: strengths and weaknesses as a professional, opportunities and threats in the field. A competitor with no internal data: work with publicly known information and flag the uncertainty. And the best edge case of all: if everything looks like a strength, Claude calls it out and names the weaknesses the user is skipping. The fixed output format closes with the SWOT numbered and justified, the confrontation matrix in four directions, and an action plan with a top priority and two follow-up actions. If you want to learn to write an instruction file like this yourself, the method is in writing a SKILL.md NL.

~/skills/ai-swot-analysis/03-confrontation-matrix[ok]
Section 03 · The confrontation matrix

Where the lists become a choice

reg. S.003

Step four is what sets this skill apart from an empty SWOT template. The quadrants from FIG.02 are set against each other: every crossing of internal and external gets a direction and a name. The four cells below light up in the order the skill works through them, and the top-left cell isn't glowing for no reason: in this example, that's where the highest priority sits.

FIG.03: The confrontation matrix, internal times external[###--] sheet 3/5
×
OPPORTUNITY · external, tailwind
THREAT · external, headwind
STRENGTH · internal, helps
GROW strength × opportunity · offensive This is where you double down: your strength meets a movement in the market heading the same way. S1 engineers want to train × K1 customers are asking: training first, offering second
DEFEND strength × threat · fending off Use your strength to fend off the threat before it hits you. S2 established contracts × B1 larger competitors: approach existing customers first
WEAKNESS · internal, holds back
IMPROVE weakness × opportunity · clear the way The opportunity is there, but your weakness blocks it: clear the weakness so you can take the opportunity. Z3 website doesn't show the offering × K1 demand already exists: make it visible first
SURVIVE weakness × threat · risk This is where the danger sits: shield it or reduce it, but don't ignore it. Z1 schedule full × B3 staff scarce: sort out capacity before you promise anything
[prio 1] GROW · make the training for the two engineers concrete: which course, how much time it costs, first step this week
[prio 2] SURVIVE · a capacity plan for the full schedule, because without room every growth route is a route on paper
[/] action plan: top priority plus two follow-up actions, the fixed close of every analysis
$ cat 04-herkomst-en-theorie.md # Stanford, Humphrey, and why the matrix belongs
DOC.04

Where SWOT comes from, and why the matrix belongs with it

The SKILL.md now distinguishes the often-repeated Humphrey attribution from the archival evidence. SWOT is linked to research at the Stanford Research Institute in the 1960s, but naming Albert Humphrey as its established sole inventor is not justified: historical research by Puyt, Lie and Wilderom shows that the technique began there as SOFT, that Robert Franklin Stewart led the work, and that Humphrey was a participant rather than the inventor (The origins of SWOT analysis, Long Range Planning 2023).

That makes the framework older than almost everything currently surrounding it in strategy models, and it has survived those decades for a simple reason: the question of what can I do, what can't I do, what's coming at me, and what helps me, is the shortest possible summary of any strategic situation.

What got added over time, especially in Dutch marketing-plan practice, is the confrontation matrix: crossing the internal axis with the external one. That isn't academic decoration. A list of strengths says nothing until you know which opportunity or threat that strength stands against. Two engineers wanting to train is a nice fact; two engineers wanting to train while customers are already asking about heat pumps is a strategy. It's exactly that crossing the skill forces, because it's the step that's almost always missing from self-made analyses.

SWOT is also rarely the only framework you need. The external row of the matrix, opportunities and threats, gets stronger the more systematically you work through the outside world, and there are separate skills for that: the PESTEL Analyst works through politics, economy, society, technology, environment and law one by one, and the Porter Five Forces Analyst NL analyses the forces in your industry, from new entrants to buyer power. Anyone who has to pick a growth direction after the SWOT can lay the four routes of the Ansoff Matrix Strategist alongside it.

And there's a fair scientific caveat worth mentioning: SWOT has faced criticism in the strategy literature for years, precisely because it so often ends as four lists with no consequence. That criticism is fair, and it's exactly why this skill makes the confrontation matrix and the action plan compulsory. The framework isn't the problem, using it half-way is the problem. Anyone who wants to test the outcome for risk afterwards can hand the analysis to the Pre-Mortem Analyst, which has you write down in advance why the plan might have failed.

Even without installing the skill, you can improve your own analysis with these principles: separate internal from external, give every point a why, and don't stop before you've crossed the quadrants.

~/skills/ai-swot-analysis/04-reality-check[ok]
Section 04 · The boundaries

What the skill doesn't let slide

reg. S.004

The edge cases and error rules from the SKILL.md, written out as the conversation in which you'd run into them. Each rule is a request you might make, together with the response the skill gives according to its own instructions. An analysis that says yes to everything isn't an analysis.

FIG.04: reality-check.log[####-] sheet 4/5
reality-check.logedge cases and error rules from the SKILL.md
keep it positive, let's leave out the weaknessesCALLED OUTWanting to sound only positive is stated literally in the list of common mistakes. If everything looks like a strength, the skill names the weaknesses you're skipping. Clear and honest is the tone instruction, naming weaknesses without discouraging.
just put competition under my weaknessesSEPARATEDInternal and external stay strictly apart. Competition comes from outside and belongs with threats. A weakness is something you have influence over. If the input mixes the two, the skill sorts them back first before building further.
I've written down twenty strengths, include them allTRIMMEDFive to seven points per quadrant, the strongest ones. More points don't make the analysis more complete, just harder to read, and the confrontation matrix becomes unworkable. The skill chooses and says why these points make the cut.
skip the confrontation matrix, the lists are enoughREFUSEDStopping at the list is the mistake this skill exists to prevent. The matrix is step four of five and is never optional: without crossing there's no direction, and without direction no action plan.
build a SWOT of my biggest competitorASSUMPTIONS ONCan do, with an honesty rule. Without internal data the skill works with publicly known information and flags every uncertainty. You get an outside-in analysis that admits as much, not false certainty about someone else's kitchen.
I don't actually know what I'm building this analysis forGOAL FIRSTNo goal, no quadrants. Step one is the goal in one sentence: a decision, a launch, a yearly plan or a career step. The skill keeps asking until that's in place, because a SWOT with no goal becomes a list with no direction.
$ unzip ai-swot-analysis-skill-for-claude.zip -d ~/.claude/skills/
DOC.05

Installing in Claude Code, Claude.ai or Codex

The zip contains a single file, SKILL.md, and that's the complete skill. Installing is simply a matter of putting that file 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. So you're not downloading a Claude file but a working instruction any modern AI assistant can read. The full guide per environment is at installing Claude skills NL.

CLAUDE CODE
  1. Unzip it into ~/.claude/skills/ (or .claude/skills/ in your project).
  2. Claude then recognises the skill automatically as soon as you start talking about a SWOT or a strategic decision.
  3. Start Claude Code with claude, then enter /ai-swot-analysis inside the session.
CLAUDE.AI
  1. Go to Customize and then Skills.
  2. Upload the zip there as a skill.
  3. Or paste the contents of SKILL.md into the project instructions of a Project.
CODEX
  1. Open AGENTS.md in your repo.
  2. Paste the contents of SKILL.md into it, or place SKILL.md alongside it as a separate file and refer to it from AGENTS.md.
  3. Codex reads that along with every session.

After that, using it is simple: say what your business does, what you need the analysis for and what's happening in your market, and ask for a SWOT. It asks about anything missing itself, so you don't need to fit anything into a format beforehand. If you're new to skills and want to understand how this kind of file works first, the knowledge base has the broader explanation of working with AI.

$ cat 06-wanneer-wel-en-niet.md
DOC.06

When to use it, and when not to

It's at its strongest at the moment there's genuinely something to choose: adding a new service or not, launching now or next year, growing as an employee or starting out on your own. In moments like that, the combination of quadrants, confrontation matrix and action plan is exactly what you need, because it pulls a gut feeling apart into checkable pieces. It works for a whole business, for a single product or service, for a personal career and for a competitor, and all four variants are described in the file.

There are also situations where you're better off leaving it alone. A SWOT is a snapshot for a decision, not a dashboard: doing it fresh every week is administrating, not choosing. For ongoing tracking of your execution, a goals framework makes more sense, such as the OKR Coach, which turns the chosen direction into measurable goals. And a SWOT isn't a revenue-model analysis: whether the heat pumps from the example actually pay off belongs in a Business Model Canvas, not in a quadrant.

The most important limit is the input. It can ask follow-up questions, flag assumptions and call things out, but it can't know what you don't tell it. For a market you don't know yourself, the outcome stays a pile of flagged assumptions, and that's exactly as it should be: the alternative is false certainty. So use the outcome the way it's meant to be used, as preparation for a decision you make, not as a replacement for it.

~/skills/ai-swot-analysis/05-upgrade-path[ok]
Section 05 · From skill to AI worker

Run it yourself, or have it run for you

reg. S.005

This skill is the free do-it-yourself version of work we also deliver as a service. It stays complete, and with no catches, but be aware what a skill actually is: it teaches your AI how to do something, while every new session starts empty. It's neither the engine nor the memory. You prompt, you supply the context about your business and your market again every time, you control it. Anyone who wants it differently has two follow-up steps: hand off the engine, or sort out the memory.

$ cat from-skill-to-ai-worker.mdthree steps, same work
upgrade-path.shfree · AI worker · brain
STEP 1 · FREE
where you are now
The skill: you're the engine You run the SWOT analysis skill yourself in Claude, Codex or Cursor. Costs nothing, works today, and you keep it entirely in your own hands: no trial period, no gated parts. The limit is your own time: the analysis only happens when you prompt it, and you have to supply your context again every session. $ claude · then /ai-swot-analysis inside the session · €0 · you prompt, you control
STEP 2 · SERVICE
a custom role
A custom role: the recalibration, not the first analysis You build your first SWOT yourself, and it gets better the longer you talk about it with the people who know the business. The three roles we set up ready-made are the Quote Worker (sorting incoming enquiries and preparing draft quotes), the Sales Worker (prospect research and outreach drafts) and the Reporting Worker (summaries and weekly and monthly reports from your own data). This work doesn't fit in there, so this becomes a custom role through Mansotti, the company TheSEO trades under. What a role like that can do is keep the recalibration going: what's changed in your market and your competitors since the last round, and which points from the action plan were left undone. That only makes sense if you genuinely hold the analysis up to the light periodically. Control stays with you, because the output stays a draft until a human gives approval. Read what an AI worker is and does. custom role, from €950 per month · a human always gives approval
STEP 3 · BRAIN
everything from one source
Jarvis: all your AI's work from the same company knowledge The skill teaches the AI, the brain is where the memory lives. Want all your AI's to work from the same company knowledge: that's Jarvis, the organisational brain. It connects ChatGPT, Claude, Codex and your people to the same projects, core knowledge and decisions, so your next AI session doesn't start from scratch. For strategic analyses this matters most of all: you no longer have to supply your goals, your market and the outcome of your previous SWOT with every single conversation. What that delivers in practice, from the plans to your first week, you can read under Jarvis itself. entry-level Brain Start: €9 per month incl. VAT · pay for your brain, not per AI query
# no marketing trick: step 1 stays free and complete. The next steps are there for anyone who wants to hand this work off.
~/skills/ai-swot-analysis/06-jarvis[ok]
Section 06 · The brain

What Jarvis delivers in practice

reg. S.006

Step 3 deserves more than a paragraph, because this is the difference between a smart chat and a system you can build on. Jarvis is the organisational brain: it remembers what your AI's need to know, distributes the work and keeps track of what happened. For an analysis skill like this one, the difference is felt straight away: a SWOT builds on goals and market knowledge, and that's exactly what the brain holds onto between sessions.

FIG.05: What an analysis session gets back from the brain[#####] sheet 5/5
jarvis · organisational brain● sync
$jarvis recall "strategic-analyses" # schematic example
[core]yearly goal: decide on expanding the offering before the end of the first quarter
[core]analysis agreement: assumptions always flagged, confrontation matrix never skipped
[task]quarterly SWOT heat pumps · draft ready · awaiting human approval
[decision]assumption about heat pump demand confirmed with own enquiries, approved by a human
[log]previous session: claude built the matrix, a human struck two points, result saved
[ok]context loaded · this session doesn't start empty
this is how every task moves through the brain: recorded → context set → delegated → human approval → saved · the full trail is at jarvis/werking
context.retained Your next session doesn't start from scratch Today you explain your goals and your market, and tomorrow a standalone chat knows nothing about it any more. With Jarvis, every session starts with the same projects, core knowledge and earlier decisions, as shown in FIG.05: recall first, only then analyse.
ai.connected ChatGPT, Claude and Codex, one source Every connected AI works from the same core knowledge and agreements. The SWOT you build and approve in Claude, ChatGPT knows about tomorrow too. You never explain anything three times, and no three separate versions of the truth appear.
tasks.tracked Tasks scheduled, tracked, marked complete A task is recorded with a goal and a deadline, picked up by the right agent and marked complete along with the result. You can see at any moment what's running, what's waiting and what's done.
everything.logged Everything logged and visible Every step leaves an auditable trail: who asked what, which sources were used, which agent worked on it and who approved it. Not because it has to, but because otherwise you can't check what happened on your behalf.
human.approval Nothing goes out without approval AI prepares, a human decides. Output stays a draft until someone approves it, and only approved knowledge feeds back into the brain. That limit applies everywhere in the system, even for work an agent has fully prepared by itself.
brain.isolated Client brain isolated If you work for multiple clients, knowledge stays strictly separated per client. What you learn for one doesn't leak into the work for another.
# THE HONEST PROOF · NOT A DEMO

We've been running on this system ourselves for months, and that's the only reason it's on this page. Every agent session, every task and every decision gets logged in it and can be read back. A new session therefore doesn't start blank: it first retrieves the recorded decisions, the running projects and the latest changes, and carries on where the previous one stopped. So we're not describing a promise but the way we work every day ourselves.

$ cat pricing.mdpay for your brain, not per AI query
Brain Start €9 /mo incl. VAT 1 organisational brain · 1 user · 1 AI worker
Brain Solo €29 /mo incl. VAT 1 organisational brain · 1 user · 3 AI workers
Brain Team €99 /mo incl. VAT 1 organisational brain · 5 users · 10 AI workers
Brain Business €249 /mo incl. VAT 3 organisational brains · 20 users · 50 AI workers

See all four plans at jarvis/prijzen NL. Through the waiting list NL, you simply pass on your preferred plan, without obligation. That doesn't create an account, an order or a payment obligation. We discuss business customisation first.

~/skills/ai-swot-analysis/07-strategy-map[ok]
Section 07 · The strategy map

The skills around it

reg. S.007

A SWOT sits in the middle of a bigger strategy cluster: outside-world analysis comes before it, and a direction and a check come after. These skills from the same library each cover a different piece.

$ claude # seven questions, seven answers
DOC.07 · FAQ

Frequently asked questions

What does the SWOT analysis skill cost?

Nothing. The skill is free, falls under the MIT licence, and you don't need to create an account or leave an email address. You download a 2.6 KB zip containing a folder and a single file, SKILL.md, and that's the complete skill. There's no paid version and no sales email follows.

Does this skill also work in Codex, Cursor or Gemini CLI?

Yes. SKILL.md has been an open standard since December 2025, so the same file also works in Codex, Cursor, Gemini CLI and other tools that follow the standard. In Codex you unzip it into .agents/skills/ in your project, or into ~/.agents/skills/ for all your projects; Codex has supported SKILL.md directly since the open standard of December 2025. Putting the contents of SKILL.md into your AGENTS.md still works too. The instructions are just ordinary readable text, so any AI assistant that accepts instruction files can work with it.

What's a confrontation matrix, and why does it belong here?

The confrontation matrix crosses your internal points with your external points and names four directions: grow where a strength meets an opportunity, defend where a strength fends off a threat, improve where a weakness blocks an opportunity, and survive where a weakness and a threat come together. Without that step, a SWOT is four lists with no conclusion. That's why the skill never skips the matrix: it's the step that turns a list into a choice.

Can I also build a personal SWOT, or one of a competitor?

Yes, both are listed as edge cases in the file. For a personal SWOT, strengths and weaknesses are filled in as a professional and opportunities and threats come from your field. For a competitor you have no internal data, so the skill works with publicly known information and explicitly flags what's uncertain. In both cases the rest of the method stays the same, including the confrontation matrix and the action plan.

What does the skill do if I give it little information?

It first asks a few targeted questions: what the business or person does and for whom, what the analysis is for, and what the biggest market development or competitor is. If there's still little to go on after that, it starts with clear assumptions and flags every assumption as an assumption, so you can confirm or adjust them. So you never get an analysis that sounds more certain than the input justifies.

How many points end up in each quadrant?

Five to seven per quadrant, each with a short justification for why the point belongs there. If you supply more, the skill picks the strongest points rather than listing everything. That's a deliberate rule from the file: nobody reads a SWOT with twenty points per quadrant, and the confrontation matrix becomes unworkable with that many.

Does the skill invent strengths just to be nice?

No, if anything the opposite. The tone instruction in the file is clear and honest: naming weaknesses without discouraging. And there's a separate edge case for the situation where everything looks like a strength: then the skill calls it out and names the weaknesses you're skipping. An analysis that only confirms what you already thought is exactly the kind of SWOT this skill tries to prevent.

$ cat 08-en-nu.md
DOC.08

First the analysis, then the visibility

There's a good chance your confrontation matrix contains an opportunity that has something to do with being found online, because that's where it sits for most businesses. If you want to know where your site stands now before you put that opportunity into a plan, the free SEO scan shows it in a few seconds. The guide which strategy model, when NL shows how this model relates to the others. And if you want to talk further about what else AI can do for your business, from individual skills to full automation, we're happy to do that in a conversation.

Section 08 · Next stepAvailable 24/7
Book a call ↗ NL
$ whoami
Gianluca, founder
Written by GianlucaFounder. Has been building visibility for Dutch businesses since 2017, in Google and in AI answers. More about the institute.