Skip to content
SkillModel-led693 tokens in use

SWOT Analysis

Lists strengths, weaknesses, opportunities and threats for a product, cross-references them for insight and ends with prioritized, owned recommendations.

28,201 stars on the repository MIT Licensephuryn/pm-skills · pm-product-strategy/skills/swot-analysis
claude plugin marketplace add phuryn/pm-skills claude plugin install pm-product-strategy@pm-skills
View source

Install command as written in the repository's README

Skill label

measured from its files

What installing SWOT Analysis costs

40tokens idle
693tokens in use

Idle is what sits in context while the skill is installed. In use is its instructions, loaded when it runs. Counts are approximate, made offline with cl100k_base.

Model dependence Model-led

Script-ledMixedModel-led

Mostly instructions, so how well it works depends on the model that follows them.

This describes the skill's structure, how much of it is scripts. It does not say how well it works.

Touches

Nothing detected: no shell, network, file writes, git or credentials in its files.

Declared tags come from the skill's frontmatter; detected ones from its scripts, its code blocks and the commands it names in inline code. This is detected, not audited.

How it scores

Quality

How well the skill is written, counted from its own files: its frontmatter, its steps, examples, stated output and constraints, its size and whether every file it ships is one it names.How we score it →
Good
  • Frontmatter12/15
  • Structure22/25
  • Examples0/15
  • Output12/15
  • Size15/15
  • Resources10/15

Security

Starts at 100 and loses points for each thing in the skill's files that a reader should look at first.How we score it →
Excellent

No findings.

Repository health

Pre-computed score based on development activity, maintenance, community, maturity, and trend momentum.How we score it →
Good
  • Development activity80
  • Maintenance76
  • Community60
  • Maturity32
  • Momentum40

SWOT Analysis guides an agent through the four quadrants for a product: internal strengths and weaknesses, external opportunities and threats. Each quadrant comes with a checklist of areas to examine, and the agent produces five to seven items for each.

It then cross-references the quadrants, asking how strengths capture opportunities and how weaknesses expose the product to threats, and turns the result into three to five recommendations with owners and metrics.

What You Get

  • Five to seven items in each of the four SWOT quadrants
  • Cross-reference insights linking strengths to opportunities and weaknesses to threats
  • Three to five strategic recommendations
  • Prioritized actions with owners
  • Metrics to track progress

Common Use Cases

  • Assessing a product’s competitive position before planning
  • Feeding a roadmap or resource allocation discussion
  • Deciding whether to build, defend, pivot or exit
  • Refreshing the analysis each quarter

What Makes It Unique

The skill goes past listing the four quadrants. It adds a cross-reference step and maps outcomes to four strategic stances: build on strengths and opportunities, defend by fortifying weaknesses against threats, pivot toward opportunities that change the competitive dynamic, or exit when threats are many and position is weak. Its notes pair well with the PESTLE skill for the external view.

Under The Hood

The skill is a single prompt file with no scripts. The agent loads the instructions and the four quadrant checklists when the skill is used and writes the analysis in the conversation. It does not call outside services, run commands or write files by itself.

Join founders building with open source

Opinionated takes, migration guides, cost-saving tips, and insights from the open source ecosystem.

Subscribe on SubstackJoin 750+ subscribers