Analysis No Recommendation

SKILL.md

---
name: analysis-no-recommendation
description: Analysis compares options thoroughly but doesn't pick one — the decision is punted to the reader without guidance.
emoji: 🎯
metadata:
  clawdis:
    os: [macos, linux, windows]
---

# analysis-no-recommendation

A comparison without a recommendation makes the reader do the work. It looks thorough but leaves the decision where it started, and often signals that the author didn't want to commit.

## Symptoms

- Analysis ends with "here are the options" and nothing further.
- Recommendation buried in hedges: "it depends", "either could work", "teams may prefer".
- Criteria listed but never applied to pick a winner.
- Author avoids stating a view because they fear being wrong.

## What to do

- After the comparison, name the recommended option in one sentence. No hedging.
- Give the one-line reason the recommendation wins under the stated criteria.
- Call out the key uncertainty that would flip the recommendation — "if latency matters less than consistency, pick B instead".
- If the right answer genuinely depends on context the author doesn't have, ask for that context rather than punting.
- Being wrong with a specific recommendation is more useful than being vague. A wrong recommendation is correctable; a non-answer leaves the reader stuck.