본문으로 건너뛰기
cccskills
무료GitHub에 공개

competitor-teardown

Produce a structured competitive analysis for any product or market. Use when asked for a competitor analysis, competitive teardown, market comparison, SWOT, or positioning map. Generates a structured teardown with positioning map, feature comparison, messaging gaps, and strategic recommendations. For a full landscape doc with feature matrix and win/loss analysis use competitive-analysis instead.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

설치 방법 보기

포함된 파일(4)

  • SKILL.md5.9 KB
  • references/intel-sourcing-guide.md3.2 KB
  • references/worked-example.md13.4 KB
  • templates/teardown-skeleton.md2.0 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

Competitor Teardown Skill

This skill produces a complete competitive analysis document — structured for use in strategy decks, investor materials, sales enablement, or product planning sessions.

Required Inputs

Work from what is given. If any of these is missing, still produce the complete output: fill each gap with a reasonable assumption marked (assumed, confirm) and list those assumptions at the end. Ask a question first only when the core subject itself is missing (there is nothing to write about).

  • Your product (name + one-line description)
  • Competitors to analyse (list 2–5 names; if not provided, ask)
  • Analysis depth (quick overview / detailed teardown)
  • Primary use case for this analysis (e.g. sales enablement, investor deck, internal strategy, product planning)

Deeper Materials

  • references/intel-sourcing-guide.md — where competitive facts come from (four source tiers), which source to use per teardown section, the [verified]/[reported]/[assumed] confidence labels, and the ethics line. Apply its labelling to every substantive claim in the output.
  • templates/teardown-skeleton.md — a fill-in teardown with the confidence labels and a verification queue built in. Offer it when the user wants to gather the intel themselves.

Output Structure

1. Competitive Landscape Overview

One paragraph summarising the market dynamic: who the key players are, how the market is segmented, and where the white space sits. Keep this under 150 words — it's the exec summary.

2. Positioning Map

