ysskrishna/ai-agent-skills / skills/swot-analysis
swot-analysis
VerifiedUse 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.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 3.4 KB |
| references/example.md | markdown | 1.7 KB |
references/example.md
View on GitHub# Example: SWOT Analysis (light path)
Illustrative case. All details are invented.
**User:** "We are a 5-person team with a feature-flag service. Should we add an enterprise plan with SSO next year? Do a SWOT."
**Subject:** our feature-flag service. **Scope and horizon:** next 12 months. **Decision:** whether to build an enterprise plan with SSO.
**Pass:** Gather, SWOT, Prioritize, TOWS, Next steps.
**SWOT** (sources: user statements; competitor pricing pages to be checked)
| | Helpful | Harmful |
|---|---------|---------|
| **Internal** | **S1** Setup takes minutes `[user stated]`. **S2** Small team ships weekly `[user stated]`. | **W1** No audit log or role model `[user stated]`. **W2** Two engineers handle support `[user stated]`. |
| **External** | **O1** Several customers asked about SSO `[user stated]`. **O2** Larger vendors' enterprise tiers are priced high `[assumed, check pages]`. | **T1** Big vendors bundle flags into their platforms `[assumed]`. **T2** Security reviews can take months and slow sales `[assumed]`. |
**Prioritize**
- Kept: S1, W1, O1, T2. Dropped S2 and W2 for this decision (they affect pace, not whether to go).
**TOWS**
- **SO:** use fast setup (S1) to offer a guided SSO setup for the customers asking (O1).
- **WO:** build roles and an audit log (W1) first, since SSO buyers expect them (O1).
- **ST:** use fast setup (S1) as the pitch against bundled platforms (T1).
- **WT:** limit exposure to long security reviews (T2) by starting with customers who already trust the team.
**Next steps**
1. Interview the customers who asked about SSO to learn what they will pay (owner: founder, 2 weeks).
2. Check competitor enterprise pricing pages to verify O2.
3. Test first: that those customers need roles and audit logs, not only SSO.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| planning-and-task-breakdownaddyosmani/agent-skillsBreaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| screenpipethedotmack/claude-memSearch screen and audio history recorded by Screenpipe and optionally save selected context into claude-mem. Use when the user asks to recall desktop activity, a meeting, or something seen in another app through Screenpipe. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |
| contact-widgetnexu-io/open-designSelf-contained floating chat widget with welcome screen, social links, meeting button, and message input. Single HTML file, zero dependencies. | Stars: 108k | Updated | Claude CodeCodex | Verified | Install |
| meeting-notesnexu-io/open-designMeeting notes page — title bar with attendees, agenda checklist, decisions block, action items table with owners + dates, and a "next meeting" footer. Use when the brief mentions "meeting notes", "minutes", "1:1 notes", "all-hands recap", or "会议纪要". | Stars: 108k | Updated | Claude CodeCodex | Verified | Install |