TweakIdea — скилл

---
name: tweakidea
description: "Use when a founder wants to evaluate a startup idea or problem, improve or compare idea evaluations, or mine Hacker News for product opportunities. Runs a 14-dimension weighted scorecard with assumption tracking, generates small/medium/big idea tweaks, diffs runs, browses and analyzes HN threads, and lists, opens, or shares artifacts saved under ~/.tweakidea/."
license: MIT
compatibility: "Works in any Agent Skills client. evaluate needs subagents plus web search and web fetch; the other commands run inline. Requires uv and network access; share also needs the GitHub CLI (gh). Tuned and tested on Claude Code with Sonnet and Opus."
allowed-tools: Read Write Bash Glob Agent AskUserQuestion
---

TweakIdea helps founders make better decisions: evaluate whether a problem is worth solving, or discover which problems are emerging from technology shifts. Be an honest second opinion, not a cheerleader.

## Setup

1. **SKILL_DIR** is the directory that contains this SKILL.md (the runtime reports it as the skill's base directory). If no base directory is reported, use the first of `$(pwd)/.claude/skills/tweakidea`, `$HOME/.claude/skills/tweakidea`, `$(pwd)/.agents/skills/tweakidea`, or `$HOME/.agents/skills/tweakidea` that contains `SKILL.md`. Every `{SKILL_DIR}` path in this skill and its references resolves against it.
2. **Runtime:** read [references/runtime.md](references/runtime.md) and map each capability it lists (`ask-user`, `spawn-subagent`, `web-search`, `read-file`, and the rest) and each model tier to what your runtime provides. The references name capabilities, not tools.
3. **HOME_DIR** is the output of `echo "$HOME"`. All user data lives under `{HOME_DIR}/.tweakidea/`.
4. Python helpers in `{SKILL_DIR}/scripts/` run through `uv run`. If a command needs them and `uv` is missing, tell the user to install it (`brew install uv` or `curl -LsSf https://astral.sh/uv/install.sh | sh`) and stop.

## Routing

The invocation arguments are:

$ARGUMENTS

If the line above is still an unsubstituted placeholder (a dollar sign followed by the word ARGUMENTS), your runtime does not substitute arguments: use the text after the skill name in the user's invoking message instead.

Split them into **COMMAND** (the first word) and **ARGS** (everything after it). Command references use `ARGS` wherever they need the user's input.

- **No arguments:** show the Commands table below and ask which command to run (`ask-user` with `evaluate`, `improve`, `browse-hn`, `list`; free text covers the rest). Never auto-run a command.
- **First word is a command name:** read that command's reference and follow it exactly, with ARGS as its input.
- **Anything else:** treat the full argument text as an idea and run `evaluate` with it as ARGS.

## Commands

| Command | Arguments | What it does | Reference |
|---|---|---|---|
| `evaluate` | idea text, file path, or empty | 14 independent evaluators produce a weighted scorecard with assumption tracking and an HTML/markdown report | [references/commands/evaluate.md](references/commands/evaluate.md) |
| `improve` | run timestamp, prefix, or `latest` | Three concrete idea tweaks (small reframe, medium reshape, big reimagine) grounded in the scoring rubrics | [references/commands/improve.md](references/commands/improve.md) |
| `diff` | two runs (timestamps, prefixes, or `latest`) | Side-by-side comparison of two runs: score deltas, potential shifts, per-dimension movers | [references/commands/diff.md](references/commands/diff.md) |
| `browse-hn` | `[topic] [today\|week\|month\|all]` | Search HN via Algolia and rank threads worth feeding into `analyze-hn-post` | [references/commands/browse-hn.md](references/commands/browse-hn.md) |
| `analyze-hn-post` | HN URL or item id | Analyze one HN discussion for technology shifts and product opportunities | [references/commands/analyze-hn-post.md](references/commands/analyze-hn-post.md) |