Skip to content

Product Teardown Skill

Principal-PM-level product-teardown skill — reverse-engineer any product as a system and render a bilingual (EN + ZH) HTML report with a product-screenshot gallery.

Install

$git clone https://github.com/yanliudesign/product-teardown-skill

Install command taken from the project's README or registry entry. Always review code before running it.

Chinese · English

🔬 Product Teardown Skill


Reverse-engineer any product as a system — and get a bilingual, print-ready HTML report. In one shot.

A Principal-PM-level product-teardown skill. Point it at any product (Linear, Notion, Cursor, Perplexity…) and it reverse-engineers the thing as a system — loops, strategy, moat, opportunities — then renders the analysis as a bilingual (EN + ZH), print-ready HTML report with an embedded product-screenshot gallery. Not a "5 things I like about this app" review. A structural read of why the product wins, where it leaks, and what the next move should be.


How it works — just 2 steps

Invoke the skill with anything like "teardown Linear" / "break down Notion" / "analyze Cursor" and it runs the same flow every time:

  1. Chat response — full teardown in 11 sections (Snapshot → Users & JTBD → Core Loop → Architecture → UX Quality → Business Model → Growth → AI Readiness → Friction → Opportunities → Final PM Verdict).
  2. HTML report auto-generates — two cross-linked files (EN + ZH, toggle in the bottom-right), saved to ~/Desktop/Claude skills/product-teardown-<slug>-{en,zh}-<yyyymm>.html. Print-optimized (Cmd+P → clean PDF).

Teardown Report · the 11-section spine

Every run ends with two single-file HTML reports at ~/Desktop/Claude skills/. Fixed 11-section spine, plus a product-tour gallery:

# Section What it answers
— Product Tour 6 screenshots pulled from the product's own og:image marketing assets.
1 Snapshot One-line pitch · category · stage · pricing · notable numbers.
2 Users & JTBD Who hires this product, and for what job — including the replaced alternative.
3 Core Loop The atomic user loop that makes the product habit-forming (or doesn't).
4 Architecture Object model · surfaces · integrations · what's a primitive vs a feature.
5 UX Quality Signature interactions, latency, information density, empty states.
6 Business Model Monetization vector · unit economics · expansion path (PLG / sales / hybrid).
7 Growth Acquisition loops · virality vector · retention hooks · notable moats.
8 AI Readiness Assistive / Embedded / Autonomous — placed on the spectrum with evidence.
9 Friction Where the product leaks — onboarding, mid-funnel, power-user ceiling.
10 Opportunities 3–5 concrete next-move bets (features, wedges, adjacencies).
11 Final PM Verdict The one sentence a Principal PM would write on the internal doc.

Reports are print-optimized (Cmd+P → clean PDF) and cross-linked EN ↔ ZH via a bottom-right language switcher.


Example output · Linear teardown

product-teardown-linear-en-202607.html + -zh- counterpart · cross-linked EN / ZH switcher · 6-image product tour · 11-section deep dive.

TL;DR + key metrics Users & JTBD Core Product Loop
Competitor Landscape AI / Future Readiness Metrics · North Star + Guardrails

Five design principles

Similar plugs

Turn any codebase, with its docs, SQL schemas, configs, and PDFs, into a queryable knowledge graph. A /graphify skill for Claude Code, Cursor, Codex, and Gemini CLI: local…

Why use many token when few token do trick. Viral skill + proxy for coding agents that cuts 65% of tokens by talking like a caveman.

The 1st Collaborative AI Design Agent Workspace. Local-first and open source. Create prototypes, websites, apps, dashboards, presentations, images, and videos with your team…

Explore related