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

76%

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

77%

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

The skill is highly actionable with a clearly sequenced branching workflow, but it is overlong for a single file with duplicated framing content and a broken examples reference that weakens its progressive-disclosure structure.

Suggestions

Remove the duplication between the Purpose section and the frontmatter intent, and consolidate the Four Transition Situations so they appear once rather than in both Key Concepts and Question 1.

Move the lengthy per-branch recommendation templates into a reference file (e.g. references/recommendations.md) and keep SKILL.md as a branching overview, and either ship or remove the missing 'examples/conversation-flow.md' reference.

Dimension	Reasoning	Score
Conciseness	The content is domain-specific lived-experience coaching Claude would not already know, but the Purpose section duplicates the frontmatter intent verbatim and the Four Transition Situations are enumerated twice (Key Concepts and Question 1), so it could be meaningfully tightened.	2 / 3
Actionability	It provides concrete numbered diagnostic questions with explicit response options and fully worked example recommendation outputs with specific named actions ('Run the five CEO interview questions', 'Start the weekly executive alignment practice now', 'Do the language audit').	3 / 3
Workflow Clarity	The flow is explicitly sequenced (Step 0 session start → Q1 branch → per-branch Q2/Q3 → recommendations) with progress labels (Q1/3, Q2/3) and clear branch logic; as a non-destructive coaching Q&A it does not require validation checkpoints.	3 / 3
Progressive Disclosure	The body is monolithic with all four branches' full recommendation templates inline, no bundle files exist to offload detail, and the referenced 'examples/conversation-flow.md' path does not exist in the bundle.	2 / 3
	Total	10 / 12 Passed

Description

75%

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 cleanly answers both what and when with an explicit trigger and occupies a distinctive niche, but its action verb is generic and its trigger phrase is more abstract than what a user would naturally say.

Suggestions

Replace the abstract trigger 'executive product scope is changing fast' with phrasing a user would actually say, e.g. 'Use when preparing for, interviewing for, or recalibrating a VP or CPO role.'

Swap the single verb 'Guide' for concrete actions, e.g. 'Diagnose where you are in the VP/CPO transition and deliver situation-specific coaching across preparing, interviewing, landing, and recalibrating.'

Dimension	Reasoning	Score
Specificity	Names the domain ('transition to VP or CPO') and four stages ('preparing, interviewing, landing, and recalibrating'), but relies on a single abstract verb ('Guide') rather than listing multiple concrete operations, so it stops short of the level-3 anchor.	2 / 3
Completeness	It states what the skill does ('Guide the transition...') and gives an explicit 'Use when...' trigger clause, satisfying both halves with an explicit trigger.	3 / 3
Trigger Term Quality	Natural tokens 'VP' and 'CPO' are present, but the trigger phrase 'executive product scope is changing fast' is abstract jargon a user would rarely say aloud, missing common variations like 'VP offer' or 'promoted to CPO'.	2 / 3
Distinctiveness Conflict Risk	The VP/CPO executive-transition niche is highly specific with distinct triggers, making conflict with other skills unlikely.	3 / 3
	Total	10 / 12 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: 9971018

Reviewed: 3 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.