CtrlK
BlogDocsLog inGet started
Tessl Logo

decision-matrix

Compare options with weighted scoring, pros and cons, pre-mortems, opportunity costs, and ICE prioritization. Use when a user wants to reason through a choice, expose assumptions, or rank alternatives.

68

Quality

83%

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.

The body is a well-structured, actionable reference of named decision frameworks with concrete scales, formulas, and worked examples. It is efficient and clearly sequenced, with only minor opportunities to tighten length and add explicit validation checkpoints.

Suggestions

Tighten the Examples and Trigger Phrases sections, or move the worked examples into a separate references file, to reduce token load.

Add an explicit validation/checkpoint step in the Step-by-Step workflow (e.g., 're-score after confirming must-haves') to make the feedback loop explicit.

Make Step 3 ('Collect the Data') more concrete by specifying how to label and weight assumptions versus objective data.

DimensionReasoningScore

Conciseness

The body is well-organized and avoids explaining concepts Claude already knows, but at ~225 lines the worked examples and trigger-phrase table could be trimmed without losing clarity.

4 / 5

Actionability

Concrete scales (weights 1-5, scores 1-10), an explicit ICE formula, and worked examples with real numbers make the guidance actionable, though a few steps like 'Collect the Data' remain high-level.

4 / 5

Workflow Clarity

A clear 7-step sequence is paired with a 'Quality checks' checklist and bias-mitigation table; validation is implicit rather than an explicit checkpoint, but the skill is non-destructive so no cap applies.

4 / 5

Progressive Disclosure

Sections are well-signaled and self-contained with no nested references, though the six frameworks and examples could optionally be split into one-level-deep reference files.

4 / 5

Total

16

/

20

Passed

Description

92%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, third-person description that clearly states capabilities and trigger conditions. It is comprehensive and distinctive, with only minor room to broaden natural trigger phrasing.

DimensionReasoningScore

Specificity

Lists multiple concrete, named methods — 'weighted scoring, pros and cons, pre-mortems, opportunity costs, and ICE prioritization' — giving comprehensive coverage of the skill's capabilities.

5 / 5

Completeness

Explicitly answers both what (compare options via the listed frameworks) and when ('Use when a user wants to reason through a choice, expose assumptions, or rank alternatives') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural phrases such as 'reason through a choice', 'expose assumptions', and 'rank alternatives', but a few common user variations (e.g. 'help me decide', 'prioritize these') are absent.

4 / 5

Distinctiveness Conflict Risk

The named frameworks (pre-mortem, ICE, opportunity cost, Pugh matrix) carve a clear decision-support niche with distinct triggers and minimal overlap with other skills.

5 / 5

Total

19

/

20

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
iflytek/skillhub
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.