本文へ移動
cccskills
無料GitHub で公開

swot-analysis

Use for SWOT analysis, or when the user wants to assess where a team, product or company stands: "strengths and weaknesses", "should we enter this market?", "review our position", "competitor comparison". Turns findings into actions. Skip for detailed planning or pure market sizing.

インストール方法を見る

含まれるファイル(2)

  • SKILL.md3.2 KB
  • references/example.md1.7 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

SWOT Analysis

Sort what you know into Strengths, Weaknesses, Opportunities and Threats, then turn it into actions with TOWS. A SWOT is only useful when each cell holds evidence and the result changes a decision.

When to use

  • Assessing the position of a product, team, project, company or competitor.
  • A go / no-go on a market, partnership, or new initiative where internal fit and external conditions both matter.
  • Preparing a strategy review or a planning session.

Skip: detailed implementation plans, market sizing, or choosing between concrete options on weighted criteria.

Before you start

  1. State in one block: Subject (one entity), Scope and horizon (for example "our API product, next 12 months"), Decision it informs, and Pass (Gather, SWOT, Prioritize, TOWS, Next steps).
  2. Gather first. Read docs, metrics, customer feedback, competitor pages and the codebase where relevant. Every item needs a source or the label [user stated] or [assumed]. Ask up to 3 questions only for what tools cannot answer.
  3. Light path. Small ask: 3 items per cell, top 2 per cell kept, 1 action per TOWS pair.

Steps

1. SWOT

Place each item by one test:

  • Internal and within your control: Strength or Weakness.
  • External and outside your control: Opportunity or Threat.

Make items specific and comparative ("support answers in under 1 hour, competitors take a day" beats "great support").

HelpfulHarmful
InternalStrengthsWeaknesses
ExternalOpportunitiesThreats

2. Prioritize

Keep the 2-4 items per cell that most affect the decision. Say why the rest are dropped.

3. TOWS

Pair cells to make actions:

  • SO: use strengths to take opportunities.
  • WO: fix weaknesses that block opportunities.
  • ST: use strengths to reduce threats.
  • WT: limit exposure where a weakness meets a threat.

4. Next steps

Name the 2-3 actions with an owner (or "to be assigned"), and the one assumption to test first.

Pitfalls

  • Items with no evidence ("strong brand"). Add a source or mark [assumed].
  • Mixing internal and external: "competitor launched a feature" is a Threat, not a Weakness.
  • Long lists with no ranking. A SWOT that does not prioritize does not help a decision.
  • Stopping at the grid. Without TOWS or next steps it records opinions and decides nothing.
  • Treating one item as both a Strength and an Opportunity. Pick the cell that matches the test.

Worked example: references/example.md.

Checklist

  • Subject, scope, horizon and the decision stated
  • Each item sits in the right cell by the internal / external test
  • Items are specific, comparative and sourced or labeled
  • Priorities kept per cell
  • TOWS actions and next steps with owners

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Use for analytical thinking, or when a question needs breaking down and evidence: "why did metric X drop?", "what drives this?", "break this down", "what data do we need?". Builds a tree, hypotheses and evidence, ends with an answer and key uncertainty. Skip for quick verdicts.

日本語の概要は準備中です。原文の説明を表示しています。

ysskrishna/ai-agent-skills122026年10月8日 更新

Use for creative thinking, or when the user wants many fresh options before choosing: "give me ideas", "brainstorm names", "other ways to do this", "think outside the box". Diverges first, then picks. Skip when one answer is wanted or the task is pure execution.

日本語の概要は準備中です。原文の説明を表示しています。

ysskrishna/ai-agent-skills122026年10月8日 更新

Use for critical thinking, or when the user wants a claim, plan or decision checked for weak spots: "is this right?", "what am I missing?", "poke holes", "sanity check", "devil's advocate", "red team this". Skip for execution-only tasks and wording edits.

日本語の概要は準備中です。原文の説明を表示しています。

ysskrishna/ai-agent-skills122026年10月8日 更新

Use for design thinking, or when a product or service problem needs user understanding before solutions: "what do users really need?", "how might we...", "plan a discovery sprint", "validate this concept". Skip when the spec is frozen or the task is code maintenance.

日本語の概要は準備中です。原文の説明を表示しています。

ysskrishna/ai-agent-skills122026年10月8日 更新

Use for ethical thinking, or when a plan could harm or unfairly burden people: "should we do this?", "is this fair?", "privacy or bias risk", "who gets hurt?". Maps stakeholders, harms, power and consent. Skip for legal advice, neutral fact lookups and implementation-only work.

日本語の概要は準備中です。原文の説明を表示しています。

ysskrishna/ai-agent-skills122026年10月8日 更新

Use for Fermi estimation, or when a rough number is needed fast: "roughly how many...", "ballpark the cost", "estimate capacity or market size", "is this even feasible?". Decomposes, uses ranges and sanity-checks. Skip when exact data is available or a precise calculation is wanted.

日本語の概要は準備中です。原文の説明を表示しています。

ysskrishna/ai-agent-skills122026年10月8日 更新

ysskrishna のスキルをすべて見る

このスキルの問題を報告する