swot-analysis

swot-analysis is a skill for Claude Code from konglong87/methodology-skills. It costs 92 tokens per session (5,182 once invoked), scanned A, original, MIT.

A structured way to assess a decision by listing internal strengths and weaknesses, then external opportunities and threats. SWOT stands for Strengths, Weaknesses, Opportunities, and Threats.

In plain words
What is it for?
Use it for project proposals, technology choices, competitor comparisons, risk reviews, problem diagnosis, and business or product planning.
Why use it?
It reduces one-sided decisions by considering both what an option can do well and what could go wrong around it. It also connects the assessment to possible strategies and actions.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Good fit Use it for project proposals, technology choices, competitor comparisons, risk reviews, problem diagnosis, and business or product planning.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/konglong87/methodology-skills/swot-analysis
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add konglong87/methodology-skills --skill swot-analysis
Clone the repo
git clone --depth 1 https://github.com/konglong87/methodology-skills

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for swot-analysis

README.md
[![agentmods](https://agentmods.dev/badge/skills/konglong87/methodology-skills/swot-analysis/github.svg)](https://agentmods.dev/skills/konglong87/methodology-skills/swot-analysis)
Your own site
<a href="https://agentmods.dev/skills/konglong87/methodology-skills/swot-analysis"><img src="https://agentmods.dev/badge/skills/konglong87/methodology-skills/swot-analysis/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for swot-analysis

Your own site · 80×15
<a href="https://agentmods.dev/skills/konglong87/methodology-skills/swot-analysis"><img src="https://agentmods.dev/badge/skills/konglong87/methodology-skills/swot-analysis.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 92 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 5,182 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00092 $0.05182
Opus 5 $0.00046 $0.02591
Sonnet 5 $0.00018 $0.01036
Haiku 4.5 $0.00009 $0.00518

Measured 10d ago against content hash 45b81359a159, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

swot-analysis scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 10d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/swot-analysis/SKILL.md · 565 lines

How it starts

The opening of the file, as written. The whole thing — 565 lines — stays where its author put it; the contents beside it link to each section on GitHub.

前置协议

环境检测

PROJECT_ROOT=$(git rev-parse --show-toplevel 2>/dev/null || echo "unknown")
BRANCH=$(git branch --show-current 2>/dev/null || echo "unknown")
COMMIT=$(git rev-parse --short HEAD 2>/dev/null || echo "unknown")

echo "PROJECT: $PROJECT_ROOT"
echo "BRANCH: $BRANCH"
echo "COMMIT: $COMMIT"

前置技能检查

# 检查前置工件
GOAL_ARTIFACT="memory/artifacts/goal-oriented/latest.json"
FP_ARTIFACT="memory/artifacts/first-principles/latest.json"

if [ -f "$GOAL_ARTIFACT" ]; then
  echo "FOUND: goal-oriented artifact"
fi

if [ -f "$FP_ARTIFACT" ]; then
  echo "FOUND: first-principles artifact"
fi

mkdir -p memory/artifacts/swot-analysis

Overview

SWOT分析是一种战略规划工具,通过系统性地分析对象的内部优势劣势,外部机会威胁,帮助做出更明智的决策。

核心价值

  • 提供全景式现状评估,避免片面判断
  • 内外因素结合,平衡客观与主观
  • 从分析到策略,直接产出可执行方案
  • 适用广泛,从产品规划到技术选型均可使用

两阶段模式

  1. 分析阶段:识别并填充S、W、O、T四个维度
  2. 策略阶段:通过TOWS矩阵交叉分析,生成SO/WO/ST/WT四类策略

关键区别

  • 简单列表式SWOT:只列出四个象限,无后续行动
  • 战略式SWOT:分析→策略→行动,形成闭环

When to Use

适用场景

  • 项目立项或新功能规划(评估可行性和风险)
  • 技术选型和架构决策(对比多个方案)
  • 竞品分析和市场进入策略
  • 问题诊断和瓶颈突破
  • 资源分配和优先级排序
  • 战略规划和业务决策
  • 用户明确要求"SWOT分析"或"优劣势分析"

不适用场景

  • 简单明确的小决策(杀鸡用牛刀)
  • 纯技术问题调试(需要debugging skill)
  • 已有明确最优方案的选择
  • 数据驱动的A/B测试(SWOT是定性分析)

快速判断是否使用SWOT

是否需要决策?
├─ 否 → 不需要SWOT
└─ 是
   └─ 问题是否复杂多因素?
      ├─ 否 → 简单决策框架即可
      └─ 是
         └─ 是否涉及内外部因素?
            ├─ 仅内部 → 考虑根因分析/5Whys
            ├─ 仅外部 → 考虑PESTEL/波特五力
            └─ 内外都有 → ✅ 适合SWOT

The Process

digraph swot_analysis {
    rankdir=TB;

    "定义分析对象" [shape=box, style=filled, fillcolor="#e0e0e0"];
    "收集信息" [shape=box, style=filled, fillcolor="#c8e6c9"];
    "填充SWOT矩阵" [shape=box, style=filled, fillcolor="#bbdefb"];
    "用户选择模式" [shape=diamond, style=filled, fillcolor="#fff9c4"];
    "简洁输出" [shape=box, style=filled, fillcolor="#f8bbd0"];
    "TOWS交叉分析" [shape=box, style=filled, fillcolor="#e1bee7"];
    "生成策略建议" [shape=box, style=filled, fillcolor="#ffccbc"];
    "输出完整报告" [shape=doublecircle, style=filled, fillcolor="#81c784"];

    "定义分析对象" -> "收集信息";
    "收集信息" -> "填充SWOT矩阵";
    "填充SWOT矩阵" -> "用户选择模式";
    "用户选择模式" -> "简洁输出" [label="简洁模式"];
    "用户选择模式" -> "TOWS交叉分析" [label="详细模式"];
    "TOWS交叉分析" -> "生成策略建议";
    "生成策略建议" -> "输出完整报告";
    "简洁输出" -> "输出完整报告";
}

Read the full file on GitHub · 565 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 10d ago First seen · 565 lines · 92 tokens per session scan A 45b81359a159

Subscribe to this mod's changes

swot-analysis is a skill published in the GitHub repository konglong87/methodology-skills (5 stars, last pushed 1mo ago), licensed MIT. It adds 92 tokens to every session and 5,182 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

importing-a-codebase

Use when the repo holds real source code but no specs: the existing-codebase branch of setting-up-a-project, normally reached via that dispatcher, directly only when the situation is unmistakable. Not for empty workspaces (starting-a-new-project) or feature work in a specced project (brainstorming).

JetBrains/thinkrail · 69 tokens

starting-a-new-project

Use when the workspace is empty — no code yet — and the user brings a raw idea: the brand-new branch of setting-up-a-project, normally reached via that dispatcher, directly only when the situation is unmistakable. Not for features in an existing project — use brainstorming instead.

JetBrains/thinkrail · 61 tokens

todos

This chat has a shared, live TODO plan — your tasks for the conversation, which the user also edits. Read this skill and reach for the todo tools whenever a request takes more than a couple of steps. It covers the plan model (group = task, items = its steps; loose items are the user's lane), how to work it: propose…

JetBrains/thinkrail · 127 tokens

writing-workflow-skills

Use when adding a new workflow skill to pi-thinkrail-workflow, changing an existing workflow skill's role, trigger, handoff, or structure, or checking a workflow skill against the workflow system's rules. Not for authoring general-purpose skills outside this package.

JetBrains/thinkrail · 60 tokens

brainstorming

Use this BEFORE any creative or feature work: building a new feature, adding functionality, changing behavior, or making a nontrivial design decision. Turns the user's request into a validated design — recorded as a spec-graph task-spec — before any implementation. Do not skip this because a change looks small.

JetBrains/thinkrail · 65 tokens

reviewing-changes

Use when a review package asks you to review a plan step's change set (todo.startReview): you are the REVIEWER, not the author. How to judge an agent-written diff, file findings with addreviewcomment, and settle with exactly one reviewverdict.

JetBrains/thinkrail · 59 tokens