Token导航 LogoToken导航TokenDH.com
运维和基础设施需要联网github未标认证来源可访问许可证需确认审计通过

biz-swot商业 swot

Agent Skill

biz-swot 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

380

周安装

16

GitHub Stars

125

下载量

133
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:biz-swot(商业 swot)
来源仓库:https://github.com/asgard-ai-platform/skills
仓库路径:skills/biz-swot
安装命令:
npx skills add https://github.com/asgard-ai-platform/skills --skill biz-swot
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/asgard-ai-platform/skills --skill biz-swot

简介

biz-swot 结合 TOWS 矩阵将内外部因素交叉匹配,生成 actionable 战略选项。

  • 适用于团队复盘、项目评估或制定攻防策略时的系统化思考场景。
  • 使用时列出优势、劣势、机会、威胁,工具生成 SO/WO/ST/WT 四类策略建议。
  • 安装需通过 npx 添加 GitHub 仓库,建议确认是否支持优先级排序与资源分配建议。
  • 注意:分类为运维和基础设施,强调其结构化思维工具属性,非自动决策系统。

SKILL.md

SWOT Analysis with TOWS Matrix

Overview

SWOT structures strategic assessment by separating internal factors (Strengths, Weaknesses) from external factors (Opportunities, Threats). The TOWS matrix then crosses these four quadrants to generate concrete strategy options. This skill guides the full workflow: from factor identification through prioritization to actionable strategy formulation.

When to Use

Trigger conditions:

  • User asks to assess a company, product, team, or project's strategic position
  • User needs to identify advantages, risks, or competitive factors
  • User wants to turn a situational analysis into strategy options
  • User mentions "SWOT", "strengths and weaknesses", or "strategic assessment"

When NOT to use:

  • For industry-level competitive dynamics → use Porter's Five Forces
  • For macro-environment scanning → use PESTEL
  • For product portfolio decisions → use BCG Matrix
  • When the user only needs financial analysis, not strategic positioning

Framework

IRON LAW: Internal vs External Classification

Strengths and Weaknesses are INTERNAL — they originate from within the
organization and the organization can directly control or change them.
Examples: proprietary technology, brand reputation, team expertise, cost
structure, operational processes.

Opportunities and Threats are EXTERNAL — they originate from the environment
and the organization cannot directly control them.
Examples: market trends, regulatory changes, competitor actions, economic
conditions, technological shifts.

NEVER classify an external trend as a Strength or Weakness.
NEVER classify an internal capability as an Opportunity or Threat.

Test: "Can the organization decide to change this tomorrow?"
  YES → Internal (S or W)
  NO  → External (O or T)
IRON LAW: Completeness Before Synthesis

Complete ALL four quadrants before generating strategies.
Do NOT jump to recommendations after identifying only strengths and
opportunities. Skipping W or T produces dangerously optimistic strategies.

Step 1: Identify Internal Factors (S and W)

Examine the organization's resources, capabilities, and performance:

  • Tangible: financial resources, physical assets, technology, patents
  • Intangible: brand equity, culture, expertise, relationships, reputation
  • Capabilities: processes, skills, management quality, innovation track record

For each factor, classify as Strength (competitive advantage) or Weakness (competitive disadvantage) relative to competitors. Be specific — "good team" is too vague; "engineering team with 5+ years experience in ML deployment" is actionable.

Step 2: Identify External Factors (O and T)

Scan the environment across these dimensions:

  • Market: growth trends, customer needs shifts, new segments
  • Competitive: competitor moves, new entrants, substitutes
  • Macro: regulatory, economic, technological, social changes
  • Industry-specific: supply chain shifts, channel evolution, standards changes

For each factor, classify as Opportunity (favorable) or Threat (unfavorable). Ground each factor in evidence — cite data, trends, or specific events when possible.

Step 3: Prioritize Factors

Not all factors carry equal weight. For each quadrant, rank factors by:

  1. Impact: How significantly would this affect the organization? (High / Medium / Low)
  2. Likelihood (for O and T): How probable is this? (High / Medium / Low)
  3. Urgency: Is this time-sensitive?

Keep the top 3-5 factors per quadrant for the TOWS matrix. Including too many dilutes the analysis.

Step 4: Build the TOWS Matrix

Cross the four quadrants to generate four types of strategies:

OpportunitiesThreats
StrengthsSO strategies: Use strengths to capture opportunitiesST strategies: Use strengths to defend against threats
WeaknessesWO strategies: Address weaknesses to capture opportunitiesWT strategies: Minimize weaknesses to avoid threats

For each cell, generate 1-3 specific strategy options. Each strategy must reference at least one factor from each axis (e.g., SO strategy must name a specific strength AND a specific opportunity).

Step 5: Formulate Action Plan

