CtrlK
BlogDocsLog inGet started
Tessl Logo

executive-onboarding-playbook

Plan a VP or CPO 30-60-90 day diagnostic onboarding path. Use when entering a new executive product role and avoiding premature change.

68

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

77%

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

A well-structured, highly actionable executive-onboarding playbook with clear phased sequencing and validation checkpoints. Its main gaps are verbosity that could be trimmed and a lack of real bundle-based progressive disclosure.

Suggestions

Trim narrative analogies (e.g. the power-plant "big red switch" passage) to tighten conciseness without losing the diagnostic-vs-execution framing.

Materialize the referenced examples/sample.md (and consider splitting the long per-phase step detail into a reference file) so progressive-disclosure references resolve to real bundle files.

Move the extended good/bad examples into a separate examples file referenced one level deep, keeping SKILL.md as a tighter overview.

DimensionReasoningScore

Conciseness

Mostly high-signal domain guidance rather than generic concepts Claude already knows, but the body is long and includes narrative padding (e.g. the power-plant "big red switch" analogy) that could be tightened.

2 / 3

Actionability

Provides copy-paste-ready guidance — the five CEO probing questions, the diagnostic interview question set, concrete per-phase steps, and explicit deliverables — giving specific, executable direction.

3 / 3

Workflow Clarity

Phases 0–3 are clearly sequenced with numbered steps and deliverables, and include explicit validation checkpoints (Month 2 reality-checks with the boss, pattern-matching across independent sources) that function as feedback loops.

3 / 3

Progressive Disclosure

The body is well-sectioned but essentially monolithic; referenced files (examples/sample.md, sibling skill SKILL.md paths) are not present in the bundle, and content that could be split out (detailed phase steps, examples) remains inline.

2 / 3

Total

10

/

12

Passed

Description

90%

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

A concise, well-targeted description with an explicit Use-when trigger and distinct executive-product niche. Its only weakness is naming a single action rather than enumerating several specific capabilities.

DimensionReasoningScore

Specificity

Names a concrete domain ("VP or CPO 30-60-90 day diagnostic onboarding path") and a single concrete action ("Plan"), but does not list multiple specific actions as the top anchor requires.

2 / 3

Completeness

Explicitly answers both what ("Plan a VP or CPO 30-60-90 day diagnostic onboarding path") and when via an explicit "Use when entering a new executive product role" clause.

3 / 3

Trigger Term Quality

Covers natural terms a user would actually say — "VP", "CPO", "new executive product role", and "30-60-90 day" — giving good trigger coverage.

3 / 3

Distinctiveness Conflict Risk

Targets a clear niche (executive product-leadership onboarding) with distinct triggers, making it unlikely to fire for the wrong skill.

3 / 3

Total

11

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
deanpeters/Product-Manager-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.