agentleFS
varunk130varunk130/claude-code-skills/skills/strategic-management/swot-tows-analyzer/SKILL.md

swot-tows-analyzer

Skill1 starsChanged 21 days agoMITView on GitHub

Performs a structured Strengths-Weaknesses-Opportunities-Threats (SWOT) analysis plus a Threats-Opportunities-Weaknesses-Strengths (TOWS) matrix that pairs internal strengths and weaknesses with external opportunities and threats to generate concrete strategic options. Use when refreshing strategy after a major external change, framing a strategic-planning offsite, justifying a market move with internal-versus-external logic, or producing a quick but rigorous strategic situation read.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    After a material external change (regulatory shift, new entrant, macro event)

    line 25
  2. Distinctive:

    Before drafting any quadrant, gather:

    line 32
  3. Distinctive:

    Test each strength for distinctiveness, not just presence

    line 135
  4. Distinctive:

    Treat SWOT as the deliverable - TOWS is the deliverable

    line 142

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

SWOT-TOWS Analyzer

Goes beyond a SWOT list - pairs internal and external factors to produce real strategic options.

What this skill is

A workflow that runs a disciplined Strengths-Weaknesses-Opportunities-Threats (SWOT) analysis with evidence requirements, then constructs the Threats-Opportunities-Weaknesses-Strengths (TOWS) matrix to generate four families of strategic options: SO (use strengths to capture opportunities), ST (use strengths to defend against threats), WO (fix weaknesses to capture opportunities), and WT (fix weaknesses to defend against threats). Forces the team to act on the SWOT, not just describe it.

What it solves

  • SWOT outputs that are uncritical lists ("our team is great") with no evidence
  • Internal-only or external-only analyses that miss the pairing
  • SWOT documents that produce no actionable strategy
  • Confusion between capabilities (internal) and trends (external)
  • Strategy memos that pivot on a single threat or opportunity without considering counters

When to invoke

  • Annual strategic planning offsite
  • After a material external change (regulatory shift, new entrant, macro event)
  • Onboarding a new executive or board member to the strategic context
  • Defending or challenging a major commitment with internal-versus-external logic
  • Quick-turn strategy brief when a deeper framework isn't warranted

Phase 1: Source the evidence

Before drafting any quadrant, gather:

  • Customer satisfaction and retention data
  • Financial trends (revenue, margin, share, capital structure)
  • Competitive intelligence (recent moves, hires, pricing, partnerships)
  • Industry analyst reports
  • Internal capabilities assessment (skills, intellectual property, data, technology, brand)
  • Employee survey signals
  • Macroeconomic and regulatory trackers

Each quadrant entry must reference a source. "No evidence" is itself an entry - flag it.

Phase 2: Strengths

Internal factors today, observable, distinctive versus competitors. Bar to clear:

  • Is it actually distinctive, or just present? (Every player has a website.)
  • Is it observable and measurable? (Customer perception, market share, Net Promoter Score (NPS), win rate.)
  • Is it sustainable, or eroding?

For each strength, score:

  • Distinctiveness versus competitors (1-5)
  • Trajectory (improving / stable / eroding)

Phase 3: Weaknesses

Internal factors that depress performance versus competitors or versus ambition. Honest list.

Test each weakness:

  • Material - does it actually impair execution or perception?
  • Comparative - relative to whom?
  • Actionable - within management control?

Common honest-weakness categories: capability gaps, data gaps, technical debt, organizational design, cultural friction, distribution gaps.

Phase 4: Opportunities

External trends, gaps, or events the company could capture. Sources:

  • Underserved segments (from a Jobs-to-be-Done (JTBD) or market-sizing analysis)
  • Regulatory tailwinds
  • Adjacent markets enabled by current capabilities
  • Distribution channel shifts
  • Competitor missteps
  • Technology inflection points

Quality bar: an "opportunity" must specify the action available, not just describe a trend.

Phase 5: Threats

External factors that could damage the business. Sources:

  • New entrants (specifically - who?)
  • Substitute technologies or business models
  • Regulatory headwinds
  • Customer-segment decline
  • Macroeconomic, foreign-exchange, or supply-chain risk
  • Reputational risk

For each threat: probability (low / medium / high), severity (low / medium / high), time horizon (now / 1 year / 3 years).

Phase 6: Construct the TOWS matrix

OpportunitiesThreats
StrengthsSO - Maxi-Maxi: use strengths to capture opportunitiesST - Maxi-Mini: use strengths to defend against threats
WeaknessesWO - Mini-Maxi: fix weaknesses to capture opportunitiesWT - Mini-Mini: defensive moves, retreat, divest

For each cell, generate 2-4 specific strategic options that pair a real internal factor with a real external one. Example:

  • SO: "Our distribution scale × new buyer segment X → launch dedicated stock-keeping unit in Q2"
  • WT: "Our technical-debt weakness × incumbent moving into our space → consider partnership or divest non-core line"

Generic statements ("invest more") are not strategic options.

Phase 7: Filter to a shortlist

For each candidate option, score 1-5:

  • Strategic fit (with stated direction)
  • Resource feasibility (capital, talent, capacity)
  • Time-to-impact
  • Reversibility
  • Risk-adjusted upside

Shortlist the top 5-7 options across the four quadrants. Reject options that exist in only one quadrant - strategy that pairs only strengths with opportunities ignores defense.

Phase 8: Action plan

For each shortlisted option:

  • Owner (single name, not a function)
  • Specific first 90-day actions
  • Resource ask
  • Success metric and review cadence
  • Kill criterion (when do we stop?)

Output

  • Evidence-anchored SWOT with sources per item
  • TOWS matrix with 8-16 specific strategic options
  • Shortlist of 5-7 priorities with scoring
  • 90-day action plan per priority
  • Watch-list: which external signals would shift the analysis
  • Pre-mortem: how each top option could fail

Operating rules

Always

  • Cite a source for every SWOT item
  • Test each strength for distinctiveness, not just presence
  • Generate options across all four TOWS quadrants
  • Pair specific internal with specific external factors
  • Assign single-owner accountability

Never

  • Confuse capabilities with trends (or vice versa)
  • Treat SWOT as the deliverable - TOWS is the deliverable
  • Generate generic options ("invest more")
  • Skip the threat or weakness quadrant because it's uncomfortable
  • Score options only on upside (ignore downside and reversibility)

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.