/pm-competitive
Готовит многомерный разбор конкурентов — feature-матрица, SWOT с cross-strategy, 5 сил Портера, сравнение ценообразования, позиционирование, прогноз стратегических ходов и три уровня дифференциации (догнать / отстроиться / создать новое). Адаптируется под цель (продуктовый
$ npx -y skills add serejaris/personal-corp-os --skill pm-competitive --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/pm-competitive
Context preview
The summary Claude sees to decide when to auto-load this skill.
Готовит многомерный разбор конкурентов — feature-матрица, SWOT с cross-strategy, 5 сил Портера, сравнение ценообразования, позиционирование, прогноз стратегических ходов и три уровня дифференциации (догнать / отстроиться / создать новое). Адаптируется под цель (продуктовый
SKILL.md
pm-competitive.SKILL.mdname: pm-competitive
description: Готовит многомерный разбор конкурентов — feature-матрица, SWOT с cross-strategy, 5 сил Портера, сравнение ценообразования, позиционирование, прогноз стратегических ходов и три уровня дифференциации (догнать / отстроиться / создать новое). Адаптируется под цель (продуктовый дизайн / fundraising / стратегия / годовой обзор). User-invoked only — do NOT auto-trigger. Triggers on /pm-competitive, "конкурентный анализ", "разбор конкурентов", "five forces", "SWOT", "competitive analysis", "competitor comparison", "feature matrix vs competitors".
pm-competitive — Competitive analysis
Part of the Personal Corp framework — running a one-person business through AI agents. Run a systematic multi-dimensional competitor study. Branches by analysis purpose. Includes information-credibility tagging, time-stamping of all findings, and explicit separation of fact vs inference.
Inputs
| Field | Required | Notes | |---|---|---| | Competitor list | yes | 2-5 names; > 5 → batch into rounds | | Our product | no | Used for differentiation positioning | | Purpose | no | Product design / fundraising deck / strategic planning / annual review; default product design | | Dimensions | no | Features / pricing / UX / tech / business model; default features + pricing |
Step 1 — Set purpose and depth
| Purpose | Emphasis | Output focus | Length | |---|---|---|---| | **Product design** | Features + UX | Feature matrix + differentiation list | 2-3 pages | | **Fundraising deck** | Market structure + moats | Landscape map + moat analysis | 1 page | | **Strategic planning** | Full depth | SWOT + 5-Forces + pricing + roadmap | 5-8 pages | | **Annual review** | Market share change + trends | YoY changes + trend judgment | 2-3 pages |
Step 2 — Information collection
Use user-supplied materials first (URLs, screenshots, pricing pages). Tag everything with credibility and timestamp.
**Credibility tiers:**
| Tier | Sources | Tagging | |---|---|---| | **High** | Official site, pricing page, official announcements | Quote directly | | **Medium** | Media coverage, user reviews, industry reports | Cite source | | **Low** | Rumors, speculation, outdated info | Mark `[unverified]` |
**Information-collection checklist:**
| Dimension | What to collect | Typical sources | |---|---|---| | Fundamentals | Founded, funding rounds, team size, user base | Official site, business databases | | Product | Core feature list, recent updates, roadmap | Official site, changelog, blog | | Pricing | Tiers, price ranges, free-tier limits | Pricing page | | Reputation | Praise, complaints, NPS | Review sites, app stores, social platforms | | Strategy | Target market, acquisition channels, partnerships | Press, social media |
**Always tag freshness** — e.g. "based on Q1 2026 public information" — and prompt user to verify currency.
Step 3 — Porter's Five Forces
Evaluate from industry-structure angle.
| Force | Dimension | Evaluation points | |---|---|---| | **Supplier power** | Upstream dependency | Concentration of key tech/talent/resources; switching cost | | **Buyer power** | Downstream customer leverage | Customer concentration; switching cost; price sensitivity | | **New-entrant threat** | Entry barriers | Tech / capital / brand / network effects / regulation | | **Substitute threat** | Alternative solutions | What's the user's current alternative? Substitute's value-for-money? | | **Industry rivalry** | Existing-player dynamics | Competitor count, concentration, differentiation, exit barriers |
Output: each force = strong / medium / weak + one-sentence rationale. Overall industry attractiveness = high / medium / low.
Step 4 — Multi-dimensional comparison
**Feature comparison matrix (core deliverable):**
| Module | Sub-feature | Us | Comp A | Comp B | Comp C | |---|---|---|---|---|---| | {module 1} | {sub 1} | ✅ Mature | ✅ Mature | ⚠️ Basic | ❌ None | | | {sub 2} | ⚠️ Basic | ✅ Mature | ✅ Mature | ⚠️ Basic |
Legend: ✅ Mature / ⚠️ Basic (exists but limited) / ❌ Missing / 🔜 Planned
**Positioning deep-dive:**
| Dimension | Method | Scoring | |---|---|---| | **Feature score** | 1-5 per module, weighted total | 5 = best-in-class, 3 = passing, 1 = barely present | | **UX comparison** | Steps in core flow, learning curve, completion efficiency | Compare clicks + time-to-complete | | **Tech architecture** | Patterns, stack, performance, openness | API openness, integration capability, extensibility |
**SWOT per competitor:**
| | Positive | Negative | |---|---|---| | **Internal** | Strengths (core advantages) | Weaknesses (clear gaps) | | **External** | Opportunities (exploitable) | Threats (must watch) |
Each quadrant: 2-3 items, each with factual support. Banned: vague claims like "strong team" or "advanced tech".
**SWOT cross-strategies:**
| Strategy | Meaning | Direction | |---|---|---| | **SO** | Strengths × Opportunities | Use strengths to grab market window | | **WO** | Weaknesses × Opportunities | Fill gaps to capture new opportunities | | **ST** | Strengths × Threats | Use moats to defend against attacks | | **WT** | Weaknesses × Threats | Most urgent defensive priorities |
**Pricing comparison (if pricing dimension included):**
| Item | Us | A | B | C | |---|---|---|---|---| | Free-tier scope | {} | {} | {} | {} | | Entry-tier monthly | {} | {} | {} | {} | | Enterprise monthly | {} | {} | {} | {} | | Billing model | {per-seat / usage / feature-tier} | | | | | Core differentiator | {pricing strategy reading} | | | |
**Pricing-strategy types:**
- **Penetration:** low price for share (look for generous free tier)
- **Skimming:** high price, premium positioning (look for many gated advanced features)
- **Freemium:** core free, advanced paid (look at the gap between free and paid)
Step 5 — Positioning quadrant
Pick two most-discriminating dimensions (e.g. "feature depth vs ease of use", or "price vs feature breadth") and place all products into a 2×2:
| Quadran
Read more
name: pm-competitive description: Готовит многомерный разбор конкурентов — feature-матрица, SWOT с cross-strategy, 5 сил Портера, сравнение ценообразования, позиционирование, прогноз стратегических ходов и три уровня дифференциации (догнать / отстроиться / создать новое). Адаптируется под цель (продуктовый дизайн / fundraising / стратегия / годовой обзор). User-invoked only — do NOT auto-trigger. Triggers on /pm-competitive, "конкурентный анализ", "разбор конкурентов", "five forces", "SWOT", "competitive analysis", "competitor comparison", "feature matrix vs competitors".
pm-competitive — Competitive analysis
Part of the Personal Corp framework — running a one-person business through AI agents. Run a systematic multi-dimensional competitor study. Branches by analysis purpose. Includes information-credibility tagging, time-stamping of all findings, and explicit separation of fact vs inference.
Inputs
| Field | Required | Notes | |---|---|---| | Competitor list | yes | 2-5 names; > 5 → batch into rounds | | Our product | no | Used for differentiation positioning | | Purpose | no | Product design / fundraising deck / strategic planning / annual review; default product design | | Dimensions | no | Features / pricing / UX / tech / business model; default features + pricing |
Step 1 — Set purpose and depth
| Purpose | Emphasis | Output focus | Length | |---|---|---|---| | **Product design** | Features + UX | Feature matrix + differentiation list | 2-3 pages | | **Fundraising deck** | Market structure + moats | Landscape map + moat analysis | 1 page | | **Strategic planning** | Full depth | SWOT + 5-Forces + pricing + roadmap | 5-8 pages | | **Annual review** | Market share change + trends | YoY changes + trend judgment | 2-3 pages |
Step 2 — Information collection
Use user-supplied materials first (URLs, screenshots, pricing pages). Tag everything with credibility and timestamp.
**Credibility tiers:**
| Tier | Sources | Tagging | |---|---|---| | **High** | Official site, pricing page, official announcements | Quote directly | | **Medium** | Media coverage, user reviews, industry reports | Cite source | | **Low** | Rumors, speculation, outdated info | Mark `[unverified]` |
**Information-collection checklist:**
| Dimension | What to collect | Typical sources | |---|---|---| | Fundamentals | Founded, funding rounds, team size, user base | Official site, business databases | | Product | Core feature list, recent updates, roadmap | Official site, changelog, blog | | Pricing | Tiers, price ranges, free-tier limits | Pricing page | | Reputation | Praise, complaints, NPS | Review sites, app stores, social platforms | | Strategy | Target market, acquisition channels, partnerships | Press, social media |
**Always tag freshness** — e.g. "based on Q1 2026 public information" — and prompt user to verify currency.
Step 3 — Porter's Five Forces
Evaluate from industry-structure angle.
| Force | Dimension | Evaluation points | |---|---|---| | **Supplier power** | Upstream dependency | Concentration of key tech/talent/resources; switching cost | | **Buyer power** | Downstream customer leverage | Customer concentration; switching cost; price sensitivity | | **New-entrant threat** | Entry barriers | Tech / capital / brand / network effects / regulation | | **Substitute threat** | Alternative solutions | What's the user's current alternative? Substitute's value-for-money? | | **Industry rivalry** | Existing-player dynamics | Competitor count, concentration, differentiation, exit barriers |
Output: each force = strong / medium / weak + one-sentence rationale. Overall industry attractiveness = high / medium / low.
Step 4 — Multi-dimensional comparison
**Feature comparison matrix (core deliverable):**
| Module | Sub-feature | Us | Comp A | Comp B | Comp C | |---|---|---|---|---|---| | {module 1} | {sub 1} | ✅ Mature | ✅ Mature | ⚠️ Basic | ❌ None | | | {sub 2} | ⚠️ Basic | ✅ Mature | ✅ Mature | ⚠️ Basic |
Legend: ✅ Mature / ⚠️ Basic (exists but limited) / ❌ Missing / 🔜 Planned
**Positioning deep-dive:**
| Dimension | Method | Scoring | |---|---|---| | **Feature score** | 1-5 per module, weighted total | 5 = best-in-class, 3 = passing, 1 = barely present | | **UX comparison** | Steps in core flow, learning curve, completion efficiency | Compare clicks + time-to-complete | | **Tech architecture** | Patterns, stack, performance, openness | API openness, integration capability, extensibility |
**SWOT per competitor:**
| | Positive | Negative | |---|---|---| | **Internal** | Strengths (core advantages) | Weaknesses (clear gaps) | | **External** | Opportunities (exploitable) | Threats (must watch) |
Each quadrant: 2-3 items, each with factual support. Banned: vague claims like "strong team" or "advanced tech".
**SWOT cross-strategies:**
| Strategy | Meaning | Direction | |---|---|---| | **SO** | Strengths × Opportunities | Use strengths to grab market window | | **WO** | Weaknesses × Opportunities | Fill gaps to capture new opportunities | | **ST** | Strengths × Threats | Use moats to defend against attacks | | **WT** | Weaknesses × Threats | Most urgent defensive priorities |
**Pricing comparison (if pricing dimension included):**
| Item | Us | A | B | C | |---|---|---|---|---| | Free-tier scope | {} | {} | {} | {} | | Entry-tier monthly | {} | {} | {} | {} | | Enterprise monthly | {} | {} | {} | {} | | Billing model | {per-seat / usage / feature-tier} | | | | | Core differentiator | {pricing strategy reading} | | | |
**Pricing-strategy types:**
- **Penetration:** low price for share (look for generous free tier)
- **Skimming:** high price, premium positioning (look for many gated advanced features)
- **Freemium:** core free, advanced paid (look at the gap between free and paid)
Step 5 — Positioning quadrant
Pick two most-discriminating dimensions (e.g. "feature depth vs ease of use", or "price vs feature breadth") and place all products into a 2×2:
| Quadran
Personal Corp is a way to run a one-person company through AI agents: tasks out of your head, departments instead of one person's memory, a weekly retro instead of "I'll sort it out someday".
Other skills on personal-corp-os.
- /paperclip-api
Use when managing Paperclip AI agent companies - creating tasks, managing agents, approving hires, running heartbeats, or any Paperclip control-plane operations via CLI or REST API. Triggers on "paperclip", "задача агенту", "одобри найм", "heartbeat", "запусти агента".
Open skill - /art-director
Orchestrate iterative visual style searches with branch prompts, decision graphs, feedback loops, and final direction selection.
Open skill - /cc-analytics
Use when user asks for Claude Code usage stats, weekly analytics, project activity summary, or wants to see what projects were worked on. Triggers on "аналитика", "статистика claude", "cc stats", "weekly report", "что делал
Open skill - /ceo-council
Use when needing strategic project analysis from multiple independent expert perspectives. Triggers on business decisions, growth strategy, product direction, competitive analysis, or any situation where diverse C-level opinions reduce blind spots
Open skill - /claude-md-writer
Use when creating or refactoring CLAUDE.md files - enforces best practices for size, structure, and content organization
Open skill - /corp-doctor
Use when a Personal Corp operating loop needs setup, repair, a new department, or task routing: HQ files and agent rules, GitHub issue workflow, corp-* owner map, department repositories, or deciding which repo an issue belongs to. Triggers: "corp doctor", "почини контур",
Open skill

