SWOT strategic analysis examining Strengths, Weaknesses, Opportunities, and Threats. Use for strategic planning, competitive analysis, career decisions, or evaluating opportunities.
npx skills add https://github.com/neurofoo/agent-skills --skill swot
Perform a strategic analysis examining Strengths, Weaknesses, Opportunities, and Threats.
First clarify the subject and objective of the analysis. Then systematically examine each quadrant, considering both internal capabilities and external factors.
Subject: What are we analyzing?
Objective: What are we trying to achieve?
SWOT Matrix
| | Helpful | Harmful |
|---|---------|---------|
| Internal | STRENGTHS | WEAKNESSES |
| | - [strength 1] | - [weakness 1] |
| | - [strength 2] | - [weakness 2] |
| | - [strength 3] | - [weakness 3] |
| External | OPPORTUNITIES | THREATS |
| | - [opportunity 1] | - [threat 1] |
| | - [opportunity 2] | - [threat 2] |
| | - [opportunity 3] | - [threat 3] |
Strengths (Internal, Positive)
What advantages do you have? What do you do well? What resources do you have? What do others see as your strengths?
Weaknesses (Internal, Negative)
What could you improve? What do you lack? What do others see as weaknesses? Where are you vulnerable?
Opportunities (External, Positive)
What trends could you take advantage of? What opportunities are open to you? How can you turn strengths into opportunities?
Threats (External, Negative)
What obstacles do you face? What is your competition doing? Are there changing requirements or standards? Could weaknesses threaten your position?
Strategic Combinations
| Combination | Strategy |
|-------------|----------|
| S-O (Strengths + Opportunities) | How to leverage strengths to capture opportunities |
| W-O (Weaknesses + Opportunities) | How opportunities can help overcome weaknesses |
| S-T (Strengths + Threats) | How to use strengths to counter threats |
| W-T (Weaknesses + Threats) | Where you're most vulnerable; what to shore up |
Key Insights
Top 3 strategic implications from this analysis.
Recommended Actions
Specific next steps based on the SWOT.
$ARGUMENTS
This skill should be used when the user asks to "plan a penetration test", "create a security assessment checklist", "prepare for penetration testing", "define pentest scope", "follow security testing best practices", or needs a structured methodology for penetration testing engagements.
Use when the user supplies or imports existing security findings, vulnerability reports, or security/vulnerability Jira/Linear tickets from scanners, advisories, GitHub, Atlassian Rovo, Linear, or similar backlog sources and wants static repo-impact triage. Do not use for discovery, duplicate-bug triage, validation, or fixes.
Orchestrate multiple Antigravity skills through guided workflows for SaaS MVP delivery, security audits, AI agent builds, and browser QA.
Integrates with Atlassian products to manage project tracking and documentation via MCP protocol. Use when querying Jira issues with JQL filters, creating and updating tickets with custom fields, searching or editing Confluence pages with CQL, managing sprints and backlogs, setting up MCP server authentication, syncing documentation, or debugging Atlassian API integrations.
Security payloads, bypass tables, wordlists, gf pattern names, always-rejected bug list, and conditionally-valid-with-chain table. Use when you need specific payloads for XSS/SSRF/SQLi/XXE/NoSQLi/command injection/SSTI/IDOR/path-traversal/HTTP smuggling/WebSocket/MFA bypass, or bypass techniques. Submittability and the always-rejected / what-NOT-to-submit decision are owned by triage-validation.
Security planning reference set for operational buckets, STRIDE analysis, standards mapping, NIST control families, and backlog scaffolding.
Use when an agent folder must pass the Agentlas Cloud 2-stage security scan (static rules + BYOK LLM judgment) before private sync or public publish, or when asked to run/interpret `hephaestus security scan`.
> Cross-functional what-if modeling for compound adversity -- shows how one problem cascades into the next. Use when facing complex risk scenarios, strategic decisions with major downside, or multi-variable threats.
Take neurofoo/swot from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.