swot-analysis
by phurynswot-analysis skill for structured SWOT assessments with actionable recommendations. Use it for strategic assessment, competitive analysis, and product or business positioning when you need a clear internal-vs-external view.
This skill scores 78/100, which means it is a solid directory listing candidate with real workflow value for agents. The repository gives users enough clarity to decide to install it: it has valid frontmatter, explicit SWOT triggers, a defined input set, and a structured analysis framework that reduces guesswork compared with a generic prompt.
- Clear triggerability: frontmatter and metadata explicitly name SWOT analysis, strategic assessment, and competitive analysis as use cases.
- Operational structure: the body lays out a stepwise SWOT framework with input requirements and category prompts for strengths, weaknesses, opportunities, and threats.
- Action-oriented scope: description says it produces actionable recommendations, making it more useful than a template-only prompt.
- No supporting scripts, references, or resources, so users must trust the in-file instructions rather than a tested workflow or external guidance.
- The repo evidence does not show a built-in install command or examples, so first-time users may need to infer how to pass inputs and expect outputs.
Overview of swot-analysis skill
What swot-analysis does
The swot-analysis skill helps you produce a structured SWOT analysis with actionable recommendations, not just a four-box summary. It is designed for product, business, and strategy work where you need to separate internal factors from external market forces and turn that into a decision-ready view.
Who should install it
Use this swot-analysis skill if you need a repeatable way to assess a product’s position, especially for competitive review, launch planning, portfolio prioritization, or stakeholder briefs. It is a good fit when you already have a rough subject in mind but need a sharper strategic read.
What makes it useful
The main value is discipline: it prompts for the inputs that actually shape a credible SWOT, such as product state, market context, capabilities, constraints, and trends. That makes the output more useful than a generic prompt because it pushes the analysis toward evidence, tradeoffs, and recommendations.
When it is a poor fit
This is not the right tool for vague brainstorming with no product context, or for deep financial modeling, market sizing, or full competitive intelligence. If you cannot describe the subject, competitors, and constraints, the analysis will be too abstract to trust.
How to Use swot-analysis skill
Install swot-analysis
Install the swot-analysis install package from the repository context with:
npx skills add phuryn/pm-skills --skill swot-analysis
After installation, confirm the skill is available in your agent environment before relying on it for a live strategy task.
Prepare inputs that matter
The swot-analysis usage works best when you provide a concise brief with these fields:
- product or business name
- what it does and for whom
- top competitors or alternatives
- current stage, traction, or limitations
- known market shifts, risks, or opportunities
A weak prompt is: “Do a SWOT for my app.”
A stronger prompt is: “Do a SWOT analysis for a B2B invoicing app used by freelancers, compared with FreshBooks and Wave, with a small team, limited budget, and strong user retention but weak brand awareness.”
Read the repo in the right order
For this swot-analysis guide, start with SKILL.md because it contains the core framework and input requirements. Since the repository has no supporting scripts, references, or resources, there is no deeper implementation layer to inspect; what matters is understanding the framework and adapting it to your case.
Get better output from the workflow
Ask for the format you want up front: concise matrix, weighted SWOT, or SWOT plus recommendations. If you need swot-analysis for Competitive Analysis, specify the competitors and the decision you are trying to support, such as positioning, feature prioritization, or market entry. That keeps the output focused on action instead of generic lists.
swot-analysis skill FAQ
Is swot-analysis only for products?
No. The skill is written for product analysis, but the same structure can help assess a service, feature, business line, or market move if you can describe the internal and external factors clearly.
How is this different from a normal prompt?
A normal prompt often produces a loose list of pros and cons. The swot-analysis skill is better for decision work because it explicitly asks for strengths, weaknesses, opportunities, and threats, then pushes toward actionable recommendations tied to real constraints.
Do I need a lot of data to use it well?
No, but you do need enough context to avoid guesswork. At minimum, provide the subject, competitors, and constraints; optional customer feedback or usage data will improve the analysis, especially for identifying threats and weaknesses.
Is it beginner-friendly?
Yes, as long as you can summarize the product or business in plain language. Beginners usually get the most value when they treat it as a guided strategy worksheet, not as a fully automated report.
How to Improve swot-analysis skill
Give sharper source material
The biggest quality lever is the brief you provide. Include evidence where possible: churn signals, pricing pressure, feature gaps, channel limits, or user feedback. Those details help the swot-analysis skill avoid generic observations.
Ask for decisions, not just categories
A useful swot-analysis usage pattern is to request “top 3 strengths, top 3 weaknesses, and the most important recommendation.” That forces prioritization and makes the output easier to act on than a long, balanced list.
Watch for common failure modes
The most common problem is mixing internal and external factors, which weakens the analysis. Another is writing threats as if they were weaknesses. If the first output is too broad, ask for tighter scope, a named competitor set, or a recommendation tied to one business goal.
Iterate after the first pass
Use the first result to refine the next prompt: ask for a deeper look at one quadrant, a different competitor set, or a revised SWOT with stronger evidence. That is usually the fastest way to turn the swot-analysis guide into a decision-ready artifact.