New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Product Economics

by avelikiy in avelikiy/great_cto

Does this product make money at a price someone will pay?. An agent skill from avelikiy/great_cto.

MITAuto-check passed

Install Product Economics

skills CLI
$ npx skills add avelikiy/great_cto --skill product-economics -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install avelikiy/great_cto product-economics --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/avelikiy/great_cto.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/product-economics .claude/skills/product-economics && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
product-economics
GitHub stars
102
Token cost
~1.6k tokens
SKILL.md length
723 words
Files
1
Skills in repo
27
Repo updated
First seen
Licence
MIT

At a glance

Does this product make money at a price someone will pay?. An agent skill from avelikiy/great_cto.

  • Works in 3 steps: Contribution margin — per unit, per month → Price, and the basis for it → Market size — bottom-up only
  • SKILL.md covers The rule that makes this worth…, 1. Contribution margin — per…, 2. Price, and the basis for it and 3. Market size — bottom-up only, plus 2 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Product Economics is an agent skill from avelikiy/great_cto. 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.

Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The repository describes itself as: You already have the agent. This is everything around it. greatcto runs Claude Code as a pipeline of 70 specialist agents — an independent model checks each stage before the next… The licence is MIT.

Example prompts

  • “/product-economics”

Requirements

  • Pre-approved tools (allowed-tools): Read, Write, WebSearch, WebFetch

Workflow steps

3 steps, taken from the step headings in SKILL.md.

  1. Contribution margin — per unit, per month
  2. Price, and the basis for it
  3. Market size — bottom-up only

What it can do on your machine

Read from SKILL.md and the folder at commit 97dd037. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Write
    • WebSearch
    • WebFetch

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Product Economics loads about 1.6k tokens when it runs. Until then it costs about 65 tokens; SKILL.md has 723 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~65
When it runs · the whole SKILL.md, loaded when a task matches
~1.6k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from avelikiy/great_cto at commit 97dd037, republished under its MIT licence (© avelikiy). 723 words, ~1,598 tokens.

