CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

75%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/executive-onboarding-playbook/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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.

A well-structured, actionable executive-transition playbook with a clear phased workflow and explicit validation checkpoint; its main weaknesses are moderate verbosity and a referenced example file that does not exist in the bundle.

Suggestions

Tighten the Key Concepts prose (e.g. the 'big red switch' and 'steering/rudder' analogies) to reduce token load without losing the diagnostic mindset message.

Provide a compact evidence-log/notebook template or schema for the Phase 1 deliverable so the guidance is fully copy-paste ready.

Either ship `examples/sample.md` (referenced in the Examples section) or remove the dangling reference so progressive disclosure stays one level deep with no broken links.

DimensionReasoningScore

Conciseness

The ~274-line body is mostly efficient advisory content rather than padding about concepts Claude already knows, but it carries narrative flair (the 'big red switch' / 'steering and rudder' analogies) and prose that could be tightened, matching the 'mostly efficient but could be tighter' anchor.

3 / 5

Actionability

It gives concrete, executable guidance — exact interview questions, numbered per-phase steps, and per-phase deliverables — so absence of code is not penalized; minor gaps (no templates for the evidence log) keep it just below fully copy-paste ready.

4 / 5

Workflow Clarity

A clear Phase 0 → 1 → 2 → 3 sequence with numbered steps and deliverables, plus an explicit validation checkpoint ('reality-check with your boss'); it lacks a formal error-recovery loop or checklist, so it does not reach anchor 5.

4 / 5

Progressive Disclosure

Well-organized into clearly headed sections (Purpose, Key Concepts, Application, Examples, Pitfalls, References) with one-level-deep, clearly signaled references to related skills; the dangling `examples/sample.md` reference (file not present in the bundle) is a minor organization gap that holds it at 4 rather than 5.

4 / 5

Total

15

/

20

Passed

Description

73%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.

A strong, specific description with an explicit 'Use when' trigger and a clear niche; its main limitation is naming a single action rather than enumerating several concrete capabilities.

DimensionReasoningScore

Specificity

It names the domain ('VP or CPO 30-60-90 day diagnostic onboarding path') and one concrete action ('Plan...'), but does not enumerate multiple specific actions, so it sits at the 'domain + 1-2 actions' anchor rather than the multi-action anchors above.

3 / 5

Completeness

It answers both 'what' (plan a diagnostic onboarding path) and 'when' (explicit 'Use when entering a new executive product role'), but the trigger 'avoiding premature change' is somewhat abstract, keeping it just below the fully concrete anchor 5.

4 / 5

Trigger Term Quality

Natural terms a user would say are present ('VP or CPO', '30-60-90 day', 'executive product role', 'onboarding'), giving good keyword coverage, though a few synonyms (e.g. 'first 90 days', 'new role') are not surfaced in the description itself.

4 / 5

Distinctiveness Conflict Risk

The 'VP or CPO 30-60-90 day diagnostic onboarding' niche is highly specific with distinct triggers and minimal realistic overlap with other skills.

5 / 5

Total

16

/

20

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.

Validation — 15 / 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

Path

skills/executive-onboarding-playbook/SKILL.md

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.