Describe a 2x2 positioning map in text form (since you can't render images):

  • Define the two axes relevant to this market (e.g. "Ease of Use vs. Depth of Features" or "Price vs. Enterprise Readiness")
  • Place each competitor in one quadrant with a one-sentence rationale
  • Place the user's product and highlight the strategic implication

3. Feature Comparison Table

Feature / Capability[Your Product][Competitor A][Competitor B][Competitor C]
[Feature]✅ / ❌ / 🟡 Partial

Use ✅ (has it), ❌ (doesn't have it), 🟡 (partial/limited). Add a "Strategic Notes" column for features where the difference is a significant selling point or risk.

Include 10–15 rows. If user hasn't provided feature details, note which cells need to be verified.

4. Messaging Analysis

For each competitor, analyse their public-facing messaging (website headline, tagline, primary value prop):

[Competitor Name]

  • Their primary claim: [what they say they do]
  • Target audience signal: [who they seem to be targeting based on language/imagery]
  • Emotional hook: [fear / aspiration / authority / speed / simplicity]
  • Gap or weakness in their messaging: [what they don't address that your product could own]

5. SWOT Summary

Produce a clean SWOT for the user's product in the context of this competitive landscape:

  • Strengths: [2–3 genuine differentiators]
  • Weaknesses: [2–3 honest gaps or vulnerabilities]
  • Opportunities: [2–3 market gaps or competitor weaknesses to exploit]
  • Threats: [2–3 competitor moves or market shifts to watch]

6. Strategic Recommendations

3–5 actionable recommendations based on the analysis. Frame each as: "Given [observation], [your product] should [action] to [outcome]."

Scoring Rubric (0–40)

Score any output of this skill before handing it over; 32+ is ship-quality.

Dimension0510
Map meaningfulnessAxes are generic (price × quality)Market-specific axes but positions unjustifiedAxes capture the real buying tension in this market and every placement is defensible
Comparative depthFeature table is checkmarksFeatures compared with some notesDifferentiators carry strategic notes explaining why the gap matters and to whom
SWOT honestyWeaknesses/threats softened to nicetiesHonest but unprioritizedWeaknesses and threats stated plainly, ranked by how much they should worry you
Recommendation specificityGeneric strategy adviceActionable but unlinked to findingsEach recommendation follows "given [observation], do [action] to [outcome]" and traces to the analysis

Quality Checks

  • Axes on positioning map are meaningful and specific to this market
  • Feature table includes strategic notes on key differentiators
  • Messaging analysis covers all named competitors
  • SWOT is honest — Weaknesses and Threats should not be softened
  • Recommendations are specific and actionable, not generic strategy advice

Anti-Patterns

  • Do not mark feature presence as equivalent across competitors without noting quality differences — both products may have "reporting" while one's is meaningfully better
  • Do not position the user's product in the most favourable quadrant without justification — a self-serving positioning map that ignores real competitive pressure provides no strategic value
  • Do not soften Weaknesses or Threats in the SWOT — a SWOT that only celebrates strengths is a marketing document, not a strategy tool
  • Do not include unverifiable claims about competitor capabilities without flagging them as assumptions — presenting rumours as facts damages analytical credibility

Example Trigger Phrases

  • "Do a competitor analysis of [Product] vs [Competitor A] and [Competitor B]"
  • "Tear down [Competitor]'s positioning"
  • "Give me a competitive landscape for [market]"
  • "Build a SWOT for our product against [competitor]"

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

Design a 360-degree feedback survey or write a structured 360 feedback report. Use when asked to build a 360 feedback process, write 360 feedback for a colleague, design a feedback survey, or produce a feedback report. Produces either a complete survey instrument with rating scales and open-ended questions, or a structured narrative feedback report with themes, strengths, and development areas.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

mohitagw15856/pm-claude-skills1.5천2026년 10월 17일 업데이트

Decode a 401k or workplace retirement plan — the real cost of its funds, the match's fine print, vesting math, and the plan features worth using or avoiding. Use when someone asks 'is my 401k any good', 'decode my 401k plan', 'which funds should I look at', or 'what fees am I paying'. Produces a fee decode in dollars-over-time, match and vesting math, a fund-lineup triage by cost, and the questions for HR or the plan administrator.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

mohitagw15856/pm-claude-skills1.5천2026년 10월 17일 업데이트

Design statistically rigorous A/B tests for product features, UI changes, onboarding flows, and pricing experiments. Use when asked to set up an experiment, design an A/B test, calculate sample size, or interpret test results. Produces a complete test plan with hypothesis, variant definitions, sample size, duration estimate, guardrail metrics, and a results interpretation guide.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

mohitagw15856/pm-claude-skills1.5천2026년 10월 17일 업데이트

Analyse a finished A/B test and write the readout — the result, whether it's statistically and practically significant, what it means, and the ship/no-ship call. Use when asked to analyse experiment results, write an A/B test readout, interpret test data, or decide whether to ship a variant. Produces a clear verdict with the lift and confidence, segment cuts, the risks (peeking, novelty, sample), and a recommendation. Distinct from planning a test — this reads results.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

mohitagw15856/pm-claude-skills1.5천2026년 10월 17일 업데이트

Build or tailor an academic CV for faculty, postdoc, research or fellowship applications: publications, grants, teaching, supervision and service in the order the field expects, with consistent citations. Use when asked to write my academic CV, update my CV for a lectureship, tenure-track or postdoc application, format my publications list, or adapt my academic CV for an industry research role. Produces the full academic CV, a field-appropriate section order, a clean publications list in one citation style, and a two-page summary version when asked.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

mohitagw15856/pm-claude-skills1.5천2026년 10월 17일 업데이트

Generate a WCAG 2.2 accessibility audit checklist and remediation suggestions for any UI or design. Use when asked to audit for accessibility, check WCAG compliance, review a design for a11y issues, or create an accessibility remediation plan. Produces a prioritised checklist with pass/fail assessments and specific fixes.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

mohitagw15856/pm-claude-skills1.5천2026년 10월 17일 업데이트

mohitagw15856의 스킬 모두 보기

이 스킬의 문제 신고