Download SKILL.mdSave it as .claude/skills/product-economics/SKILL.md (or your agent's skills folder).
name
product-economics
description
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.
allowed-tools
Read, Write, WebSearch, WebFetch
when_to_use
Apply BEFORE gate:product, while the brief is being written: - product-owner, in Step 4 — the Economics section of BRIEF-*.md - architect, when a design…
effort
medium
paths
docs/product/**, docs/architecture/**

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 two guesses is presented with the same confidence as a measurement.

The third state is the one the notation has no symbol for: a number nobody knows. Do not fill that hole with a plausible figure — a plausible figure becomes [assumption], gets multiplied, and disappears into a margin. Write the line as an open question instead, and carry it into Risks & kill-criteria with the threshold that would end the project. An unknown that decides the answer is a finding, not a gap.

1. Contribution margin — per unit, per month

price per unit                              $
  − variable cost per unit                  $
      LLM tokens (in + out, at list price)  $   ← usually the largest, often forgotten
      inference / GPU seconds               $
      storage + egress attributable to one unit
      per-unit third-party fees (payments %, SMS, maps, email)
      support minutes × loaded hourly cost
= contribution margin                       $     ← this must be POSITIVE

Fixed costs (your time, base infra, domain) do not belong here. They decide when the product breaks even, not whether a unit is viable. A negative contribution margin cannot be fixed by volume — more users lose more money.

For AI products the LLM line is the whole question. A heavy user on a frontier model at an unmetered flat price is the classic way to build something excellent and unsellable. Compute it at list price for the model actually configured, at the 95th percentile of expected usage, not the mean: flat-rate plans are priced by the tail, and the tail is what arrives.

cost-model covers infrastructure and LLM cost for the BUILD. This covers the cost of one user, for the LIFE of the product. Use its numbers here rather than re-deriving them.

Show full SKILL.md (321 more words)Show less

2. Price, and the basis for it

State which of the three the price rests on. Not all three — the one that actually decided it:

  • Cost-plus — margin over unit cost. Honest, and a floor; it never tells you what someone will pay.
  • Competitor-anchored — priced against a named incumbent, with the delta justified. Name the incumbent and the price you checked, with a date.
  • Value-based — a stated fraction of the money or hours the buyer saves. Requires a number for what they save, which is usually assumed; say so.

Then the sanity check that catches most of it: what does the buyer pay today for this problem? Zero is a valid answer and a hard one — it means the budget does not exist yet and must be created, which is a different product.

3. Market size — bottom-up only

Top-down TAM ("the CRM market is $90B, 0.1% is $90M") is not evidence. It is arithmetic performed on someone else's report.

Bottom-up:

number of buyers you can NAME or enumerate
  × realistic annual price
  × a reachable fraction, with the channel that reaches them
= revenue you could plausibly get

If the channel cannot be named, the fraction is unknown, not optimistic.

For a solo operator the honest threshold is rarely "is the market big" — it is "are there 100 buyers I can reach without a sales team". Ask that one.

What this produces

A section in BRIEF-*.md, before the recommendation:

markdown
## Economics

| | value | basis |
|---|---|---|
| Price / unit / month | $X | competitor-anchored `[source: <name> pricing page, <date>]` |
| Variable cost / unit | $Z | `[source: LLM list price, <model>, p95 usage]` |
| Contribution margin | $X−Z | derived |
| What buyers pay today | $W | `[source: …]` or `[assumption]` |
| Reachable buyers (bottom-up) | N | via <named channel> `[assumption]` |

**Kill criterion:** <the number that, if it turns out worse than T, ends this>
**Cheapest way to find out:** <the test that resolves the largest `unknown`>

Every unknown in that table is carried into Risks & kill-criteria with a threshold, so the brief cannot record an unresolved economic question as a resolved one.

What this is NOT

  • Not a forecast. No three-year revenue curve. A curve built on assumed inputs is a decorated guess, and its shape persuades where its inputs cannot.
  • Not a reason to refuse to build. Plenty of things are worth building at a loss — a portfolio piece, a wedge, something you want to exist. The rule is that the loss is stated and chosen, not discovered in month four.
  • Not investment advice, and not a substitute for the operator's own judgement about their market.

© avelikiy, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/product-economics of avelikiy/great_cto.

Open the folder on GitHubat commit 97dd037

Compare with similar skills

Product Economics next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Product Economics compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Product Economics this skillavelikiy/great_cto102—~1.6kAutomated safety check: PassMIT
Pricingsickn33/agentic-awesome-skills47k1 repos~1.9kAutomated safety check: PassMIT
Pricing Strategyphuryn/pm-skills27k—~913Automated safety check: PassMIT
Pricing Strategyalirezarezvani/claude-skills28k1 repos~3.5kAutomated safety check: PassMIT
Pricing Strategistalirezarezvani/claude-skills28k—~2.3kAutomated safety check: PassMIT
SaaS Pricing Strategistsickn33/agentic-awesome-skills47k1 repos~1.5kAutomated safety check: PassMIT

Similar skills

  • Pricing

    sickn33/agentic-awesome-skills

    When the user wants help with pricing decisions, packaging, or monetization strategy.

    47k GitHub starsUsed in 1 repo~1.9k tokens
    Sales & SupportAuto-check passed

  • Pricing Strategy

    phuryn/pm-skills

    Analyze and design pricing strategies including pricing models, competitive pricing analysis, willingness-to-pay estimation, and price elasticity.

    27k GitHub stars~913 tokensUpdated yesterday
    Sales & SupportAuto-check passed

  • Pricing Strategy

    alirezarezvani/claude-skills

    Design, optimize, and communicate SaaS pricing — tier structure, value metrics, pricing pages, and price increase strategy.

    28k GitHub starsUsed in 1 repo~3.5k tokens
    Sales & SupportAuto-check passed

  • Pricing Strategist

    alirezarezvani/claude-skills

    A skill your agent uses when designing or revisiting product pricing — selecting a pricing model (subscription seat-based, usage-based, value-based, freemium, or hybrid), running Van Westendorp…

    28k GitHub stars~2.3k tokensUpdated 1 mo ago
    Sales & SupportAuto-check passed

  • SaaS Pricing Strategist

    sickn33/agentic-awesome-skills

    Design, optimize, and test pricing strategies for SaaS products using data-driven frameworks, competitive analysis, and psychological pricing principles.

    47k GitHub starsUsed in 1 repo~1.5k tokens
    Marketing & SEOAuto-check passed

  • Add Model Price

    langfuse/langfuse

    A skill your agent uses when editing worker/src/constants/default-model-prices.json, packages/shared/src/server/llm/types.ts, pricing tiers, tokenizer IDs, or matchPattern regexes for OpenAI…

    36k GitHub stars~1.2k tokensUpdated today
    AI & LLM EngineeringAuto-check passed

More from avelikiy/great_cto

All 27 skills in this repo

  • AnyDesign Design Analyzer

    avelikiy/great_cto

    Analyzes a screenshot, website or Figma file and writes a `design.md` with its token system, component inventory and reconstruction notes, or an `element.md` for one element.

    103 GitHub starsUsed in 1 repo~3.2k tokens
    Auto-check passed

  • Opportunity Solution Tree

    avelikiy/great_cto

    Builds an Opportunity Solution Tree that links one measurable outcome to customer opportunities, candidate solutions and experiments.

    103 GitHub stars~1.8k tokensUpdated today
    Auto-check passed

  • Outcome-Focused Roadmap Rewriter

    avelikiy/great_cto

    Rewrites a feature-list roadmap into outcome statements that name the customer segment, the result they get and the business impact, grouped into themes.

    103 GitHub stars~1.3k tokensUpdated today
    Auto-check passed

  • Exposed Secret Rotation

    avelikiy/great_cto

    Turns a leaked key, token or password into one tracked rotation task the moment it's spotted, instead of a reminder repeated every session.

    103 GitHub stars~884 tokensUpdated today
    Auto-check: notes

  • Skeptical Triage

    avelikiy/great_cto

    Runs a three-round self-challenge plus an arbiter over high-stakes findings, so false positives from reviews, audits and flaky-test verdicts do not become blockers.

    103 GitHub stars~2.1k tokensUpdated today
    Auto-check: notes

  • Aesthetic Instrument

    avelikiy/great_cto

    greatcto's own committed aesthetic — the instrument panel. An agent skill from avelikiy/great_cto.

    103 GitHub stars~1.9k tokensUpdated today
    Auto-check passed

Questions about Product Economics

What does Product Economics do?

Does this product make money at a price someone will pay?. An agent skill from avelikiy/great_cto. Product Economics is an agent skill from avelikiy/great_cto. Does this product make money at a price someone will pay?

How do I install Product Economics in Claude Code?

Run `npx skills add avelikiy/great_cto --skill product-economics -a claude-code`. Or copy the skill folder (skills/product-economics in avelikiy/great_cto) into .claude/skills/product-economics in your project. Claude Code loads it when a task matches its description.

How do I install Product Economics in Codex?

Run `npx skills add avelikiy/great_cto --skill product-economics -a codex`. Or copy the skill folder (skills/product-economics in avelikiy/great_cto) into .agents/skills/product-economics in your project. Codex loads it when a task matches its description.

Can I use Product Economics in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add avelikiy/great_cto --skill product-economics -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/product-economics, .gemini/skills/product-economics, .github/skills/product-economics and .opencode/skills/product-economics in your project.

What does Product Economics need to run?

SKILL.md names no scripts, command-line tools or credentials: Product Economics is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Write, WebSearch, WebFetch.

Does Product Economics access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Product Economics safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Product Economics use?

Product Economics is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Product Economics use?

About 1.6k tokens (SKILL.md is roughly 6.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Product Economics?

Skills that share tags, products or a category with Product Economics: Pricing (sickn33/agentic-awesome-skills, 47k stars), Pricing Strategy (phuryn/pm-skills, 27k stars), Pricing Strategy (alirezarezvani/claude-skills, 28k stars) and Pricing Strategist (alirezarezvani/claude-skills, 28k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Product Economics?

avelikiy (a GitHub user) maintains it in avelikiy/great_cto, which has 102 GitHub stars. The repository holds 27 skills in this directory. The repository was last updated on October 9, 2026.

Source: avelikiy/great_cto on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.