Game Changing Features
openstatusHQ/data-table-filters
Find 10x product opportunities and high-leverage improvements.
Strategic product leadership for scaling companies: product vision, portfolio strategy, and PMF measurement.
Install Cpo Advisor
$ npx skills add borghei/Claude-Skills --skill cpo-advisor -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install borghei/Claude-Skills cpo-advisor --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/c-level-advisor/cpo-advisor .claude/skills/cpo-advisor && rm -rf skills-srcUse ~/.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/
Install the "cpo-advisor" agent skill from https://github.com/borghei/Claude-Skills/tree/main/c-level-advisor/cpo-advisor into .claude/skills/cpo-advisor/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cpo-advisor", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/borghei/Claude-Skills/tree/main/c-level-advisor/cpo-advisorType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add borghei/Claude-Skills --skill cpo-advisor -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install borghei/Claude-Skills cpo-advisor --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/c-level-advisor/cpo-advisor .agents/skills/cpo-advisor && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "cpo-advisor" agent skill from https://github.com/borghei/Claude-Skills/tree/main/c-level-advisor/cpo-advisor into .agents/skills/cpo-advisor/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cpo-advisor", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add borghei/Claude-Skills --skill cpo-advisor -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install borghei/Claude-Skills cpo-advisor --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/c-level-advisor/cpo-advisor .cursor/skills/cpo-advisor && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "cpo-advisor" agent skill from https://github.com/borghei/Claude-Skills/tree/main/c-level-advisor/cpo-advisor into .cursor/skills/cpo-advisor/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cpo-advisor", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/borghei/Claude-Skills.git --path c-level-advisor/cpo-advisor--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add borghei/Claude-Skills --skill cpo-advisor -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install borghei/Claude-Skills cpo-advisor --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/c-level-advisor/cpo-advisor .gemini/skills/cpo-advisor && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "cpo-advisor" agent skill from https://github.com/borghei/Claude-Skills/tree/main/c-level-advisor/cpo-advisor into .gemini/skills/cpo-advisor/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cpo-advisor", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install borghei/Claude-Skills cpo-advisorInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add borghei/Claude-Skills --skill cpo-advisor -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/c-level-advisor/cpo-advisor .github/skills/cpo-advisor && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "cpo-advisor" agent skill from https://github.com/borghei/Claude-Skills/tree/main/c-level-advisor/cpo-advisor into .github/skills/cpo-advisor/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cpo-advisor", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add borghei/Claude-Skills --skill cpo-advisor -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install borghei/Claude-Skills cpo-advisor --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/c-level-advisor/cpo-advisor .opencode/skills/cpo-advisor && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "cpo-advisor" agent skill from https://github.com/borghei/Claude-Skills/tree/main/c-level-advisor/cpo-advisor into .opencode/skills/cpo-advisor/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cpo-advisor", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
cpo-advisor- GitHub stars
- 881
- Token cost
- ~4.9k tokens
- SKILL.md length
- 1,844 words
- Files
- 4 (incl. scripts)
- Skills in repo
- 349
- Repo updated
- First seen
- Licence
- MIT
At a glance
Strategic product leadership for scaling companies: product vision, portfolio strategy, and PMF measurement.
- Works in 3 steps: product_portfolio_analyzer.py → feature_prioritizer.py → product_health_scorer.py
- Setting product vision
- SKILL.md covers Keywords, The CPO Owns Three Things, Product-Market Fit Assessment and Portfolio Management, plus 10 more sections
- Runs Python scripts from its folder; calls python
What it does
Cpo Advisor is an agent skill from borghei/Claude-Skills. Strategic product leadership for scaling companies: product vision, portfolio strategy, and PMF measurement. Use when setting product vision, managing a product portfolio, measuring PMF, or designing product teams.
Its SKILL.md is about 4.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including scripts (for example `scripts/feature_prioritizer.py`, `scripts/product_health_scorer.py` and `scripts/product_portfolio_analyzer.py`).
It sits in Product & Project Management, covering Product strategy. The repository describes itself as: 385 AI skills, 77 expert agents, and 900 stdlib Python tools for every team: engineering, PM, marketing, C-level, compliance, business ops, research, and a LinkedIn toolkit… The licence is MIT.
When your agent uses it
- Setting product vision
- Managing a product portfolio
- Designing product teams
Example prompts
- “/cpo-advisor”
Requirements
- Python 3
Workflow steps
3 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 4a698e8. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 3 files in scripts/ (Python), which the agent can run.
Shell commands in SKILL.md call:
python
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
Cpo Advisor loads about 4.9k tokens when it runs. Until then it costs about 57 tokens; SKILL.md has 1,844 words of instructions outside code blocks.
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); the scripts in this folder are not scanned.
SKILL.md
The full file from borghei/Claude-Skills at commit 4a698e8, republished under its MIT licence (© borghei). 1,844 words, ~4,853 tokens.
Download SKILL.mdSave it as
.claude/skills/cpo-advisor/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.- name
- cpo-advisor
- description
- Strategic product leadership for scaling companies: product vision, portfolio strategy, and PMF measurement. Use when setting product vision, managing a product portfolio, measuring PMF, or designing product teams.
- license
- MIT + Commons Clause
- metadata.version
- 2.0.0
- metadata.author
- borghei
- metadata.category
- c-level
- metadata.domain
- cpo-leadership
- metadata.updated
- 2026-03-09
- metadata.frameworks
- pmf-playbook, product-strategy, product-org-design, portfolio-management, north-star-framework, investment-posture
- metadata.triggers
- CPO, chief product officer, product strategy, product vision, product-market fit, PMF, portfolio management, product organization, roadmap strategy, product…
CPO Advisor
Strategic product leadership. Vision, portfolio, PMF, org design, and metrics. Not for feature-level work -- for the decisions that determine what gets built, why, and by whom.
Keywords
CPO, chief product officer, product strategy, product vision, product-market fit, PMF, portfolio management, product org, roadmap strategy, product metrics, north star metric, retention curve, product trio, team topologies, jobs to be done, JTBD, category design, product positioning, board product reporting, invest-maintain-kill, BCG matrix, switching costs, network effects, product-led growth, PLG, feature adoption, time to value, activation rate
The CPO Owns Three Things
Everything else is delegation.
| Ownership | What It Means | Key Question |
|---|---|---|
| Portfolio | Which products exist, which get investment, which get killed | "If we could only fund 2 of our 4 products, which 2?" |
| Vision | Where the product goes in 3-5 years and why customers care | "What does the world look like if we succeed?" |
| Organization | The team structure that can execute the vision | "Can this org ship the next 12 months of strategy?" |
Product-Market Fit Assessment
PMF Scoring Matrix
| Dimension | Weight | Score 1-3 (Weak) | Score 4-6 (Emerging) | Score 7-10 (Strong) |
|---|---|---|---|---|
| Retention | 30% | D30 < 15% (consumer) or < 40% (B2B) | D30 15-30% / 40-60% | D30 > 30% / > 60% |
| Engagement | 25% | DAU/MAU < 15% | DAU/MAU 15-35% | DAU/MAU > 35% |
| Satisfaction | 25% | Sean Ellis < 25% "very disappointed" | 25-40% | > 40% |
| Growth | 20% | No organic growth | Some organic, mostly paid | > 50% organic |
PMF Decision Tree
START: "Do we have PMF?"
|
v
[Check retention curve shape]
|
+-- Declining to zero --> NO PMF. Stop building. Talk to users.
|
+-- Declining but flattening --> EMERGING. Find the segment where it's flat.
|
+-- Flat or smiling --> [Check Sean Ellis score]
|
+-- < 25% "very disappointed" --> Weak PMF. Product is nice, not essential.
|
+-- 25-40% --> Moderate PMF. Find and double down on power users.
|
+-- > 40% --> [Check organic growth]
|
+-- < 30% organic --> PMF exists but distribution is weak.
+-- > 30% organic --> STRONG PMF. Scale.Post-PMF Traps
| Trap | Description | Prevention |
|---|---|---|
| Feature creep | Adding features for new segments dilutes core value | Maintain a "jobs" focus, not feature focus |
| Premature scaling | Scaling sales/marketing before retention proves sustainable | Prove 3+ cohorts retain before scaling spend |
| Metric vanity | Celebrating signups while ignoring retention | North star must be a retention/engagement metric |
| Founder departure from product | CEO stops talking to customers post-PMF | Monthly customer conversations are permanent |
| Platform too early | Building platform capabilities before core is solid | Platform only after 3+ products need shared infra |
Portfolio Management
Investment Posture Framework
Every product gets exactly one posture. "Wait and see" is a decision to lose share.
| Posture | Signal | Resource Allocation | Review Cadence |
|---|---|---|---|
| Invest | High growth, strong/improving retention, clear PMF | Full team, aggressive roadmap, dedicated marketing | Monthly |
| Maintain | Stable revenue, slow growth, good margins | Bug fixes, incremental improvement, minimal new features | Quarterly |
| Harvest | Declining growth, still profitable, no recovery path | Minimal investment, maximize cash extraction | Quarterly |
| Kill | Declining, negative margins, no recovery evidence | Set sunset date, migration plan, team reallocation | Immediate |
Portfolio Health Scorecard
| Metric | Healthy | Unhealthy |
|---|---|---|
| % revenue from "Invest" products | > 60% | < 40% |
| % engineering on "Kill" candidates | < 10% | > 20% |
| Number of products without clear posture | 0 | > 1 |
| Portfolio D30 retention (weighted) | Improving QoQ | Declining QoQ |
| # of "question marks" > 2 quarters | 0 | > 2 |
Portfolio Review Process
Quarterly Portfolio Review (Half-day workshop)
Step 1: Data Preparation (pre-meeting)
- Revenue, growth rate, retention, margin per product
- Engineering investment % per product
- Customer satisfaction per product
Step 2: BCG Classification
- Plot each product on Growth Rate (Y) vs Market Share (X)
- Stars: high growth, high share --> Invest
- Cash Cows: low growth, high share --> Maintain/Harvest
- Question Marks: high growth, low share --> Invest or Kill (decide now)
- Dogs: low growth, low share --> Kill
Step 3: Investment Allocation
- Align engineering capacity to posture
- Reallocate from Kill/Harvest to Invest
- Set clear milestones for Question Marks (90-day decision point)
Step 4: Communication
- Share portfolio decisions with all product teams
- Update roadmaps to reflect postures
- Communicate sunset plans for Kill productsNorth Star Metric Framework
Selection Criteria
The north star metric must satisfy ALL of these:
| Criterion | Test |
|---|---|
| Measures customer value | Does improvement mean customers got more value? |
| Leading indicator | Does it predict future revenue? |
| Actionable | Can product teams influence it? |
| Single number | Can you state it as one metric? |
| Non-gameable | Is it hard to improve without genuinely helping customers? |
North Star by Business Model
| Model | North Star | Why It Works |
|---|---|---|
| B2B SaaS | Weekly active accounts using core feature | Combines adoption + engagement + stickiness |
| Consumer social | Daily content creators | Creators drive consumer engagement |
| Marketplace | Successful transactions per week | Both sides active = healthy marketplace |
| PLG | Accounts reaching activation within 14 days | Activation predicts retention |
| Data/Analytics | Queries per active user per week | Usage intensity = value received |
| Fintech | Monthly active transactors | Transaction activity = core value |
| E-commerce | Repeat purchase rate (90-day) | Retention is everything in commerce |
Metrics Hierarchy
North Star Metric (1, owned by CPO)
|
+-- Leading Indicator 1 (owned by PM Team A)
| e.g., Activation rate within 7 days
|
+-- Leading Indicator 2 (owned by PM Team B)
| e.g., Feature X adoption rate
|
+-- Leading Indicator 3 (owned by PM Team C)
| e.g., D7 retention rate
|
+-- Guard Rail Metrics (owned by CPO)
e.g., NPS, support ticket volume, revenue per userProduct Organization Design
Team Topology Selection
| Topology | When to Use | Optimal Size | Communication |
|---|---|---|---|
| Stream-aligned | Default. Teams own end-to-end customer journey. | 5-9 people | Low cross-team dependency |
| Platform | Shared infrastructure multiple streams need | 4-8 people | API-first, self-service |
| Enabling | Temporary teams to upskill stream teams | 2-4 people | Coaching mode, time-limited |
| Complicated subsystem | Deep specialist domain (ML, payments) | 3-6 people | Provides service to streams |
Product Team Ratios
| Company Size | PM : Engineers | PM : Designer | Total Product Team |
|---|---|---|---|
| 10-30 | 1:4-6 | 1:1 | 1 PM, 1 Designer, 4-6 Eng |
| 30-80 | 1:5-8 | 1:1-2 | 2-4 PMs, 2-3 Designers |
| 80-200 | 1:6-10 | 1:1-2 | 5-10 PMs, 4-6 Designers |
| 200+ | 1:8-12 | 1:2 | 10+ PMs, 8+ Designers |
The Product Trio
Every product team should operate as a trio: PM + Designer + Tech Lead.
| Role | Owns | Decides |
|---|---|---|
| PM | What to build and why | Prioritization, scope |
| Designer | User experience and usability | Interaction patterns, research |
| Tech Lead | How to build and technical feasibility | Architecture, implementation |
Anti-pattern: PM writes spec, hands to design, design hands to engineering. This is waterfall with agile labels.
CPO Dashboard
| Category | Metric | Frequency | Target |
|---|---|---|---|
| Growth | North star metric | Weekly | Improving MoM |
| Retention | D30 / D90 retention by cohort | Weekly | Flattening or improving |
| Acquisition | New activations | Weekly | Per plan |
| Activation | Time to first value | Weekly | Decreasing |
| Engagement | DAU/MAU ratio | Weekly | > 30% (B2B) / > 20% (consumer) |
| Satisfaction | NPS trend | Monthly | > 40 |
| Portfolio | Revenue per product | Monthly | Aligned to posture |
| Portfolio | Engineering investment % per product | Monthly | Aligned to posture |
| Quality | Support tickets per 1K users | Monthly | Decreasing |
| Moat | Feature adoption depth | Monthly | Increasing |
Red Flags
- Products stuck as "question marks" for 2+ quarters without a decision -- make the call
- Engineering allocated to highest-revenue product while highest-growth product is understaffed -- misallocation
30% of team time on products with declining revenue -- sunk cost fallacy
- Retention curve never flattens -- no PMF, stop building features and start talking to users
- PMs writing specs without talking to users -- product theater
- Platform team has 6-week queue -- platform should be self-service, not a bottleneck
- CPO has not talked to a customer in 30+ days -- disconnected from reality
- North star trending up while retention trends down -- wrong metric
- Roadmap built from sales requests instead of user data -- sales-driven product is a trap
- No user research conducted in 90+ days -- team is guessing, not learning
Integration with C-Suite
| When... | CPO Works With... | To... |
|---|---|---|
| Company direction | CEO (ceo-advisor) | Translate vision into product bets |
| Roadmap funding | CFO (cfo-advisor) | Justify investment allocation per product |
| Scaling product org | COO + CHRO | Align hiring with product growth needs |
| Technical feasibility | CTO (cto-advisor) | Co-own features vs. platform trade-off |
| Launch timing | CMO (cmo-advisor) | Align releases with demand gen capacity |
| Sales-requested features | CRO (cro-advisor) | Separate revenue-critical from noise |
| Compliance deadlines | CISO (ciso-advisor) | Identify non-negotiable security items |
| Product strategy | Product Team (product-team/) | Execute strategy through product managers |
| User research | UX Research (product-team/ux-researcher) | Validate assumptions with data |
Proactive Triggers
- Retention curve not flattening -- PMF at risk, stop feature work and investigate
- Feature requests piling up without prioritization framework -- propose RICE scoring
- No user research in 90+ days -- product team is building on assumptions
- NPS declining QoQ -- dig into detractor feedback, find the pattern
- Portfolio has a "dog" everyone avoids discussing -- force the kill/invest decision
- Engineering spending > 20% on a product with < 5% of revenue -- investment misalignment
- New competitor launched with similar positioning -- competitive response needed
Show full SKILL.md (730 more words)Show less
Output Artifacts
| Request | Deliverable |
|---|---|
| "Do we have PMF?" | PMF scorecard across 4 dimensions with cohort data |
| "Prioritize our roadmap" | Scored backlog with framework (RICE/ICE), stack-ranked |
| "Evaluate our portfolio" | BCG map with invest/maintain/kill recommendations per product |
| "Design our product org" | Org proposal with topology, ratios, reporting, and transition plan |
| "Product board section" | Board slide: north star, retention, roadmap highlights, risks |
| "Set our north star" | North star proposal with hierarchy, leading indicators, and guard rails |
| "Kill a product" | Sunset plan: timeline, migration, communication, team reallocation |
Tool Reference
1. product_portfolio_analyzer.py
Analyzes a product portfolio using BCG matrix classification (Star/Cash Cow/Question Mark/Dog), calculates portfolio health scores, identifies investment misalignment, and generates rebalancing recommendations.
python scripts/product_portfolio_analyzer.py --input portfolio.json --json
python scripts/product_portfolio_analyzer.py --input portfolio.json| Flag | Type | Description |
|---|---|---|
--input | required | Path to JSON file with products (revenue, growth rate, market share, engineering investment %, retention) |
--json | optional | Output in JSON format instead of human-readable text |
2. feature_prioritizer.py
Prioritizes features using RICE scoring (Reach x Impact x Confidence / Effort). Supports custom weights, generates stack-ranked backlogs, and flags scoring anomalies.
python scripts/feature_prioritizer.py --input features.json --json
python scripts/feature_prioritizer.py --input features.json --method rice| Flag | Type | Description |
|---|---|---|
--input | required | Path to JSON file with features (reach, impact, confidence, effort, optional category) |
--method | optional | Scoring method: rice (default), ice, or weighted |
--json | optional | Output in JSON format instead of human-readable text |
3. product_health_scorer.py
Scores product health across 5 dimensions: retention (D30/D90), engagement (DAU/MAU), satisfaction (NPS/Sean Ellis), growth (organic %), and activation (time to value). Generates PMF assessment and trend analysis.
python scripts/product_health_scorer.py --input product_data.json --json
python scripts/product_health_scorer.py --input product_data.json| Flag | Type | Description |
|---|---|---|
--input | required | Path to JSON file with product metrics across retention, engagement, satisfaction, growth, and activation |
--json | optional | Output in JSON format instead of human-readable text |
Troubleshooting
| Problem | Likely Cause | Resolution |
|---|---|---|
| Products stuck as "question marks" for 2+ quarters | No decision framework or leadership avoidance | Force invest-or-kill decision at next portfolio review; set 90-day milestones with automatic kill trigger |
| Engineering allocated to highest-revenue product while highest-growth product starves | Investment posture not aligned to growth potential | Run portfolio analyzer to quantify misalignment; reallocate using BCG classification |
| RICE scores gamed by PMs inflating reach or impact | No calibration process or shared scoring standards | Require evidence for each score dimension; run quarterly calibration sessions across PM teams |
| North star metric trending up while retention trends down | Wrong north star metric selected or metric is gameable | Re-evaluate north star against the 5 selection criteria; add retention as a guard rail metric |
| Roadmap built from sales requests instead of user data | No structured intake process or CPO not filtering | Implement feature request triage; require user research evidence before roadmap inclusion |
| Platform team has 6-week queue blocking stream teams | Platform not self-service; too many dependencies | Redesign platform for self-service APIs; add enabling team to unblock highest-priority streams |
| No user research conducted in 90+ days | Research not embedded in team workflow or understaffed | Embed researcher in product trio; set minimum research cadence (2 studies per quarter minimum) |
Success Criteria
- Every product has a clear investment posture (Invest/Maintain/Harvest/Kill) reviewed quarterly
- North star metric improving month-over-month for "Invest" products
- D30 retention flattening or improving for all active products
- Engineering investment percentage aligned to portfolio posture within 10% tolerance
- Feature prioritization uses a consistent scoring framework across all PM teams
- Time to first value decreasing quarter-over-quarter
- No product classified as "question mark" for more than 2 consecutive quarters
Scope & Limitations
In scope: Product-market fit assessment, portfolio management (BCG classification, investment postures), north star metric framework, product organization design (team topologies, ratios, product trio), feature prioritization (RICE/ICE scoring), product health scoring, CPO dashboard metrics, and board-level product reporting.
Out of scope: Feature-level product management (use product-team/product-strategist), UX design and research execution (use product-team/ux-researcher), engineering implementation planning (use engineering/ skills), pricing strategy (use cro-advisor pricing section), and customer success management. Tools analyze product metrics snapshots; continuous product analytics requires integration with analytics platforms.
Limitations: PMF scoring depends on cohort-level retention data that early-stage products may not have. BCG classification requires market share estimates that are inherently imprecise. RICE scoring is subjective; quality depends on calibration rigor. Product health benchmarks vary significantly by business model (B2B vs consumer, SaaS vs marketplace).
Integration Points
- ceo-advisor -- Product strategy translates CEO vision into product bets; portfolio health feeds board reporting
- cto-advisor -- Technical feasibility co-owned; features vs platform trade-off decisions require CTO partnership
- cro-advisor -- Sales-requested features filtered through CPO; expansion revenue depends on product roadmap
- cmo-advisor -- Launch timing aligned with demand gen capacity; product positioning informs marketing
- cfo-advisor -- Investment allocation per product justified with portfolio health data
- product-team/ -- CPO strategy executed through product managers; research and prioritization cascade down
© borghei, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 3 other files (scripts) in c-level-advisor/cpo-advisor of borghei/Claude-Skills.
- SKILL.md
- scripts/feature_prioritizer.py
- scripts/product_health_scorer.py
- scripts/product_portfolio_analyzer.py
Open the folder on GitHubat commit 4a698e8
Compare with similar skills
Cpo Advisor 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Cpo Advisor this skillborghei/Claude-Skills | 881 | — | ~4.9k | Automated safety check: Pass | MIT | |
| Game Changing FeaturesopenstatusHQ/data-table-filters | 2.3k | 3 repos | ~2.1k | Automated safety check: Pass | MIT | |
| Company Research Briefdeanpeters/Product-Manager-Skills | 7.2k | 2 repos | ~3.8k | Automated safety check: Pass | Custom licence | |
| Organic Growth Path Advisordeanpeters/Product-Manager-Skills | 7.2k | 2 repos | ~5.2k | Automated safety check: Pass | Custom licence | |
| Product Strategistalirezarezvani/claude-skills | 28k | 2 repos | ~1.8k | Automated safety check: Pass | MIT | |
| PlaidBuildGreatProducts/plaid | 217 | — | ~1.6k | Automated safety check: Pass | MIT |
Similar skills
Company Research Brief
deanpeters/Product-Manager-Skills
Builds a company research brief covering executive quotes, product strategy, transformation efforts and org context, tailored to interview prep, competitor or partnership work.
Organic Growth Path Advisor
deanpeters/Product-Manager-Skills
Diagnoses where a growth constraint lives and recommends one organic growth path from the McKinsey Growth Pyramid to test first.
Product Strategist
alirezarezvani/claude-skills
OKR cascade toolkit for product leaders: generates aligned company-to-team OKRs from five strategy types and scores how well they line up.
Plaid
BuildGreatProducts/plaid
Product Led AI Development — guides founders from idea to launched product.
Product Competitive Analysis
Fokkyp/claude-skills
Produces product-manager competitive analysis reports in Chinese, with a confirm-first scoping gate, three-phase evidence collection and single or multi-product modes.
More from borghei/Claude-Skills
All 349 skills in this repoAgents In The Team
borghei/Claude-Skills
Run delivery when AI coding and ops agents take tickets. An agent skill from borghei/Claude-Skills.
AI Content Disclosure
borghei/Claude-Skills
Check AI-generated marketing content and reviews for required disclosures under the EU AI Act, FTC rules and platform AI-label policies.
AI Prototyping
borghei/Claude-Skills
Idea to AI-generated prototype to customer validation to engineering handoff.
Analytics Engineer
borghei/Claude-Skills
Analytics engineering across data modeling, dbt, transformation, and semantic layers.
Ansoff Matrix
borghei/Claude-Skills
Ansoff Matrix — 4-quadrant framework for growth options: market penetration, market/product development, and diversification.
Brainstorm Okrs
borghei/Claude-Skills
OKR brainstorming and validation using the Radical Focus framework — outcome objectives, measurable key results, counter-metrics.
Related
Categories
Questions about Cpo Advisor
What does Cpo Advisor do?
Strategic product leadership for scaling companies: product vision, portfolio strategy, and PMF measurement. Cpo Advisor is an agent skill from borghei/Claude-Skills. Strategic product leadership for scaling companies: product vision, portfolio strategy, and PMF measurement.
When should I use Cpo Advisor?
Cpo Advisor fits situations like: setting product vision; managing a product portfolio; designing product teams.
How do I install Cpo Advisor in Claude Code?
Run `npx skills add borghei/Claude-Skills --skill cpo-advisor -a claude-code`. Or copy the skill folder (c-level-advisor/cpo-advisor in borghei/Claude-Skills) into .claude/skills/cpo-advisor in your project. Claude Code loads it when a task matches its description.
How do I install Cpo Advisor in Codex?
Run `npx skills add borghei/Claude-Skills --skill cpo-advisor -a codex`. Or copy the skill folder (c-level-advisor/cpo-advisor in borghei/Claude-Skills) into .agents/skills/cpo-advisor in your project. Codex loads it when a task matches its description.
Can I use Cpo Advisor 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 borghei/Claude-Skills --skill cpo-advisor -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/cpo-advisor, .gemini/skills/cpo-advisor, .github/skills/cpo-advisor and .opencode/skills/cpo-advisor in your project.
What does Cpo Advisor need to run?
Going by SKILL.md and its folder, Cpo Advisor needs Python for the scripts in its folder and the command-line tools its instructions call (python). Our summary lists: Python 3.
Does Cpo Advisor 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 Cpo Advisor 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Cpo Advisor use?
Cpo Advisor is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Cpo Advisor use?
About 4.9k tokens (SKILL.md is roughly 19k 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 Cpo Advisor?
Skills that share tags, products or a category with Cpo Advisor: Game Changing Features (openstatusHQ/data-table-filters, 2.3k stars), Company Research Brief (deanpeters/Product-Manager-Skills, 7.2k stars), Organic Growth Path Advisor (deanpeters/Product-Manager-Skills, 7.2k stars) and Product 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 Cpo Advisor?
borghei (a GitHub user) maintains it in borghei/Claude-Skills, which has 881 GitHub stars. The repository holds 349 skills in this directory. The repository was last updated on October 7, 2026.
Source: borghei/Claude-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.