Convert the most promising TOWS strategies into actionable recommendations:

  1. Select the 3-5 highest-impact strategies across all four cells
  2. For each, define: objective, owner, timeline, resources needed, success metric
  3. Flag dependencies and potential conflicts between strategies

Output Format

# SWOT Analysis: {Subject}

## Internal Factors

### Strengths
| # | Factor | Evidence | Impact |
|---|--------|----------|--------|
| S1 | {specific strength} | {supporting data} | High/Med/Low |
| S2 | ... | ... | ... |

### Weaknesses
| # | Factor | Evidence | Impact |
|---|--------|----------|--------|
| W1 | {specific weakness} | {supporting data} | High/Med/Low |
| W2 | ... | ... | ... |

## External Factors

### Opportunities
| # | Factor | Evidence | Likelihood |
|---|--------|----------|-----------|
| O1 | {specific opportunity} | {supporting data} | High/Med/Low |
| O2 | ... | ... | ... |

### Threats
| # | Factor | Evidence | Likelihood |
|---|--------|----------|-----------|
| T1 | {specific threat} | {supporting data} | High/Med/Low |
| T2 | ... | ... | ... |

## TOWS Strategy Matrix

| | Opportunities (O1, O2...) | Threats (T1, T2...) |
|---|---|---|
| **Strengths** | SO: {strategy using S to capture O} | ST: {strategy using S to counter T} |
| **Weaknesses** | WO: {strategy to fix W and capture O} | WT: {strategy to minimize W and avoid T} |

## Recommended Actions
1. **{Strategy name}** — {description} (from: {SO/ST/WO/WT})
   - Timeline: ...
   - Success metric: ...
2. ...

Examples

Correct Application

Scenario: SWOT for a mid-size Taiwanese bubble tea chain considering expansion to Japan

Analysis:

QuadrantFactorClassificationReasoning
SProprietary tapioca pearl recipe with unique textureInternal ✓Company's own R&D product
S50 stores in Taiwan with proven SOPInternal ✓Company's operational asset
WNo Japanese-speaking management teamInternal ✓Company's own resource gap
WLimited capital for overseas expansionInternal ✓Company's financial constraint
OJapanese bubble tea market growing 15% YoYExternal ✓Market trend, not company-controlled
OJapan-Taiwan tourism recovery post-COVIDExternal ✓Macro environment factor
TEstablished Japanese competitors (Gong Cha, CoCo)External ✓Competitor landscape
TYen depreciation increasing import costsExternal ✓Economic condition

TOWS strategy example:

  • SO: Leverage proprietary recipe (S1) to differentiate in the growing Japanese market (O1) — position as "authentic Taiwanese craft tea"
  • WT: Address capital limitation (W2) by minimizing currency risk (T2) — source ingredients locally in Japan where possible

Incorrect Application

Scenario: Same bubble tea chain

What went wrong:

FactorPlaced InShould BeWhy
"Japanese bubble tea market growing 15% YoY"StrengthOpportunityMarket growth is an external trend — the company cannot control it. Violates Iron Law: internal factors only in S/W.
"Our team lacks experience"ThreatWeaknessTeam composition is internal — the company controls who it hires. Violates Iron Law: external factors only in O/T.
"Good brand"Strength ⚠️Needs specificityToo vague to be actionable. What makes the brand good? Recognition in Taiwan? Social media following? Specific awards?

Gotchas

  • Internal/External confusion with "market position": "We are the #3 player" feels internal but the ranking itself is determined by market dynamics. Split it: "Strong distribution network in northern Taiwan" (S, internal capability) vs "Market consolidation reducing number of competitors" (O or T, external trend).
  • Strengths that are actually table stakes: "We have a website" is not a strength if every competitor also has one. Strengths must be relative advantages vs competitors.
  • Confusing absence of threat with opportunity: "No major competitor in this niche" is NOT an opportunity — it may signal the niche is not viable. An opportunity requires a positive external trend or event.
  • TOWS strategies that only reference one axis: "Expand to Japan" is not a TOWS strategy. It must cross quadrants: "Leverage proprietary recipe (S1) to enter the growing Japanese market (O1)."
  • Scope drift: SWOT for "the company" is too broad. Scope to a specific decision: "SWOT for expanding to Japan" or "SWOT for launching a new product line."
  • Recency bias: Recent events dominate the analysis. Force consideration of structural, long-term factors alongside current events.

References

  • For detailed TOWS matrix case studies, see references/tows-case-studies.md
  • For comparison with other strategy frameworks (Porter's, PESTEL, BCG), see references/framework-comparison.md

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

34.58%
按下载量换算46

Claude

32.09%
按下载量换算43

Cursor

18.9%
按下载量换算25

Gemini CLI

8.95%
按下载量换算12

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills