should-i-buylisted

Helps the user decide on a purchase by taking the product links they're considering, asking a couple of sharp clarifying questions about their needs and circumstances, then opening each link in real Chrome via the Claude-in-Chrome extension to extract price, specs, ratings, reviews, return policy, and shipping. Produces a modern 2026 HTML report with a side-by-side comparison, pros/cons per option, an external-review pulse-check, and a clear verdict (buy / wait / pick X over Y / skip). Saves each decision session to its own folder. Learns from thumbs-up/down feedback — brand, budget style, deal-breakers, and past regrets personalize future verdicts. Use when the user pastes one or more product URLs and wants a second opinion before buying, wants a comparison between links they already shortlisted, or asks "should I buy this / which one should I get?".
mostafa-drz/claude-skills · ★ 4 · AI & Automation · score 76

Install: claude install-skill mostafa-drz/claude-skills

## Preferences _On startup, use Read to load `~/.claude/skills/should-i-buy/preferences.md`. If missing, treat as first-run (see First-time detection below)._ Defaults when no preferences exist: - `output-root`: `~/Desktop/should-i-buy/` (confirmed on first run) - `currency`: `USD` - `budget-style`: `value` (value / premium / bargain — shapes the verdict weighting) - `tone`: `friendly-cli` (terse, direct, warm — like a friend who actually knows the category) - `open-report`: `true` (auto-open the HTML report when done) - `verdict-style`: `decisive` (decisive / balanced — decisive means I pick one and say why; balanced lays out the trade-off) _Also load `~/.claude/skills/should-i-buy/feedback-journal.md` if present — it contains thumbs-up/down on past verdicts. Summarize its signal (e.g., "regretted buying X for Y reason", "consistently prefers refurb over new") and carry that into the current verdict._ ## Context _On startup, use Bash to detect: today's date (`date +%Y-%m-%d`), and whether the output-root folder exists (`ls` or absence). Do not fetch the shared URLs yet — that happens after we've clarified the ask._ ## Command routing Check `$ARGUMENTS`: - `help` → show help, stop - `config` → run config flow, stop - `reset` → delete preferences + feedback journal, confirm, stop - `feedback` → collect thumbs-up/down on the most recent decision (see Feedback section), stop - `history` → list recent decision folders with titles and dates, stop - `setup` or `preflight` →