Back to search
product-teardown-skill
SkillGitHub
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.
Safety scan
A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.
Checked today
Badge for your README
Markdown
[](/listings/yanliudesign--product-teardown-skill)HTML
<a href="/listings/yanliudesign--product-teardown-skill"><img src="/api/listings/yanliudesign--product-teardown-skill/badge.svg" alt="findsafeskills safety rating" /></a>Install
i
What was scanned
The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.
README.md · README · 127 lines
View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)
- <div align="center">
- [Chinese](./README_zh.md) · **English**
- # 🔬 Product Teardown Skill
- ---
- **Reverse-engineer any product as a system — and get a bilingual, print-ready HTML report. In one shot.**
- [](./LICENSE)
- []()
- [](https://github.com/yanliudesign/product-teardown-skill/stargazers)
- [](https://claude.ai/code)
- []()
- []()
- []()
- []()
- </div>
- 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.
- <p align="center">
- <img src="docs/screenshots/01-cover.png" alt="Cover — Linear · category, users, model, stage + 11-section table of contents" width="820" />
- </p>
- | TL;DR + key metrics | Users & JTBD | Core Product Loop |
- |:---:|:---:|:---:|
- | <img src="docs/screenshots/02-tldr.png" alt="If you only read three things + Time-to-value, Core loop frequency, Moat score" /> | <img src="docs/screenshots/03-users-jtbd.png" alt="Target users, trigger & context, functional/emotional/social JTBD" /> | <img src="docs/screenshots/04-core-loop.png" alt="Trigger → Action → Reward → Return loop + acquisition, retention, virality" /> |
- | **Competitor Landscape** | **AI / Future Readiness** | **Metrics · North Star + Guardrails** |
- | <img src="docs/screenshots/05-competitors.png" alt="Linear vs Jira / Notion / Asana / Height across philosophy, speed, non-eng fit, AI depth" /> | <img src="docs/screenshots/06-ai-readiness.png" alt="Assistive / Embedded / Autonomous spectrum + current usage + strategic AI risk" /> | <img src="docs/screenshots/07-metrics.png" alt="Weekly Active Teams (north star) + input metrics + guardrails + blindspots" /> |
- ---
- ## Five design principles
- 1. **Structure over opinion.** Every section answers a specific question. No "here's what I think about this app."
- 2. **Loops, not features.** The Core Loop section is the spine of the teardown — features are downstream of the loop.
- 3. **AI placement is a spectrum, not a badge.** Assistive / Embedded / Autonomous — pick one and defend it with evidence.
- 4. **Screenshots must come from the product itself.** Pull from `og:image` marketing assets (`curl -s <url> | grep og:image`), not random blog posts.
- 5. **Bilingual by default.** Every teardown ships EN + ZH in the same run, cross-linked. Not translated later.
- ---
- ## Repo contents
- ```
- product-teardown-skill/
- ├── product-teardown-prompt.md # Portable skill prompt (paste into any tool)
- ├── templates/
- │ ├── product-teardown-template-en.html # English report template
- │ └── product-teardown-template-zh.html # Chinese report template (same placeholders)
- └── scripts/
- ├── fill_linear.py # Reference implementation — renders both templates
- └── translate_template_zh.py # One-shot: derives the ZH template from EN
- ```
- - **Aesthetic:** cream paper + serif display + yellow accent. Print-optimized.
- - **Placeholders:** `{{ALL_CAPS_KEYS}}`. Fill via `str.replace` with keys sorted longest-first so prefixes don't collide.
- - **AI meter:** put `active` on exactly one of `{{ACTIVE_IF_ASSISTIVE}}` / `{{ACTIVE_IF_EMBEDDED}}` / `{{ACTIVE_IF_AUTONOMOUS}}`; empty on the other two.
- - **Language switcher:** `{{LANG_EN_HREF}}` / `{{LANG_ZH_HREF}}` = target filenames; `{{ACTIVE_IF_EN}}` / `{{ACTIVE_IF_ZH}}` = `active` on the file's own language.
- - **Brand footer:** contains `TEARDOWN.` mark + LinkedIn / X / Xiaohongshu links. Do not remove.
- ---
- ## Use as a VS Code slash command
- Copy [product-teardown-prompt.md](product-teardown-prompt.md) into your VS Code prompts folder as `product-teardown.prompt.md` and invoke via `/product-teardown <product name>`.
- macOS: `~/Library/Application Support/Code/User/prompts/`
- ---
- ## How it thinks
- - **A product is a system, not a screen.** The screen is what you see; the *loop* is what makes it work. The teardown always finds the loop first, then works outward to surfaces, business model, and moat.
- - **JTBD beats persona.** "Who uses it" is less useful than "what did they hire it to *replace*." The interesting answer is almost never the obvious one.
- - **AI readiness is a placement problem, not a checkbox.** Every AI feature sits somewhere on Assistive → Embedded → Autonomous. Naming the point is the analysis.
- - **Opportunities must be actionable.** No "they should add AI." Every opportunity in §10 is a concrete wedge you could ship next quarter.
- ---
- ## License
- MIT — fork it, remix it, ship your own version.
- Created by [Dreameryanyan](https://www.linkedin.com/in/yanliudesign/) · [LinkedIn](https://www.linkedin.com/in/yanliudesign/) · [X](https://x.com/yanliudreamer) · [Xiaohongshu](https://www.xiaohongshu.com/user/profile/5b2afdf311be104ac3c22931)
Ratings and comments
Sign in to rate this skill.
Sign inFree to use. If it’s helped, pass it on.