swot-analysis
Skill6 starsChanged 4 months agoApache-2.0View on GitHub
Use when the situation needs a balanced snapshot of position, options, and external pressure before choosing a strategy. Use when applying the SWOT Analysis consulting method and when a user asks for SWOT Analysis, method execution, structured diagnosis, or action planning.
15 other projects use a version of this.
Adopted by
Most recently taken up by
- yuusakuri/agent-skillstheir own version, first seen Nov 1, 2026
- vijaysuperpositionist/skillstheir own version, first seen Nov 1, 2026
- deanpeters/Product-Manager-Skillstheir own version, first seen Oct 25, 2026
- daviszhen/agent-skillstheir own version, first seen Oct 25, 2026
- The-Utopia-Studio/skillstheir own version, first seen Oct 13, 2026
- ysskrishna/ai-agent-skillstheir own version, first seen Oct 13, 2026
Used with
Projects with it also use brainstorm-experiments-existing, prioritize-assumptions and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
skytiger6724Skillbrainstorm-experiments-existing
Design experiments to test assumptions for an existing product — prototypes, A/B tests, spikes, and other low-effort validation methods. Use when validating assumptions, testing feature ideas cheaply, or planning product experiments.
Also in 7 projects that use this
skytiger6724Skillprioritize-assumptions
Prioritize assumptions using an Impact × Risk matrix and suggest experiments for each. Use when triaging a list of assumptions, deciding what to test first, or applying the assumption prioritization canvas.
Also in 7 projects that use this
45ckSkillpestle-analysis
Also in 7 projects that use this
About-IntelligenceSkillpositioning-ideas
Brainstorm product positioning ideas differentiated from competitors.
Also in 7 projects that use this
About-IntelligenceSkillproduct-name
Brainstorm 5 unique, memorable product names with rationale aligned to brand values and target audience.
Also in 7 projects that use this
launchapp-devSkillinterview-script
Create a structured user interview script with warm-up, core exploration, and wrap-up sections. Use when preparing for user research interviews to ensure consistent, insightful conversations.
Also in 9 projects that use this
- +6 more from skytiger6724
Other versions15 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 15
- deanpeters/Product-Manager-Skills★ 7.7ksame name
- Zafer-Liu/Data-Analysis-Agent★ 2.6ksame name
- ysskrishna/ai-agent-skills★ 20same name
- deciqAI/knowledge-skills★ 13same name
- The-Utopia-Studio/skills★ 6same name
- Adhamxon/claude-code-skills★ 2same name
- skytiger6724/qwen-skills★ 2same name
- yuusakuri/agent-skills★ 2same name
- daviszhen/agent-skills★ 1same name
- miovrag/claude-skills★ 1same name
5 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository57 other files it gives its agents.
- 5w1h-analysisSkill
- abductive-reasoningSkill
- account-planSkill
- affinity-diagramSkill
- assumption-inventorySkill
- balanced-scorecardSkill
- break-even-analysisSkill
- business-model-canvasSkill
- change-event-timelineSkill
- change-impact-analysisSkill
- communications-planSkill
- competitive-positioningSkill
- constraint-analysisSkill
- cost-benefit-analysisSkill
- critical-uncertaintiesSkill
- customer-segmentationSkill
- customer-success-health-scoreSkill
- deal-strategy-mapSkill
- decision-matrixSkill
- deductive-reasoningSkill
- effort-impact-matrixSkill
- empathy-mapSkill
- evidence-mapSkill
- fifteen-percent-solutionsSkill
- first-principles-thinkingSkill
- fishbone-diagramSkill
- five-whys-root-causeSkill
- force-field-analysisSkill
- go-to-market-diagnosisSkill
- hypothesis-treeSkill
- inductive-reasoningSkill
- issue-treeSkill
- jobs-to-be-doneSkill
- kano-modelSkill
- mece-frameworkSkill
- metrics-treeSkill
- mind-map-analysisSkill
- min-specsSkill
- north-star-metricSkill
- pestel-analysisSkill
- porter-five-forcesSkill
- power-interest-gridSkill
- pre-mortemSkill
- pricing-strategy-checkSkill
- raci-matrixSkill
- rice-scoringSkill
- risk-matrixSkill
- scenario-planningSkill
- service-blueprintSkill
- signal-vs-noise-filterSkill
- stakeholder-power-mapSkill
- systems-thinkingSkill
- user-journey-mappingSkill
- validation-planSkill
- weighted-scorecardSkill
- win-loss-reviewSkill
- wsjf-prioritizationSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 2 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 14 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 9
Use this skill to run SWOT Analysis as a practical consulting method, not as a generic framework explanation.
- Very specific: line 25
If an input is missing, do not block automatically.
- Distinctive: line 29
Do not start with an empty four-box brainstorm.
- Distinctive: line 86
Keep wording professional and plain enough that a smart non-specialist can use the output directly.
“Common” is measured: kept by at least 6 in 10 of the 14 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
SWOT Analysis
Use this skill to run SWOT Analysis as a practical consulting method, not as a generic framework explanation.
Method Notes
- Strengths and weaknesses are internal; opportunities and threats are external.
- Turn the four quadrants into strategic moves, not a brainstorm archive.
Required Inputs
Collect or infer these inputs before execution:
- objective
- internal capabilities
- external market or stakeholder context
- constraints
If an input is missing, do not block automatically. Mark it as missing, state the assumption used, and add a validation action.
When Not To Use
Do not start with an empty four-box brainstorm. Use SWOT only after the decision scope and evidence are clear, and only when the synthesis will change a choice, risk response, or action.
Adjacent Methods
pestel-analysis: examine macro external forces in depth.porter-five-forces: examine industry structure and profit pressure.competitive-positioning: define the buyer-facing choice and proof versus alternatives.
Step-by-Step Execution
| Step | Required input | How to execute | Output |
| Frame objective | Business, project, account, or decision scope. | State the decision the SWOT should inform. | SWOT objective. |
| Fill internal factors | Capabilities, assets, constraints, performance, resources. | List strengths and weaknesses that the actor can control or influence. | Strengths and weaknesses. |
| Fill external factors | Market, customer, competitor, regulatory, technology, stakeholder context. | List opportunities and threats outside the actor's direct control. | Opportunities and threats. |
| Prioritize factors | Four-quadrant list and evidence. | Rank by impact, urgency, addressability, and evidence strength. | Priority SWOT factors. |
| Convert to moves | Priority factors. | Define SO, WO, ST, and WT moves or a smaller set of practical actions. | Strategic action implications. |
Output Template
### 1. Objective And Evidence Boundary
Objective:
Scope:
Time horizon:
Evidence cut-off:
### 2. SWOT
| Quadrant | Factor | Evidence | Materiality | Controllability |
|---|---|---|---|---|
| | | | | |
### 3. Strategic Combinations
| Move | SO / WO / ST / WT | Rationale | Risk |
|---|---|---|---|
| | | | |
### 4. Priority Action
| Action | Owner | Timing | Signal | Stop condition |
|---|---|---|---|---|
| | | | | |
### Evidence And Next Decision
- Confirmed facts:
- Assumptions:
- Missing evidence:
- Next action, owner, and timing:
- Expected signal and decision threshold:Quality Gate
- Produce the method-specific outputs for Objective And Evidence Boundary, SWOT, Strategic Combinations; do not substitute a generic framework summary.
- Tie every material score, causal claim, or stakeholder judgment to evidence or label it as an assumption.
- Include at least one disconfirming check, sensitivity, alternative explanation, or failure condition appropriate to the method.
- Convert the result into a named action or decision with an owner or stakeholder, timing, and observable signal.
- State missing inputs and the smallest validation action instead of inventing precision.
- Keep wording professional and plain enough that a smart non-specialist can use the output directly.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

