CtrlK
BlogDocsLog inGet started
Tessl Logo

skill-decision-support

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

52

Quality

59%

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

56%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 content teaches a well-sequenced, actionable options-presentation process with strong worked examples, and its workflow clarity is high. Its main weaknesses are heavy template duplication inflating token cost and a monolithic single-file structure that inlines content a reference file should carry.

Suggestions

Merge the Phase 3 trade-off template and Phase 4 presentation template into a single option format to eliminate the duplicated pros/cons structure, and cut the "Bottom Line" section entirely.

Move the three worked Common Patterns examples into a references/patterns.md file and link to it from a short section, keeping SKILL.md as a lean overview.

Add an explicit recovery step in Phase 5 for when the user rejects all options (e.g., loop back to generate new options or offer the escape hatch actions).

DimensionReasoningScore

Conciseness

The body is noticeably verbose at ~440 lines: the pros/cons option template appears nearly identically in Phase 3 and Phase 4, the three worked patterns demonstrate the same structure a third time, and sections like "The Bottom Line" ("Otherwise → Confusion + Poor decisions + Regret") and the Red Flags table pad beyond what Claude doesn't already know. Several sections could be cut or merged without losing guidance, matching the noticeably-verbose anchor rather than the mostly-efficient one.

2 / 5

Actionability

Every phase has a concrete fill-in template, and three fully worked examples (auth fix, caching, TypeScript vs JavaScript) cover the common cases. As an instruction-only skill the absence of code is appropriate per the rubric's scoring notes; minor gaps remain in that templates still leave placeholders undefined in a few spots, keeping it below the fully copy-paste-ready anchor.

4 / 5

Workflow Clarity

A clear five-phase sequence (understand context → generate options → analyze trade-offs → present → support choice) is stated as the core principle and elaborated per phase, with checkpoint logic such as AskUserQuestion for requirements and don't-generate rules. This is not a destructive or batch operation so no validation cap applies; it falls short of a 5 only because there is no explicit recovery loop when the user rejects all options (the escape hatch partially covers it).

4 / 5

Progressive Disclosure

The skill is a single 440-line file with no bundle (references/, scripts/, assets/ are absent). Section headers and a Quick Reference table give it reasonable structure, but the worked pattern examples and duplicated presentation templates are inlined content that clearly belongs in a separate reference file at this length, matching the some-structure-but-content-should-be-separate anchor.

3 / 5

Total

13

/

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.

A solid description that clearly states what the skill does and when to use it, with a distinctive decision-support niche. Its main weaknesses are thin action coverage and missing natural trigger synonyms that users would actually say.

Suggestions

Fold one or two concrete trigger phrases into the description itself (e.g., "use when the user asks for options, alternatives, or help deciding between approaches") rather than relying solely on the separate trigger field.

Broaden the action list slightly to cover the full workflow — e.g., "present options with trade-offs, compare approaches, and recommend one with reasoning".

DimensionReasoningScore

Specificity

The description names the domain (decision support) and one concrete action — "Present options with trade-offs" — but coverage is not comprehensive; it omits comparing alternatives, recommending, and supporting the chosen path. It matches the anchor for naming a domain with 1-2 concrete actions, not the several-specific-actions level above.

3 / 5

Completeness

Both parts are present: the what ("Present options with trade-offs for informed decision-making") and the when ("use when choosing between approaches"). The when clause lacks concrete trigger phrases, matching the anchor where both exist but the when could be more explicit; a 5 requires explicit trigger phrases like "user mentions X".

4 / 5

Trigger Term Quality

Natural keywords like "options", "trade-offs", and "choosing between approaches" are present, but common user phrasings such as "alternatives", "help me decide", or "what are my options" are absent from the description (they appear only in the separate trigger field, which this rubric does not evaluate). This fits the anchor for some relevant keywords missing common variations.

3 / 5

Distinctiveness Conflict Risk

Options presentation with trade-offs is a clear niche with a distinct trigger that is unlikely to fire for unrelated skills, though "choosing between approaches" has minor overlap with general planning/advice skills. This matches the mostly-distinct anchor rather than the fully minimal-conflict anchor.

4 / 5

Total

14

/

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.

Validation — 15 / 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
nyldn/claude-octopus
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.