メニュー
Perform competitive market analysis with feature comparisons, positioning, and strategic recommendations.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Design static ad creatives for social media and display advertising campaigns.
Source and evaluate candidates with job analysis, search strategies, specific candidate profiles, and outreach templates.
Draft emails, manage calendar scheduling, prepare meeting agendas, and organize productivity
Create brand identity kits with color palettes, typography, logo concepts, and brand guidelines.
Create social media posts, newsletters, and marketing content calibrated to your voice and platform.
Conduct thorough, multi-source research on complex topics with structured findings and citations.
| name | competitive-analysis |
| description | Perform competitive market analysis with feature comparisons, positioning, and strategic recommendations. |
Identify competitors, analyze positioning, and deliver actionable recommendations. Skip textbook frameworks (Porter's, PESTLE) unless specifically requested — they're MBA artifacts, not operator tools.
Skip Porter's Five Forces. Operators use these four:
1. April Dunford's Positioning (from "Obviously Awesome") — the most-used positioning method in B2B SaaS. Five inputs in strict order:
2. Wardley Mapping (Simon Wardley, free book at medium.com/wardleymaps) — plot components on two axes: visibility-to-user (y) vs evolution Genesis → Custom → Product → Commodity (x). Reveals: where competitors overinvest in commoditizing components, where to build vs buy, what's about to become table stakes. Tool: onlinewardleymaps.com (free). Best for platform/infra competition.
3. Feature comparison matrix — the unglamorous workhorse. Rows = capabilities, columns = competitors, cells = ✓/✗/partial. Battlecards for sales teams are this + "trap-setting questions." Key: weight features by how often they appear in lost-deal notes, not by what engineering thinks matters.
4. Kano mapping applied to competitors — categorize each competitor feature as Basic (expected, table stakes), Performance (more = better), or Delighter (unexpected). Kano's insight: today's delighters become tomorrow's basics. Competitors' delighters tell you where the bar is moving.
| Need | Tool | How to use |
|---|---|---|
| Find competitors | webSearch("[product] alternatives site:g2.com") | G2's "alternatives" pages are crowdsourced competitor lists |
| Verified user complaints | webSearch("[competitor] site:g2.com"), Capterra, TrustRadius | Filter reviews to 1-3 stars. Look for repeated phrases — those are exploitable weaknesses |
| Enterprise IT buyers | PeerSpot (formerly IT Central Station) | More technical, less marketing-gamed than G2 |
| Pricing (often hidden) | webFetch competitor /pricing page, Wayback Machine for historical, webSearch("[competitor] pricing reddit") for leaked enterprise quotes | |
| Tech stack | webFetch("https://builtwith.com/[domain]") — 673M+ sites, 85k+ technologies. Wappalyzer similar. | Reveals: are they on legacy stack? What vendors? Switching cost signals |
| Traffic/channel mix | SimilarWeb (reliable for large sites, unreliable <50k visits/mo) | See which channels drive competitor traffic |
| Funding/team size | Crunchbase free tier, webSearch("[competitor] raises TechCrunch") | |
| Strategic direction | webSearch("[competitor] site:linkedin.com/jobs") — hiring = roadmap. 5 ML engineers = AI features in 6mo. | |
| Historical messaging | webFetch("https://web.archive.org/web/2024*/[competitor].com") | Shows positioning pivots — what they tried and abandoned |
| SEO/content strategy | Ahrefs (paid, $129+/mo) or webSearch("site:[competitor].com") to map content |
Step 1: Frame — Get from user: their product, target customer, and who THEY think competes. Their list is always incomplete.
Step 2: Expand the competitor set — Run webSearch("[known competitor] alternatives") and webSearch("[category] vs"). Check G2 category pages. Add indirect competitors (different product, same job) and the "do nothing" option.
Step 3: Per-competitor dossier — For each (limit to 5-7 for depth):
Step 4: Synthesize — Build the feature matrix. Plot on a 2×2 (pick the two axes the buyer cares about, not the ones that make user look good). Identify white space.
Step 5: Recommend — Not "monitor the threat." Specific: "Competitor X's reviews mention slow support 23 times — lead with your SLA in sales calls."
Before building any deliverable, ask the user how they want the analysis presented using the query tool:
"How would you like your competitive analysis presented — as a slide deck or a written report?"
Then follow the appropriate path below. Do not default to one format without asking.
Load the slides skill and build a Replit slide deck. Follow the slides skill's conventions for manifest, components, and design. Structure the deck as:
Do not output a markdown summary. Build a polished competitive analysis report as a professional PDF using jsPDF, with a React web preview that visually matches page-by-page. The report should look like a strategy consulting deliverable.
Build order: Generate the PDF first and present it to the user. Then build the web preview. The PDF is the primary deliverable — the web app is a visual complement.
Use jsPDF to generate the PDF with explicit point-based layout:
new jsPDF({ unit: "pt", format: "letter" }) — US Letter: 612×792ptPAGE_H - MARGIN, call doc.addPage() and reset Y to the top margin. Never let content silently overflow — always check before rendering.doc.addImage() — scale to fit content width while respecting remaining page height.isNewPage flag). Only add a page if you're not already on a fresh one.The React web artifact renders the same report data as an HTML version that visually mirrors the PDF page-by-page. Each "page" should be a fixed-size container (816×1056px — US Letter at 96dpi) with the same margins, typography, and chart placement as the PDF.