SaaS Platform Teardown Kit

One SaaS URL in, a due-diligence-grade teardown out. A Claude Code skill.

What you get · Quick start · How it works · Kit anatomy · Examples · FAQ · Roadmap · Contributing

Give it a landing page and it produces a structured, multi-file Markdown teardown of the whole product: what it does, every feature and user journey on every platform (web / desktop / mobile), how those platforms integrate — and the business logic behind those choices — plus hardware coverage, business-scale/revenue signals, and concrete release artifacts per platform.

Every claim is sourced, dated, and confidence-tagged, so the report tells you not just what the product looks like but how much of that you should believe.

✨ What you get

Nine linked report files per teardown:

-teardown/
├── 00-INDEX.md                    # executive summary + access-methods summary
├── 01-overview-and-recon.md       # + complete verified link inventory
├── 02-web-platform.md             # + access log, journeys
├── 03-mobile-platform.md          # + store artifact tables, access log, journeys
├── 04-desktop-platform.md         # + per-OS/arch artifact table, version history
├── 05-user-journeys.md            # all platforms × 5 journeys, personas, handoff map
├── 06-hardware-integrations.md    # device families — or the explicit none-finding
├── 07-integration-architecture.md # + business-objective map
└── 08-pricing-revenue-sources.md  # + revenue estimates with method per figure

Every claim in the report carries one of three confidence tags — the reader always knows how much of it to believe:

Tag	Means	The reader's move
🟢 Confirmed	Directly observed — screenshot, DOM, API response, official doc	Trust it; check the report date
🟡 Reported	A secondary source states it — review, forum, press	Re-verify before deciding on it
🟠 Inferred	Deduced from indirect evidence — reasoning shown, not just the conclusion	Read the reasoning first

🚀 Quick start

1 · Pick your tier

Nothing is required to start. Each tier adds capability; every tier degrades gracefully when missing.

flowchart LR
    T0["🟢 Tier 0 — zero-installbuilt-in web search + fetch"] --> OUT
    T1["🔵 Tier 1 — live browserPlaywright MCP — UI claims go Confirmed"] --> OUT
    T2["🟣 Tier 2 — parallel sweepsagy + jq — research fans out"] --> OUT
    OUT(["📦 The same full teardown either way —missing tools degrade the report honestly,they never block it"])

Tier	You need	It unlocks	Without it
0 — zero-install (default)	Claude Code	Full teardown via the built-in web search/fetch tools; static web audit	— this is the floor
1 — live browser (recommended)	Playwright MCP — claude mcp add playwright -s user -- npx @playwright/mcp@latest	Live in-app exploration, authenticated-state screens, UI claims upgraded to Confirmed	Web audit limited to static fetches; UI claims stay Reported
2 — parallel research (optional)	agy CLI + jq	The 15 research sweeps fanned out as parallel headless jobs	Same sweeps run sequentially on built-in search — slower, same depth

2 · Install

Tier 0 is one step: