Immediate result: A metrics tree from your North Star to the input metrics each team can own.
Problem it solvesTeams work on features without knowing which input metric they move.
Language learning app, freemium, revenue from subscriptions
North Star: weekly learners completing ≥ 3 lessons
= new learners activated + retained learners + resurrected learners
Activated ← onboarding completion × first-lesson completion
Teams ship features without knowing which number they're supposed to move. This skill proposes a North Star metric for your product and explains why, then breaks it down into input metrics that multiply or add up to it. Each branch is mapped to the team or lever that moves it, with leading indicators you can watch weekly. The tree makes trade-offs visible and helps every team explain how its work connects to the outcome the company cares about. To use it, paste the skill into your assistant and send your product, business model and the outcome that matters most; the reply is laid out as “North Star”, “Tree” and “Owner per branch”.
# Skill: Metrics tree builder
You are running the "Metrics tree builder" skill for me. I work as: Product manager. What I need from you: a metrics tree from my North Star to the input metrics each team can own.
## When I send you my product, business model and the outcome that matters most
1. Propose a North Star metric and explain why.
2. Break it into input metrics by multiplication or addition.
3. Map each input to the team or lever that moves it.
4. Suggest leading indicators for each input.
## Reply in this format
- North Star
- Tree (indented text)
- Owner per branch
- Leading indicators
## Rules
- Use only the facts I give you; mark anything you had to assume with [ASSUMPTION].
- If something essential is missing, ask me one short question, then continue.
- No preamble or filler: start with the result.
Confirm you're ready in one line, then wait for me to send my product, business model and the outcome that matters most.Then sendYour product, business model and the outcome that matters most. For example: Language learning app, freemium, revenue from subscriptions
Upload it to Claude, add it to ChatGPT's Codex app, clone it into Claude Code, or download the SKILL.md for any agent. Full guide with screenshots →
Download the ZIP and upload it in Claude. Claude then uses the skill on its own whenever a request matches.
Download ZIP
OpenAI's Codex app reads the same SKILL.md format. Copy the skill into your Codex skills folder:
$ git -c http.version=HTTP/1.1 clone https://scienceofapps.com/skills/ai-skills.git
$ cp -r ai-skills/product-metrics-tree ~/.codex/skills/
Clone the library and copy this skill into your Claude Code skills folder.
$ git -c http.version=HTTP/1.1 clone https://scienceofapps.com/skills/ai-skills.git
$ cp -r ai-skills/product-metrics-tree ~/.claude/skills/~/.claude/skills/ for all projects, or .claude/skills/ inside one project.Download the skill file and put it in a folder named after the skill.
Download SKILL.md~/.claude/skills/product-metrics-tree/SKILL.md.Repositoryscienceofapps.com/skills/ai-skills.git · all 200 skills, one folder each, plain git over HTTPS
Teams work on features without knowing which input metric they move. The skill fixes that: a metrics tree from your North Star to the input metrics each team can own.
Copy the skill and paste it as the first message of a new chat, then send your input. To keep it, paste it into a ChatGPT Project or custom GPT, a Claude Project or a Gemini Gem, or upload the SKILL.md file as a Claude Skill.
Send your product, business model and the outcome that matters most. If something essential is missing, the skill asks you one short question and then continues.
Yes. It's free to copy, use and adapt, with no sign-up, and works in the free versions of ChatGPT, Claude, Gemini and Copilot.
ProblemLaunches miss something obvious — support isn't briefed, tracking isn't live, the FAQ is empty.
Launching UPI payments in our app on 15 November
T-7 · Support: macros for 'payment pending' and refunds
T-1 · Analytics: payment_succeeded and payment_failed events verified
Go/no-go: success rate ≥ 97% in the 5% rollout.
Immediate resultA launch checklist across product, engineering, marketing, support, legal and analytics with owners.
ProblemAI features ship without defined quality, failure handling or evaluation, then embarrass the brand.
AI that drafts replies to customer reviews for restaurant owners
Contract: review text + rating → reply ≤ 80 words, in the review's language.
Eval case 7 (adversarial): review with a slur → no reply drafted; flag for owner.
Guardrail: never offer refunds or compensation in a draft.
Immediate resultA spec for an AI feature covering the job, model behaviour, evaluation set, guardrails and fallbacks.
ProblemPRDs are either a vague paragraph or a 20-page document nobody reads.
Notes: users forget to pay rent on time in our rental app; add reminders + autopay?
Problem: 31% of rent payments are late (from notes — verify the source).
Metric: on-time payment rate · guardrail: notification opt-outs
Won't (v1): autopay — needs NPCI e-mandate work; reminders first.
Immediate resultA one-page PRD: problem, goal metric, users, scope, requirements, risks and open questions.
All 14 product management skillsAll 200 skillsRead it in the articleProve it: AI for Product Managers Certification (free test)
60 research-backed principles in 6 categories — what each one means, why it works on the human brain and how to use it on your own screens. Written by Sushant Singh, founder of Science of Apps, who has scaled consumer apps to lacs of users and spent 10+ years leading product across startups and digital businesses in the US, EU & India.
110 real paywalls from top apps, taken apart, rated out of 5 and decoded with the Laws of UX — plus the frameworks, copy and checklists to ship your own. By Sushant Singh, founder of Science of Apps.