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

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/altitude-horizon-framework/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 body is highly actionable with clear, sequenced workflows and concrete examples, but it carries some restatement that hurts conciseness and references bundle files that are not actually present, weakening progressive disclosure.

Suggestions

Remove the verbatim duplication of the frontmatter intent in the Purpose section, or compress it to a single framing sentence.

Either create the referenced `examples/sample.md` (and the `director-readiness-advisor` skill) or drop the dangling references so navigation is real rather than promised.

Consolidate the Cascading Context Map description so the six-step list and the markdown template are presented once, cross-referenced rather than repeated.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient — using tables, bullets, and named concepts — but it restates the frontmatter intent verbatim in the Purpose section and explains the Cascading Context Map twice (six-step list plus template), so it could be tightened.	2 / 3
Actionability	It gives concrete, specific guidance: a 30/60/90-day action sequence, a copy-paste Cascading Context Map template, and worked Good/Bad examples with explicit reasoning — fully actionable for an instruction-only skill.	3 / 3
Workflow Clarity	The Cascading Context Map is a clearly sequenced six-step process with a template and an explicit "one page is better than ten" guidance, and the application sections lay out ordered checkpoints; no destructive or batch operations require validation here.	3 / 3
Progressive Disclosure	It signals external references ("See examples/sample.md", "director-readiness-advisor"), but those referenced files do not exist in the bundle and the bulk of the framework is inlined rather than split, leaving structure present but not well realized.	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 an explicit trigger clause and occupies a distinct niche, but its lead verb is abstract and several trigger terms are framework-internal jargon rather than natural user phrasing.

Suggestions

Lead with a more concrete action than "Understand" — e.g., "Diagnose PM-to-Director transition gaps using the altitude (scope) and horizon (time) model."

Add plain-language trigger terms users would actually say, such as "PM to Director promotion," "role transition friction," or "thinking at the wrong level."

Consider dropping or softening the jargon "altitude and horizon thinking" in the description, or pairing it with the parenthetical glosses (scope / time) so the trigger still reads naturally.

Dimension	Reasoning	Score
Specificity	"Understand the PM-to-Director transition through altitude and horizon thinking" names the domain and core model, but the verb "Understand" is abstract rather than a list of concrete actions, fitting the 'names domain and some actions but not comprehensive' anchor.	2 / 3
Completeness	It explicitly 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"), with an explicit 'Use when' clause.	3 / 3
Trigger Term Quality	"diagnosing scope, time-horizon, or leadership-level gaps" gives some natural trigger terms, but "altitude and horizon thinking" is framework jargon a user would be unlikely to say unprompted, so common variations are missing.	2 / 3
Distinctiveness Conflict Risk	The PM-to-Director transition framed through a specific two-axis mental model is a clear niche with distinct triggers, making it unlikely to fire for the wrong skill.	3 / 3
	Total	10 / 12 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: 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.