skill-decision-support

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

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

Quality

Content

65%Weight 40%Scale 1-3

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

The body is highly actionable with concrete templates and examples and a clear phased workflow, but it is verbose for a presentation skill, lacks explicit validation checkpoints, and keeps all content in one monolithic file with no progressive-disclosure structure.

Suggestions

Collapse the near-duplicate Phase 3 and Phase 4 presentation templates into a single canonical template, and trim the Common Patterns to one fully-worked example plus a pointer, to reduce redundancy.

Add explicit decision/validation gates between phases (e.g., 'Before presenting: confirm each option meets stated constraints; drop any that don't') so checkpoints are not merely implicit.

Move the detailed presentation templates and the worked Common Patterns into reference files (e.g., references/templates.md, references/examples.md) referenced one level deep, leaving SKILL.md as a lean overview.

Dimension	Reasoning	Score
Conciseness	The ~440-line body is mostly efficient and avoids explaining concepts Claude already knows, but the Phase 3 and Phase 4 templates near-duplicate each other and the three Common Patterns re-demonstrate the same format, so it could be meaningfully tightened rather than earning the lean level-3.	2 / 3
Actionability	It provides copy-paste-ready presentation templates (option blocks with pros/cons/effort/risk, comparison tables, recommendation structure) backed by concrete filled examples (JWT auth fix, Node-cache/Redis/CDN caching, TypeScript vs JavaScript), which is fully actionable guidance for an instruction-only skill.	3 / 3
Workflow Clarity	The five phases are clearly sequenced with numbered steps and supporting checklists (Red Flags, Quick Reference), but there are no explicit validation/decision checkpoints beyond implicit branching, matching the level-2 'sequence present but checkpoints missing or implicit' anchor.	2 / 3
Progressive Disclosure	The body is a single monolithic file with no references/scripts/assets and no signaled navigation; it is well-sectioned but at >50 lines contains template and example content that could be split out, fitting the 'some structure but content that should be separate is inline' anchor rather than a level-3 split structure.	2 / 3
	Total	9 / 12 Passed

Description

67%Weight 40%Scale 1-3

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 what and when with an explicit 'use when' clause, but its action list and trigger-term coverage are only partial and the niche is not sharply disambiguated from adjacent skills.

Suggestions

Expand the action list with more concrete verbs (e.g., 'Generate 2-4 options, compare trade-offs, recommend with reasoning') to lift specificity from 2 to 3.

Add the natural phrasings users actually say — "what are my options", "help me decide", "show me alternatives" — to broaden trigger-term coverage.

Sharpen distinctiveness by contrasting with neighbors in the description itself (e.g., 'not for open-ended research or implementation'), reducing overlap with planning/research skills.

Dimension	Reasoning	Score
Specificity	Names the domain and a couple of actions ("Present options with trade-offs", "informed decision-making") but does not list multiple concrete capabilities; it sits at the 'names domain and some actions, but not comprehensive' anchor rather than the multi-action level 3.	2 / 3
Completeness	It answers both what ("Present options with trade-offs for informed decision-making") and when via an explicit trigger clause ("use when choosing between approaches"), satisfying the level-3 'clearly answers both what AND when with explicit triggers' anchor.	3 / 3
Trigger Term Quality	"options", "trade-offs", and "choosing between approaches" are reasonably natural, but common phrasings users actually say ("help me decide", "what are my options", "alternatives") are absent, so coverage is partial rather than comprehensive.	2 / 3
Distinctiveness Conflict Risk	The options/decision niche is somewhat specific, yet "decision-making" and "choosing between approaches" are broad enough to overlap with general planning or research skills, matching the 'somewhat specific but could still overlap' anchor rather than a clearly conflict-free niche.	2 / 3
	Total	9 / 12 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: nyldn/claude-octopus
Path: .claude/skills/skill-decision-support/SKILL.md
Commit: 9f39f0c

Reviewed: 7 days ago

Table of Contents

Discovery Implementation Validation

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.