vp-cpo-readiness-advisor

Guide the transition to VP or CPO across preparing, interviewing, landing, and recalibrating. Use when executive product scope is changing fast.

Quality

59%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/vp-cpo-readiness-advisor/SKILL.md

Quality

Content

55%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 body is well-structured and highly actionable for an interactive advisory skill, with a clear sequenced workflow and concrete example outputs. Its main weakness is conciseness — the Key Concepts and full inlined recommendation scripts make it long — compounded by unverified external references given there is no bundle.

Suggestions

Move the full per-branch recommendation scripts and the Key Concepts exposition into reference files (e.g. concepts.md, branch-recommendations.md) and keep SKILL.md as an overview with pointers, sharply reducing token load.

Verify or remove the referenced paths (examples/conversation-flow.md and the sibling skills/executive-onboarding-playbook, altitude-horizon-framework, director-readiness-advisor, workshop-facilitation); references to non-existent files hurt navigation.

Trim the restated Rubik's Cube analogy and other repeated conceptual explanations to a single concise statement; assume the reader's competence for basic leadership concepts.

Dimension	Reasoning	Score
Conciseness	At ~400 lines the body is noticeably verbose: the Key Concepts section extensively explains leadership concepts and metaphors (the Rubik's Cube analogy restated twice, the Empowerment Myth) that add length without proportional guidance value, and full recommendation scripts are inlined rather than summarized.	2 / 5
Actionability	The branch structure gives concrete, copy-ready diagnostic questions, numbered response options, and example recommendation outputs that an agent can execute directly, with only minor gaps (some recommendations point outward to skills whose existence cannot be verified).	4 / 5
Workflow Clarity	The interaction is clearly sequenced (Step 0 entry mode, Q1/3 then adaptive Q2/Q3 branches, then enumerated recommendations) with explicit progress labels and a cross-referenced facilitation protocol; it lacks formal validation checkpoints, but this advisory skill has no destructive/batch operations that would require them.	4 / 5
Progressive Disclosure	Structure exists (Purpose, Input, Key Concepts, Application, Examples, Pitfalls, References) and references are mostly one-level-deep, but no bundle files exist, so the cited paths (examples/conversation-flow.md, the sibling skills) cannot be verified and large inlined recommendation scripts and concept exposition that could live in separate files are kept inline.	3 / 5
	Total	13 / 20 Passed

Description

63%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 concise and uses correct third-person voice with an explicit Use-when trigger, covering both what and when. Its main weakness is trigger-term breadth — the keywords skew toward executive jargon rather than the natural phrases a user would actually say.

Suggestions

Add natural-language trigger terms users actually say, e.g. 'Use when preparing for a VP or CPO role, evaluating a CPO offer, or recalibrating an executive product role that isn't working'.

Replace the abstract 'executive product scope is changing fast' trigger with concrete situations (preparing, interviewing, newly landed, recalibrating) drawn from the body's four branches.

Consider mentioning the Director-to-VP and VP-to-CPO transitions explicitly in the description to sharpen distinctiveness from generic leadership/coaching skills.

Dimension	Reasoning	Score
Specificity	Names the domain and four concrete transition phases ("preparing, interviewing, landing, and recalibrating"), which is more than 1-2 actions but stops short of fully comprehensive action coverage.	4 / 5
Completeness	It states both what ("Guide the transition to VP or CPO across...") and when ("Use when executive product scope is changing fast"), but the when clause is somewhat abstract and could name the triggering situations more explicitly.	4 / 5
Trigger Term Quality	It includes the natural trigger phrase "Use when executive product scope is changing fast", but the keywords are domain-jargon heavy ("executive product scope") and miss common user phrasings like "VP transition," "CPO offer," or "executive product role."	3 / 5
Distinctiveness Conflict Risk	The VP/CPO executive-transition niche is fairly distinct and would rarely conflict with other skills, though "executive product scope is changing fast" is slightly broad and could overlap with adjacent leadership skills.	4 / 5
	Total	15 / 20 Passed

Validation

87%

Warnings & errors only

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

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 1 suspicious	Warning

	Total	14 / 16 Passed

Repository: deanpeters/Product-Manager-Skills
Path: skills/vp-cpo-readiness-advisor/SKILL.md
Commit: a03af68

Reviewed: 11 days ago

Table of Contents

Discovery Implementation Validation

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.