CtrlK
BlogDocsLog inGet started
Tessl Logo

prioritize

Take a list of ideas, features, or initiatives and quickly prioritize them using an effective framework. Use when you have too many things and need to decide what to do first.

71

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

100%

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

The body is a tight, highly actionable prioritization playbook with a clear sequenced workflow and an embedded sanity-check validation step, well-organized into sections with no external references needed. It is a strong example of an instruction-only skill.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence: it provides the RICE formula, specific numeric scales, a table format, and rules without explaining what prioritization is or padding with concepts Claude already knows.

3 / 3

Actionability

As an instruction/prompt skill it gives concrete, specific, copy-paste-ready guidance — explicit RICE scales, a sorted-table output format, a sanity-check checklist, and a top-3/defer/kill recommendation structure.

3 / 3

Workflow Clarity

The process is explicitly sequenced (Clarify → Score RICE → Sanity Check → Recommendation) with a built-in validation checkpoint in the Sanity Check step and tradeoff rules for near-tied scores.

3 / 3

Progressive Disclosure

It is a single-purpose skill with no bundle files and no need for external references; content is well-organized into clearly labeled sections (Prompt Template, Tips, numbered steps), satisfying the simple-skill allowance for a top score.

3 / 3

Total

12

/

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 the skill does and when to use it with a distinct niche, but its action list is narrow and its trigger terms omit common phrasings like "rank" or "prioritize this list". Tightening specificity and expanding trigger coverage would raise it further.

Suggestions

Add a few more concrete verbs to the action list (e.g., 'score, rank, and recommend what to do first') to reach the multi-action score-3 anchor for specificity.

Broaden the 'Use when' trigger to include natural variations users say: 'prioritize this list', 'rank these', 'help me decide', or 'what should we do first'.

DimensionReasoningScore

Specificity

It names the domain ("ideas, features, or initiatives") and a concrete action ("prioritize them using an effective framework"), but describes a single action rather than listing multiple specific concrete actions like the score-3 anchor.

2 / 3

Completeness

It explicitly answers what ("Take a list... prioritize them using an effective framework") and when (explicit "Use when..." trigger), matching the score-3 anchor for both what and when.

3 / 3

Trigger Term Quality

The "Use when you have too many things and need to decide what to do first" clause offers natural phrases, but misses common variations a user would say such as "prioritize this list", "rank these", or "help me decide".

2 / 3

Distinctiveness Conflict Risk

Prioritizing a list via a scoring framework is a clear niche with distinct triggers unlikely to fire for unrelated skills, matching the score-3 anchor.

3 / 3

Total

10

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
amplitude/builder-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.