prioritization-advisor

Choose a prioritization framework based on stage, team context, and stakeholder needs. Use when deciding between RICE, ICE, value/effort, or another scoring approach.

Quality

83%

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

Quality

Content

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured interactive skill with strong actionability and a clear question sequence, but it is verbose in places and monolithic where a leaner SKILL.md pointing to reference files would improve token efficiency and navigation.

Suggestions

Remove the verbatim repeat of the frontmatter intent in the Purpose section and the '[If Dean has prioritization resources, link here]' placeholder to tighten conciseness.

Move the long output template and/or the worked examples into a references/ file, leaving SKILL.md as a concise overview with a clearly signaled link.

Condense the generic placeholder-laden output template into a shorter skeleton, since Example 1 already demonstrates the filled-in concrete form.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient but padded in places: the Purpose section repeats the frontmatter intent verbatim, the output template is a very long placeholder block, and leftover fluff like '[If Dean has prioritization resources, link here]' adds no value. It is not at the lean/efficient level because several sections could be tightened.	2 / 3
Actionability	Concrete enumerated options per question, a fully specified output template, and a worked Example 1 with an actual RICE scoring table and formula give copy-paste-ready, executable guidance for an instruction-only interactive skill.	3 / 3
Workflow Clarity	The process is clearly sequenced (Q1-Q4 adaptive questions, then a structured recommendation), with explicit ARGUMENTS/empty-handling handling and a delegated facilitation protocol; no destructive or batch operations are involved, so the absence of validation loops does not cap the score.	3 / 3
Progressive Disclosure	The one external reference (workshop-facilitation) is clearly signaled and one level deep, but the skill is a large monolithic file with the long output template, examples, and pitfalls all inline rather than split into bundle files, fitting the 'content that should be separate is inline' anchor.	2 / 3
	Total	10 / 12 Passed

Description

90%

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 description with explicit what/when triggers and good natural-language keywords; its only weakness is that it describes a single choosing action rather than enumerating multiple concrete capabilities.

Dimension	Reasoning	Score
Specificity	The description names the domain and one core action ('Choose a prioritization framework based on stage, team context, and stakeholder needs') but does not list multiple distinct concrete actions, so it stops at the 'names domain and some actions' anchor rather than the multi-action level.	2 / 3
Completeness	It explicitly answers both what ('Choose a prioritization framework...') and when ('Use when deciding between...'), matching the anchor requiring an explicit 'Use when' trigger clause.	3 / 3
Trigger Term Quality	'Use when deciding between RICE, ICE, value/effort, or another scoring approach' gives strong coverage of the natural terms a user would actually say when reaching for this skill.	3 / 3
Distinctiveness Conflict Risk	The prioritization-framework-selection niche with named frameworks (RICE, ICE, value/effort) is a clear, distinct trigger set unlikely to fire for unrelated skills.	3 / 3
	Total	11 / 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/prioritization-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.