# Swot Analysis

Build an evidence-cited SWOT of one company, yours or a competitor's, from public...

- Repository: https://github.com/deanpeters/Product-Manager-Skills (7825 stars)
- Category: Engineering
- License: see repository
- Last updated: 2026-10-16
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add deanpeters/Product-Manager-Skills --skill swot-analysis -g -a claude-code -y`
Codex: `npx skills add deanpeters/Product-Manager-Skills --skill swot-analysis -g -a codex -y`
Cursor: `npx skills add deanpeters/Product-Manager-Skills --skill swot-analysis -g -a cursor -y`
Gemini CLI: `npx skills add deanpeters/Product-Manager-Skills --skill swot-analysis -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add deanpeters/Product-Manager-Skills`

## Description

Build an evidence-cited SWOT of one company, yours or a competitor's, from public sources, ending with the S-O/W-T crossings. Use for strategy reviews, board prep, or competitor depth.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# SWOT Analysis (Evidence-Cited)

## Purpose

Build an evidence-cited SWOT of one company, yours or a competitor's, from the public record:
**use or gather evidence → four labeled quadrants → crossings → next-step options.** Strengths and
weaknesses come from documented capability and customer voice; opportunities and threats from market,
competitor, and macro signals. Every entry carries a source and a label, and the analysis ends with
the S-O and W-T crossings, because a SWOT without "so what" is a parking lot with four sections.

## Input

**Works best with:** the company to analyze, the scope (whole company or one product line/market),
and **the decision this SWOT should support**.
**Also useful:** the perspective, theirs, or yours competing with them, and any research already in
session (a [`competitive-research-snapshot`](../competitive-research-snapshot/SKILL.md), VoC themes, a
landscape scan, [`company-intel`](../company-intel/SKILL.md) output): the SWOT then *synthesizes*
instead of re-searching.

Input supplied inline with the invocation, text after the skill name, a pasted context dump, or an
appended `ARGUMENTS:` line, counts as answers already given. Use it against the question budget;
don't re-ask.

**Arriving empty-handed? That works too.** The skill opens with at most 3 questions (company + scope,
decision, perspective) and proceeds on labeled assumptions if they go unanswered.

**Example invocation:** `Evidence-cited SWOT on [Competitor A]'s mid-market product line, from our
perspective, supports the Q3 positioning refresh. Last month's snapshot is attached.`

## Key Concepts

The rest: https://github.com/deanpeters/Product-Manager-Skills/blob/HEAD/skills/swot-analysis/SKILL.md