saas-platform-teardown SKILL.md skillA

saas-platform-teardown from ahmedyehya92/saas-platform-teardown-kit is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned
mdr add ahmedyehya92/saas-platform-teardown-kit/saas-platform-teardown@git:20260907.c64d496

Pins git:20260907.c64d496 in mdr.lock. Pin the fingerprint instead.

Audit grade
A, 17 of 17 checks passed
Kind
SKILL.md skill
Repository
ahmedyehya92/saas-platform-teardown-kit
Path
saas-platform-teardown/SKILL.md
Versions recorded
4
Latest version
git:20260907.c64d496, committed Sep 7, 2026
First version recorded
Sep 6, 2026
Size
11,292 bytes
Repository stars
20
License
MIT

This skill should be used when the user gives a SaaS product's landing page URL, homepage, or name and asks for a full teardown or deep-dive of how the product works across web, desktop, and mobile — including per-platform feature inventories and user journeys, tech stack, pricing/plan mapping, how the platforms integrate and sync (and the business logic behind those choices), hardware integrations, business-scale/revenue signals, and concrete release artifacts per platform — with a structured…

Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.

What the file says

# SaaS Platform Teardown

## Role

Act as a product-research engineer producing a due-diligence-grade teardown of
a SaaS product from nothing but its landing page URL. The deliverable is
Markdown documentation good enough that someone who has never seen the
product could explain, to a stakeholder, exactly what it does, on which
platforms, how those platforms talk to each other — and whether the business
behind it is substantial — with enough method transparency that the reader
can tell verified truth from secondhand reconstruction.

## Before starting

Confirm what's available and degrade gracefully rather than stalling:

1. Check for live browser access, in this order:
   a. Playwright MCP tools (`mcp__playwright__browser_navigate`,
      `browser_snapshot`, etc.). If this session started before the server
      was registered, it won't be present — see (b).
   b. `agent-browser` CLI on `$PATH` (`agent-browser --version` via bash).
      Same audit capability, shell-driven.
   If both are absent, tell the user the web audit will be limited to static
   page fetches — no live app exploration — and continue anyway.
…

Read the whole file at its exact version.

How to install

The exact contents, by fingerprint
mdr add ahmedyehya92/saas-platform-teardown-kit/saas-platform-teardown@sha256:e70ca222310619b8

The line at the top of this page pins the label git:20260907.c64d496, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.

Badge

mdr badge

[![mdr](https://markdownregistry.com/badge/art_lqd7lygoemjaxgbv.svg)](https://markdownregistry.com/a/art_lqd7lygoemjaxgbv)

3 badge image fetches in 30 days. What the badge shows.

Versions

The registry has recorded 4 versions of this file, between Sep 6, 2026 and Sep 7, 2026, more than one a day.

versioncommittedcommitsizeaudit
git:20260907.c64d496 latest2026-09-07 c64d496 11,292 BA view · diff
git:20260907.db6cea02026-09-07 db6cea0 10,988 BA view · diff
git:20260906.3ded5d32026-09-06 3ded5d3 9,803 BA view · diff
git:20260906.620fdb82026-09-06 620fdb8 6,181 BA view

Audit of the latest version

A  17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.
  • pass: Frontmatter block present
  • pass: Frontmatter declares a name
  • pass: Frontmatter declares a description
  • pass: Size between 200 bytes and 200 KB (11292 bytes)
  • pass: No zero-width or bidi control characters
  • pass: No instruction hidden inside an HTML comment
  • pass: No link to an exfiltration or paste host
  • pass: No credential-shaped string
  • pass: No instruction to send local credentials anywhere
  • pass: No text hidden with inline styles
  • pass: No prompt-injection phrasing
  • pass: No curl or wget piped into a shell
  • pass: No recursive delete of root, home or parent
  • pass: No instruction to read or print local credentials
  • pass: No base64 blob over 200 characters
  • pass: No link to a raw IP address
  • pass: No script tag

Source

GitHub

ahmedyehya92/saas-platform-teardown-kit · 20 stars · license MIT · pushed 2026-09-07 · branch master

API

GET https://markdownregistry.com/api/v1/artifacts/art_lqd7lygoemjaxgbv
GET https://markdownregistry.com/api/v1/resolve?ref=ahmedyehya92/saas-platform-teardown-kit/saas-platform-teardown
GET https://markdownregistry.com/api/v1/blob/e70ca222310619b872389130877166d8765cfa765996cc3cd2f53d8630fb58dc

Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.

Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.

Browse by kind, by grade A, or by owner.