本文へ移動
cccskills
無料GitHub で公開

pm-competitive

Готовит многомерный разбор конкурентов — 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".

インストール方法を見る

含まれるファイル(4)

  • SKILL.md9.9 KB
  • assets/illustration.png464.3 KB
  • README.md1.0 KB
  • README.ru.md1.4 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

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

FieldRequiredNotes
Competitor listyes2-5 names; > 5 → batch into rounds
Our productnoUsed for differentiation positioning
PurposenoProduct design / fundraising deck / strategic planning / annual review; default product design
DimensionsnoFeatures / pricing / UX / tech / business model; default features + pricing

Step 1 — Set purpose and depth

PurposeEmphasisOutput focusLength
Product designFeatures + UXFeature matrix + differentiation list2-3 pages
Fundraising deckMarket structure + moatsLandscape map + moat analysis1 page
Strategic planningFull depthSWOT + 5-Forces + pricing + roadmap5-8 pages
Annual reviewMarket share change + trendsYoY changes + trend judgment2-3 pages

Step 2 — Information collection

Use user-supplied materials first (URLs, screenshots, pricing pages). Tag everything with credibility and timestamp.

Credibility tiers:

TierSourcesTagging
HighOfficial site, pricing page, official announcementsQuote directly
MediumMedia coverage, user reviews, industry reportsCite source
LowRumors, speculation, outdated infoMark [unverified]

Information-collection checklist:

DimensionWhat to collectTypical sources
FundamentalsFounded, funding rounds, team size, user baseOfficial site, business databases
ProductCore feature list, recent updates, roadmapOfficial site, changelog, blog
PricingTiers, price ranges, free-tier limitsPricing page
ReputationPraise, complaints, NPSReview sites, app stores, social platforms
StrategyTarget market, acquisition channels, partnershipsPress, 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.

ForceDimensionEvaluation points
Supplier powerUpstream dependencyConcentration of key tech/talent/resources; switching cost
Buyer powerDownstream customer leverageCustomer concentration; switching cost; price sensitivity
New-entrant threatEntry barriersTech / capital / brand / network effects / regulation
Substitute threatAlternative solutionsWhat's the user's current alternative? Substitute's value-for-money?
Industry rivalryExisting-player dynamicsCompetitor 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):

ModuleSub-featureUsComp AComp BComp 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:

DimensionMethodScoring
Feature score1-5 per module, weighted total5 = best-in-class, 3 = passing, 1 = barely present
UX comparisonSteps in core flow, learning curve, completion efficiencyCompare clicks + time-to-complete
Tech architecturePatterns, stack, performance, opennessAPI openness, integration capability, extensibility

SWOT per competitor:

PositiveNegative
InternalStrengths (core advantages)Weaknesses (clear gaps)
ExternalOpportunities (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:

StrategyMeaningDirection
SOStrengths × OpportunitiesUse strengths to grab market window
WOWeaknesses × OpportunitiesFill gaps to capture new opportunities
STStrengths × ThreatsUse moats to defend against attacks
WTWeaknesses × ThreatsMost urgent defensive priorities

Pricing comparison (if pricing dimension included):

ItemUsABC
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:

QuadrantTraitProducts
High features + high priceEnterprise full-stack{list}
High features + low priceBest value{list}
Low features + high priceNiche specialist{list}
Low features + low priceEntry-level{list}

Step 6 — Strategic projection

Predict competitor's likely next moves based on recent signals.

Method:

  1. Signal collection: product updates, funding moves, hiring focus, partnership announcements (last 3-6 months)
  2. Pattern recognition: what does the cluster of signals imply?
    • Repeated feature launches in area X → betting on X
    • Heavy hiring in role Y → preparing new product line
    • Price cut / new free tier → market-share grab
  3. Projection output:
CompetitorRecent movesInferred intentImpact on usConfidenceRecommended response
{A}{actions}{hypothesis}{assessment}High/Medium/Low{strategy}

Projection rules:

  • Distinguish "fact" from "inferred intent" — second always tagged with confidence
  • One signal can have multiple readings — list 2-3 most likely
  • Time windows: short-term (1-3 months), mid-term (3-12 months)

Step 7 — Three-tier differentiation strategy

TierDefinitionAction
Catch-upCompetitors have it; we don'tList features to add + priority + estimated effort
DifferentiateWe're unique or clearly aheadList strengths to reinforce + marketing message ideas
InnovateNo competitor has done it; opportunity existsList blue-ocean candidates + validation approach

Quality bar

  1. Comparisons grounded in verifiable public info; cite source + date
  2. Same dimension scored on the same scale across all products
  3. Every SWOT item backed by a fact; no fluff
  4. Differentiation suggestions concrete and prioritized
  5. All data tagged with freshness ("as of Q1 2026")
  6. Pricing data tagged with collection date
  7. Strategic projections separate fact from inference
  8. Five-Forces evaluation grounded in industry data

Red lines

  1. No fabricated data — unverified info → [unverified]
  2. No subjective trash-talk — competitor evaluation must be objective; no pejoratives
  3. Always tag freshness — every data point + collection date; nudge user to refresh
  4. Tag inference confidence — every strategic projection labeled with confidence

Market-structure judgment

StructureTraitStrategy advice
One-dominantOne player > 50% shareDifferentiate niches, avoid head-on
DuopolyTop 2 = > 70% combinedPick a side, or be the third option
FragmentedTop 5 each < 20%Speed-grab a niche #1 position
EmergingNo clear leaderEducate market first, build brand

Monitoring cadence

FrequencyWhat to monitorTrigger
WeeklyProduct changelog, social signalsMajor updates → tracker entry
MonthlyPricing changes, new features, pressUpdate feature matrix
QuarterlyFull competitor report, strategy projection refreshQuarterly competitor brief
Event-drivenFunding / M&A / major launches / exec changesImmediate impact assessment

When input is incomplete

  • Only competitor names → standard feature matrix + brief SWOT
  • No own product → competitor-vs-competitor comparison only, no differentiation advice
  • > 5 competitors → batch, or pick 3 for deep-dive + brief notes on others

Related skills

  • /pm-prd — differentiation gap → PRD
  • /pm-prioritize — catch-up feature list → RICE-rank
  • /pm-feedback — user mentions of competitors → enrich perception data
  • /pm-brainstorm — diverge on differentiation ideas

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Orchestrate iterative visual style searches with branch prompts, decision graphs, feedback loops, and final direction selection.

日本語の概要は準備中です。原文の説明を表示しています。

serejaris/personal-corp-os2292026年10月8日 更新

Audits the agent rules in the current folder (AGENTS.md, nested AGENTS.md files) and the skill descriptions the agent sees at start, then reports what to cut, move or rewrite and edits only after the user says yes. Use on «аудит правил», «проверь AGENTS.md», «почему агент не слушается правил», «проверь скиллы».

日本語の概要は準備中です。原文の説明を表示しています。

serejaris/personal-corp-os2292026年10月8日 更新

avatar

無料

Робот агента Personal Corp. Агент делает себе голову робота из набора деталей, хранит её в штабе в stack/avatars.json и кладёт в штаб страницу avatar/robot.html, где робот стоит за партой своего штаба и вокруг видны отделы, без сервера и интернета. На уроке по ссылке входа с экрана урока робот входит в живой класс и горит маячком, пока агент работает. Триггеры /avatar, /avatar <ссылка входа>, сделай себе аватар, покажи своего робота, приди на урок.

日本語の概要は準備中です。原文の説明を表示しています。

serejaris/personal-corp-os2292026年10月8日 更新

benchmark

無料

Use when choosing between engines or models for an agent pipeline and the answer must come from measurement on your own data, not from marketing pages: speech recognition for meeting recordings, the model that turns a transcript into notes, the critic model that checks it. Runs every variant in an isolated container, measures time, cost per hour of input (USD and RUB, with price source and date) and quality (WER/CER and course terms for ASR; code checks plus a judge of a different model for LLM steps), writes results.json/csv and one static analytics page. Triggers on "бенчмарк", "сравни движки", "сколько стоит час записи", "какую модель взять для пайплайна", "benchmark the pipeline", "compare ASR engines".

日本語の概要は準備中です。原文の説明を表示しています。

serejaris/personal-corp-os2292026年10月8日 更新

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", "что делал"

日本語の概要は準備中です。原文の説明を表示しています。

serejaris/personal-corp-os2292026年10月8日 更新

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

日本語の概要は準備中です。原文の説明を表示しています。

serejaris/personal-corp-os2292026年10月8日 更新

serejaris のスキルをすべて見る

このスキルの問題を報告する