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.

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/director-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 delivers highly actionable, well-sequenced coaching guidance with clear branching and concrete scripts. Its main weaknesses are overall length with some cross-branch repetition and a dangling reference to a non-existent examples file.

Suggestions

Move the four full example recommendation outputs into the referenced "examples/" bundle (and create that file) so SKILL.md keeps concise per-branch move lists and points to the long-form examples.

Tighten the recurring Hero Syndrome and 1-on-1 reframe language across branches by defining each pattern once in Key Concepts and referencing it, reducing redundancy.

Dimension	Reasoning	Score
Conciseness	The body (~340 lines) is mostly valuable specialized coaching content Claude would not already know, but the four full prose example-output blocks and repeated framings (Hero Syndrome and the 1-on-1 reframe recur across branches) add length that could be tightened, matching the "mostly efficient but could be tightened" anchor.	2 / 3
Actionability	Recommendations are concrete and ready to deliver — e.g., "Run a Cascading Context Map this week," "Reframe your 1-on-1s immediately" with copy-paste scripts like "I want to understand how each of your products connects to the business goals..." — meeting the actionable standard for an instruction-only skill.	3 / 3
Workflow Clarity	The flow is explicitly sequenced (Step 0 entry mode, Q1/3 routing, then per-branch Q2/3 and Q3/3 with numbered options and "Other (specify)"), with progress labels and a "choose a number to go deeper" follow-up loop; no destructive/batch validation cap applies to a coaching skill.	3 / 3
Progressive Disclosure	Cross-skill references to the mental model and facilitation protocol are clearly signaled and one level deep (a strength), but the body is a long monolithic block with four full inline example outputs that could be externalized, and the referenced "examples/conversation-flow.md" has no corresponding bundle file, fitting the score-2 anchor.	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 a clear, distinctive niche and an explicit "Use when" trigger. It is slightly held back by a single action verb and a thin spread of natural trigger phrases.

Suggestions

Replace the single verb "Guide" with several concrete actions (e.g., "Diagnose where you are in the PM-to-Director transition, surface the specific behavior shifts that matter, and deliver targeted coaching") to lift specificity.

Expand the trigger clause with natural phrasings users would actually say, e.g., "Use when you're preparing for a Director interview, just got promoted to Director, or are recalibrating a Director role that isn't working."

Dimension	Reasoning	Score
Specificity	"Guide the PM-to-Director transition across preparing, interviewing, landing, and recalibrating" names the domain and four specific sub-situations, but relies on a single action verb ("Guide") rather than listing multiple distinct concrete actions like the score-3 anchor ("extract text, fill forms, merge documents").	2 / 3
Completeness	It clearly states both what ("Guide the PM-to-Director transition...") and when with an explicit "Use when leadership scope is changing and you need practical coaching" clause, matching the score-3 anchor that answers both what and when with explicit triggers.	3 / 3
Trigger Term Quality	"PM-to-Director transition" is a natural phrase, and "Use when leadership scope is changing and you need practical coaching" supplies a trigger, but common variations a user would actually say ("promoted to Director," "Director interview prep," "new Director role") are missing, leaving coverage partial.	2 / 3
Distinctiveness Conflict Risk	The "PM-to-Director transition" framing is a narrow, well-defined career niche with distinct triggers, making it unlikely to fire for unrelated skills; it does not read generically like the score-2 "Works with document files" anchor.	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/director-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.