CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

skill-decision-support

Present options with trade-offs for informed decision-making — use when choosing between approaches

Quality

70%

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

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/skill-decision-support/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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 instruction skill: a clearly sequenced five-phase workflow, concrete templates, and useful worked patterns. Its main costs are token efficiency — redundant summary sections and repeated template blocks — and the absence of a fully worked scoring example, which leaves the core quantitative technique demonstrated only in placeholder form.

Suggestions

Cut the "Quick Reference" and "The Bottom Line" sections and the "When to Use" block (which duplicates the frontmatter trigger), saving tokens with no loss of guidance.

Include one fully worked scoring example with real raw and weighted numbers so the "Criteria and scores" table technique is demonstrated, not just templated.

Move the three "Common Patterns" worked examples into a single references file (e.g. references/patterns.md) and keep a one-line pointer in SKILL.md, shortening the always-loaded overview.

DimensionReasoningScore

Conciseness

The body mostly delivers usable templates rather than explaining things Claude already knows, but it could be tightened: the "Quick Reference" and "The Bottom Line" sections restate earlier content, "When to Use" duplicates the frontmatter trigger, and option template blocks ("[Same structure as Option 1]") repeat verbatim. This matches anchor 3 ("Mostly efficient but includes some unnecessary explanation or could be tightened") rather than 2, whose "several unnecessary explanations" the template payload doesn't warrant.

3 / 5

Actionability

Concrete copy-paste presentation templates, hard rules ("Weights must total 100%", "Limit to 2-4 options including the status quo"), and three worked patterns give mostly executable guidance for an instruction-only skill. It stops short of anchor 5 because the scoring tables remain placeholders — there is no fully worked example with actual raw and weighted numbers to imitate.

4 / 5

Workflow Clarity

Five phases are clearly sequenced with numbered steps and process checkpoints (criteria and weights fixed before scoring, rescore on any revision, "Choose the recommendation only after this analysis"), matching anchor 4's "clear sequence with most checkpoints present". It is not 5 because there are no explicit error-recovery feedback loops beyond the post-choice deep-dive path.

4 / 5

Progressive Disclosure

With no bundle files, the single SKILL.md is well organized into scannable sections with no nested or buried references, matching anchor 4 ("Good structure; most content is appropriately placed"). It is not 5 because at ~500 lines everything is inlined — the worked patterns and full presentation template would fit naturally in separate reference files.

4 / 5

Total

15

/

20

Passed

Description

62%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.

The description is serviceable: it states a clear capability and an explicit use-when clause with a distinct decision-support niche. Its weaknesses are thin trigger-term coverage (one phrasing where users would say "options", "alternatives", or "help me decide") and a single-action capability statement rather than a fuller inventory of what the skill does.

Suggestions

Add natural trigger phrases to the description, e.g. "Use when the user asks for options, alternatives, or help deciding between approaches" — these are the phrasings users actually say.

Enumerate the concrete actions the skill performs (generate 2-4 options including the status quo, score them against weighted criteria, present a comparison, recommend with reasoning) instead of the single "present options with trade-offs" action.

Add a brief disambiguation clause (e.g. "not for general research or implementation") to sharpen the boundary with related research/implementation skills.

DimensionReasoningScore

Specificity

"Present options with trade-offs" names the decision-support domain with one concrete action, but coverage is not comprehensive — generating options, weighted scoring, and reasoned recommendation are absent. It matches anchor 3 ("Names domain and 1-2 concrete actions, but not comprehensive") better than 4, which requires several specific listed actions.

3 / 5

Completeness

It explicitly answers both what ("Present options with trade-offs for informed decision-making") and when ("use when choosing between approaches"), matching anchor 4. It is not 5 because the when-clause is a single generic condition rather than concrete trigger phrases a user would say.

4 / 5

Trigger Term Quality

The only trigger phrasing is "use when choosing between approaches", which is relevant but misses the natural variations users actually say ("what are my options", "help me decide", "show me alternatives"). This fits anchor 3 ("Some relevant keywords but missing common variations or synonyms") rather than 4's "good keyword coverage".

3 / 5

Distinctiveness Conflict Risk

Options presentation with trade-offs is a distinct niche with only minor overlap risk against closely related planning or research skills, matching anchor 4 ("Mostly distinct; minor overlap risk"). It is not 5 because the description itself gives no disambiguating contrast with those related skills.

4 / 5

Total

14

/

20

Passed

Validation

87%

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

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (528 lines); consider splitting into references/ and linking

Warning

frontmatter_unknown_keys

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

Warning

Total

14

/

16

Passed

Repository

nyldn/claude-octopus

Path

.claude/skills/skill-decision-support/SKILL.md

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.