should-i-buy
SolidHelps 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?".
Install
Quality Score: 83/100
Skill Content
Details
- Author
- mostafa-drz
- Repository
- mostafa-drz/claude-skills
- Created
- 7 months ago
- Last Updated
- yesterday
- Language
- HTML
- License
- MIT
Similar Skills
Semantically similar based on skill content — not just same category
shop-research
Researches products across Amazon, Google Shopping, and relevant specialty sites using the Claude-in-Chrome browser extension. Finds candidates matching user-specified criteria (gift, gadget, gear, home goods, etc.), captures screenshots and key data per candidate, then generates a modern 2026 HTML report with pros/cons, review highlights, metrics, and recommendations. Saves each research session to its own semantically-named folder. Learns from user feedback over time — preferences, favored brands, budget style, and thumbs-up/down on past picks personalize future searches. Use when the user wants to shop for something, compare products, find a gift, or research purchases before buying.
ui-test
Runs UI tests described in plain English by driving real Chrome via the Claude-in-Chrome extension. Covers end-to-end flows (clicks, forms, assertions), visual checks (screenshot + optional baseline diff), accessibility (axe-core), performance (Web Vitals + light Lighthouse-style metrics), and an interactive --debug mode that tails console + network and surfaces issues without needing explicit assertions. Accepts inline descriptions or test files in `./tests/ui/*.md`. Per-run folders contain artifacts (screenshots, console, network, axe report, perf metrics) plus a single-file 2026-aesthetic HTML report with a verdict-forward layout. Learns from per-run feedback — false-positive categories, screenshot strategy, severity floors, and per-project baselines personalize future runs. Use when the user wants to verify a UI flow, screenshot a regression, audit accessibility, profile a page, or debug something visibly broken in a real browser session.
before-you-install
Vets a tool before you sign up for it and ends on a call rather than a summary. Trigger whenever the user says "should I use", "is this tool safe", "before I install", "what is the catch", "is it worth paying for", "check this tool", "review this app", "what does their privacy policy actually say", "what are people saying about", "how does this free tool make money", or pastes a product page, pricing page, privacy policy or terms and asks what to make of it. Also trigger when they are choosing between two tools they might pay for, or when they have already installed something and want to know what they agreed to. It reads the policy and terms for what they permit, finds documented complaints and controversies, checks permissions and business model, and finishes on install, install with conditions, or do not install. Runs with or without web access and states which. Use a vendor-review or procurement skill for a company purchase with a buying committee; this one is for one person with a credit card.