altitude-horizon-framework

Understand the PM-to-Director transition through altitude and horizon thinking. Use when diagnosing scope, time-horizon, or leadership-level gaps.

Quality

68%

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/altitude-horizon-framework/SKILL.md

Quality

Content

70%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 genuinely useful, well-structured conceptual framework skill with clear workflows, concrete templates, and strong sequencing. Its main weaknesses are moderate verbosity (verbatim repetition of the intent) and a referenced examples file that does not exist in the bundle.

Suggestions

Remove the verbatim duplication of the frontmatter intent paragraph in the Purpose section to recover tokens.

Either add the referenced 'examples/sample.md' file or drop the 'See examples/sample.md' pointer so progressive disclosure references are all real.

Tighten the Named Failure Modes section by collapsing the repetitive 'What it looks like / Why it happens / The cost' tripling where the cost is self-evident.

Dimension	Reasoning	Score
Conciseness	The body is well-organized and mostly non-padded, but at ~240 lines it repeats the Purpose paragraph verbatim from the frontmatter intent and explains fairly familiar leadership-transition framing at length, which could be tightened.	3 / 5
Actionability	It provides concrete, usable artifacts: the six-step Cascading Context Map, a copy-paste markdown template, named failure modes with symptoms/fixes, and 30/60/90-day action lists. Minor gaps: no fully worked filled-in cascade template in-body.	4 / 5
Workflow Clarity	Multi-step processes (the six-step Cascading Context Map, the 30/60/90-day plan, the diagnosis-before-prescription loop) are explicitly sequenced with numbered steps and clear checkpoints; the 'diagnose which zone, then act' loop is a genuine feedback pattern.	5 / 5
Progressive Disclosure	No bundle directories (references/, scripts/, assets/) exist, yet the body references 'examples/sample.md' which is absent; structure is good via headers but a referenced file is missing and one external related skill is the only true offload.	3 / 5
	Total	15 / 20 Passed

Description

66%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 solid description that names a specific domain, gives a clear 'what', and an explicit 'Use when' trigger clause. It is slightly thin on enumerated concrete actions and on the breadth of trigger phrases that the body's scenarios reveal.

Suggestions

Add one or two more concrete actions (e.g., 'apply the Cascading Context Map to translate vague strategy into team clarity') to lift specificity.

Broaden the 'Use when' clause to mirror the body's scenarios, e.g., 'newly promoted to Director and something isn't clicking' or 'creating context from a vague company strategy'.

Dimension	Reasoning	Score
Specificity	The description names the domain (PM-to-Director transition) and one concrete action ('diagnosing scope, time-horizon, or leadership-level gaps') but stops at a single abstract action rather than listing multiple concrete capabilities.	3 / 5
Completeness	It answers both what ('Understand the PM-to-Director transition through altitude and horizon thinking') and when ('Use when diagnosing scope, time-horizon, or leadership-level gaps'), but the 'when' is narrower than the skill's full set of scenarios.	4 / 5
Trigger Term Quality	Natural trigger phrases like 'diagnosing scope, time-horizon, or leadership-level gaps' are present and would plausibly be said by a user, though it lacks synonyms/variations a user might phrase differently.	4 / 5
Distinctiveness Conflict Risk	The PM-to-Director framing is a fairly specific niche with minimal overlap risk against other skills, though it could conceivably overlap with adjacent career-leadership skills.	4 / 5
	Total	15 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
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/altitude-horizon-framework/SKILL.md
Commit: 1b5a524

Reviewed: ~8 hours 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.