CtrlK
BlogDocsLog inGet started
Tessl Logo

cpo-advisor

Product leadership for scaling companies. Product vision, portfolio strategy, product-market fit, and product org design. Use when setting product vision, managing a product portfolio, measuring PMF, designing product teams, prioritizing at the portfolio level, reporting to the board on product, or when user mentions CPO, product strategy, product-market fit, product organization, portfolio prioritization, or roadmap strategy.

64

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

The risk profile of this skill

Fix and improve this skill with Tessl

tessl review fix ./c-level-advisor/skills/cpo-advisor/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

68%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is a well-structured advisory overview with executable scoring scripts and clearly signaled one-level-deep references. It is concise and actionable, but workflow clarity is limited by implicit rather than explicit validation checkpoints in the advisory process.

Suggestions

Add an explicit numbered workflow with validation checkpoints for the core advisory processes (e.g., score PMF -> interpret thresholds -> decide posture -> validate with cross-functional peer review), rather than leaving the Internal Quality Loop as an external reference.

Trim or remove the 'Reasoning Technique: First Principles' section, which restates a concept Claude already knows and adds tokens without domain-specific value.

Consider moving the detailed CPO Dashboard and North-Star-by-business-model tables into a reference file to keep SKILL.md a tighter overview, with inline pointers.

DimensionReasoningScore

Conciseness

The body is lean and table/bullet-driven, assuming Claude's competence; minor instances of over-explanation exist (e.g., the generic 'Reasoning Technique: First Principles' section restates a concept Claude already knows).

4 / 5

Actionability

Provides concrete, runnable commands ('python scripts/pmf_scorer.py', 'python scripts/portfolio_analyzer.py') backed by real executable scripts with sample data, plus specific signal/action tables; minor gaps in fully prescriptive step-by-step procedures for the advisory tasks.

4 / 5

Workflow Clarity

Sequences are present (Quick Start commands, metrics hierarchy, invest/maintain/kill flow) but explicit validation checkpoints are largely implicit; the Internal Quality Loop is referenced but not embedded as a concrete step-by-step workflow with checkpoints.

3 / 5

Progressive Disclosure

Good structure with a Resources table mapping each real bundle file (3 references, 2 scripts) to a 'When to load' condition; references are one level deep and clearly signaled, though some detailed inline content (e.g., the full metrics dashboard) could arguably live in references.

4 / 5

Total

15

/

20

Passed

Description

83%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is strong: it clearly states both capabilities and explicit 'Use when' triggers with natural synonyms, and carves out a distinct CPO niche. It is comprehensive and concise without fluff, with only minor gaps in trigger-term variants and slight overlap risk with related product skills.

DimensionReasoningScore

Specificity

Lists several concrete activities ('setting product vision, managing a product portfolio, measuring PMF, designing product teams, prioritizing at the portfolio level, reporting to the board on product') rather than vague abstractions, though they are activity categories rather than fully granular operations, leaving minor coverage gaps.

4 / 5

Completeness

Explicitly answers both what ('Product leadership for scaling companies. Product vision, portfolio strategy, product-market fit, and product org design.') and when ('Use when setting product vision, managing a product portfolio, measuring PMF, designing product teams, prioritizing at the portfolio level, reporting to the board on product, or when user mentions CPO, product strategy, product-market fit, product organization, portfolio prioritization, or roadmap strategy.').

5 / 5

Trigger Term Quality

Good keyword coverage with natural terms and synonyms users would say ('CPO', 'product strategy', 'product-market fit', 'PMF', 'product organization', 'portfolio prioritization', 'roadmap strategy'); a few natural variants like 'chief product officer' are absent.

4 / 5

Distinctiveness Conflict Risk

The CPO/product-leadership niche is mostly distinct with role-specific triggers, but there is minor overlap risk with adjacent product-management or other C-level skills.

4 / 5

Total

17

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
alirezarezvani/claude-skills
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.