CtrlK
BlogDocsLog inGet started
Tessl Logo

prioritization-frameworks

Reference guide to 9 prioritization frameworks with formulas, when-to-use guidance, and templates — RICE, ICE, Kano, MoSCoW, Opportunity Score, and more. Use when selecting a prioritization method, comparing frameworks like RICE vs ICE, or learning how different prioritization approaches work.

68

Quality

85%

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

SKILL.md
Quality
Evals
Security

Quality

Content

75%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 well-organized reference guide that delivers concrete formulas, scales, and a comparative selection table without over-explaining fundamentals. Tightening the occasional redundant commentary would push conciseness higher, and an explicit selection workflow could strengthen workflow clarity.

Suggestions

Trim redundant phrasing such as 'Considers not only value but also risk and economic factors' and the duplicate 'Accounts for risk'/'Accounts for economic factors' notes under ICE.

Add a brief explicit selection workflow (e.g., 'Identify your decision type → match to a Best-For row → apply the formula') to make the implicit selection path a clear sequence.

Consider moving the lengthy external template/further-reading link list into a short pointer while keeping the two or three most-used links inline to improve progressive disclosure.

DimensionReasoningScore

Conciseness

The body is largely lean, giving formulas and scales directly without explaining what prioritization is, but includes minor padding such as 'Considers not only value but also risk and economic factors' and 'Accounts for risk'/'Accounts for economic factors' that could be trimmed, fitting 'efficient; minor instances of over-explanation'.

4 / 5

Actionability

Concrete formulas (Opportunity Score = Importance × (1 − Satisfaction), Score = I × C × E, (R × I × C) / E) with explicit scales (normalize 0–1, Confidence 1-10 or 0-100%, Effort in person-months) give actionable guidance, with only minor gaps in execution detail, fitting the 4 anchor; as an instruction-only skill it is not penalized for lacking code.

4 / 5

Workflow Clarity

The 9-frameworks overview table with 'Best For' and 'Key Insight' columns plus explicit 'Recommended' markers gives a clear selection-then-apply path with most checkpoints present; no destructive/batch operation applies, so no cap, but explicit sequencing of a selection workflow is only implied rather than enumerated.

4 / 5

Progressive Disclosure

Content is organized into clear, well-signaled sections (Core Principle, per-framework, overview table, Templates, Further Reading) with one-level external links and no nested references; it is a single cohesive reference rather than a monolith, fitting 'good structure; most content appropriately placed' though it is slightly above the under-50-line simple-skill case.

4 / 5

Total

16

/

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.

A strong description that clearly communicates purpose, scope, and trigger conditions with concrete named frameworks. Minor specificity gains are possible by listing a couple more capabilities, but it already answers what-and-when explicitly.

DimensionReasoningScore

Specificity

The description names the domain and several concrete deliverables ('formulas, when-to-use guidance, and templates') plus specific frameworks, but stops short of fully enumerating all capabilities, so it fits the 'several specific actions; minor gaps' anchor rather than the comprehensive 5.

4 / 5

Completeness

It explicitly states both what it does ('Reference guide to 9 prioritization frameworks with formulas, when-to-use guidance, and templates') and when to use it ('Use when selecting a prioritization method, comparing frameworks... or learning...'), with concrete trigger phrases matching the top anchor.

5 / 5

Trigger Term Quality

Natural phrases like 'selecting a prioritization method', 'comparing frameworks like RICE vs ICE', and named frameworks cover what a user would say, with only minor synonyms missing, matching 'good keyword coverage; a few natural terms missing' rather than the fully comprehensive 5.

4 / 5

Distinctiveness Conflict Risk

The prioritization-frameworks niche with named, distinct triggers (RICE, ICE, Kano, MoSCoW, Opportunity Score) is a clear niche with minimal conflict risk against unrelated skills, matching the top anchor.

5 / 5

Total

18

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
phuryn/pm-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.