product-economics SKILL.md skillA
product-economics from avelikiy/great_cto is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add avelikiy/great_cto/product-economics@git:20260904.214434dPins git:20260904.214434d in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- avelikiy/great_cto
- Path
skills/product-economics/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260904.214434d, committed Sep 4, 2026
- Size
- 6,439 bytes
- Repository stars
- 112
- License
- MIT
Does this product make money at a price someone will pay? Forces contribution margin, a price with a stated basis, and a bottom-up market size — each number labelled measured / assumed / unknown, so a guess can never be read as a calculation.
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
# Product economics A product can pass every gate this pipeline has — architecture reviewed, tests green, security signed off, deployed — and still lose money on every user. The pipeline is silent about that, and silence reads as approval. This is the missing question, and it is three questions: 1. **Does a unit pay for itself?** (contribution margin) 2. **What is the price, and on what basis?** (pricing) 3. **Are there enough units to matter?** (market size, bottom-up) ## The rule that makes this worth doing **Every number carries its provenance**, in the notation the brief already uses — do not invent a second vocabulary for this: - `[source: <where it was read>]` — an invoice, a usage log, a competitor's published price with the date you checked it - `[assumption]` — you made it up, and saying so is the point `artifact-lint` already rejects a figure carrying neither. That rule was written for the Problem section; it binds here at least as hard, because arithmetic launders provenance: an `[assumption]` conversion rate and a `[source:]` one are indistinguishable once they have been multiplied together, and the product of …
Read the whole file at its exact version.
How to install
mdr add avelikiy/great_cto/product-economics@sha256:96104c53b9f380faThe line at the top of this page pins the label git:20260904.214434d, 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.
[](https://markdownregistry.com/a/art_wrbrcvzqo73qkdpn)
5 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Sep 4, 2026.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (6439 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
avelikiy/great_cto · 112 stars · license MIT · pushed 2026-11-06 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_wrbrcvzqo73qkdpn GET https://markdownregistry.com/api/v1/resolve?ref=avelikiy/great_cto/product-economics GET https://markdownregistry.com/api/v1/blob/96104c53b9f380fa0185aa688db8d7492848fc494268e6d08ae8179e54a14841
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.