CtrlK
BlogDocsLog inGet started
Tessl Logo

director-readiness-advisor

Guide the PM-to-Director transition across preparing, interviewing, landing, and recalibrating. Use when leadership scope is changing and you need practical coaching.

65

Quality

79%

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/director-readiness-advisor/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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, highly actionable interactive coaching skill with a clear branched workflow and concrete example outputs. Its main weaknesses are some duplication and repeated scaffolding affecting conciseness, and progressive disclosure is hurt by references pointing to non-existent bundle files and lengthy inline worked examples that could be split out.

Suggestions

Remove the near-verbatim duplication between the frontmatter 'intent' and the Purpose section, or repurpose Purpose to add only new information.

Create the referenced examples/conversation-flow.md file (or drop the reference) so the bundle matches what the body points to, and consider moving the four full worked-example recommendation blocks into per-branch reference files to slim the main SKILL.md.

Tighten the repeated question-scaffolding across the four branches (e.g., factor the shared 'Or describe your situation directly' / 'Choose a number to go deeper' framing) to reduce token cost.

DimensionReasoningScore

Conciseness

The body is substantive coaching content that mostly earns its tokens, but the Purpose section duplicates the frontmatter intent nearly verbatim and the four branches repeat scaffolding patterns; it could be tightened, fitting 'mostly efficient but includes some unnecessary explanation or could be tightened' — not 4 due to the duplicated intent and repeated structure.

3 / 5

Actionability

As an instruction-only interactive skill it provides concrete question scripts, numbered response options, and full worked example recommendation outputs that are copy-ready and cover the common cases, matching the 'fully executable; specific examples cover the common cases' anchor.

5 / 5

Workflow Clarity

The flow is clearly sequenced (Step 0 → Q1 → branch Q2/Q3 → recommendations) with progress labels and explicit branching, fitting 'clear sequence with most checkpoints present'; not 5 because there are no explicit feedback/validation loops, though the coaching Q&A nature does not strictly require them.

4 / 5

Progressive Disclosure

References are signaled (examples/conversation-flow.md, altitude-horizon-framework, workshop-facilitation) but none of the referenced files exist in the bundle, and the full inlined worked-example recommendation scripts for all four branches are lengthy content that could live in separate files, fitting 'some structure but could be better organized; references present but not clearly signaled; content that should be separate is inline'.

3 / 5

Total

15

/

20

Passed

Description

87%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 specifies a clear niche, enumerates the four transition phases, and provides an explicit 'Use when' trigger clause answering both what and when. It falls just short of maximum specificity and trigger coverage only because the phase list is somewhat abstract and omits common synonyms like 'promotion' or 'first 90 days'.

DimensionReasoningScore

Specificity

Names the PM-to-Director domain and enumerates four concrete transition phases (preparing, interviewing, landing, recalibrating) rather than generic actions, fitting 'lists several specific actions; minor gaps' — not 5 because the phases are somewhat abstract capabilities rather than multiple distinct concrete actions.

4 / 5

Completeness

Explicitly answers both what ('Guide the PM-to-Director transition across...') and when ('Use when leadership scope is changing and you need practical coaching') with concrete trigger phrases, matching the anchor for clearly and explicitly answering both.

5 / 5

Trigger Term Quality

Includes natural terms a user would say ('PM-to-Director transition', 'leadership scope is changing', 'practical coaching') with good coverage, but misses common synonyms like 'promotion', 'new Director role', or 'first 90 days', fitting 'good keyword coverage; a few natural terms missing'.

4 / 5

Distinctiveness Conflict Risk

'PM-to-Director transition' is a narrow, well-defined niche with distinct triggers and minimal overlap risk with unrelated skills, matching the 'clear niche with distinct triggers; minimal conflict risk' anchor.

5 / 5

Total

18

/

20

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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