agentleFS
ccgargantuaccgargantua/gars-claude-skills/skills/product-research/SKILL.md

product-research

Skill1 starsChanged 2 months agoMITView on GitHub

Research products to help the user decide what to buy. Use when the user wants recommendations, comparisons, or help choosing between products, for personal or work purchases, at any budget. Trigger on requests like 'what should I buy', 'help me find a', 'recommend a', 'which is better', or any purchase decision, even if no budget or use case has been given yet.

14 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 13 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Never rely on training data alone for prices, specs, or "best in class" picks.

    line 8
  2. Distinctive:

    If budget, use case, or a hard requirement is missing, ask the user rather than assuming it.

    line 9
  3. Distinctive:

    Every current guide agrees on one thing regardless of brand: prioritize RAM over CPU speed or screen resolution for coding workloads, since …

    line 46

“Common” is measured: kept by at least 6 in 10 of the 13 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Rules

  1. Never rely on training data alone for prices, specs, or "best in class" picks. These change constantly, so verify with a search performed in this conversation before stating them as current.
  2. If budget, use case, or a hard requirement is missing, ask the user rather than assuming it.

Steps

  1. Confirm what's actually unclear before searching. Do not assume budget, use case, or personal-vs-work if the prompt doesn't say. Use the ask_user_input_v0 tool to confirm the missing pieces in one short round, for example: intended use (personal / work / gift), budget tier (low / mid / high / no limit), and any hard requirements (brand, size, compatibility, must-haves). If the prompt already answers one of these, don't ask again, just confirm the others. Skip the tool entirely if the user already gave enough detail to work with (specific budget, clear use case, named requirements) - asking anyway wastes their time.
  2. Make zero assumptions about the market. Know what in your training is stale. Product lineups, prices, and "best in class" picks change constantly, so treat any specific model, price, or spec claim as something to verify now, not recall.
  3. Search the web. Look at current buying guides, retailer listings, and expert reviews. Favor recent, independent, specific sources (reputable review sites, hands-on comparisons) over generic listicles or SEO-driven affiliate content. Cross-check prices and specs across at least two sources since prices shift and listings go stale.
  4. Narrow to a short list. Don't dump every option that exists. Pick 2-4 real candidates that fit the confirmed budget and use case, and say why each one made the cut over the alternatives.
  5. Report directly. For each candidate: what it is, current price, why it fits the stated use case and budget, and the one or two tradeoffs against the others. Be direct and brief, skip filler like "this is a great choice for anyone."
  6. State assumptions and gaps at the end. If anything wasn't confirmed (e.g. the user skipped a question, or a spec couldn't be verified), say so plainly rather than quietly filling it in.

Example

User: "I need a new laptop for work."

Claude: [Uses ask_user_input_v0 to confirm: primary work tasks (e.g. general office / creative or video work / heavy coding or dev work), budget tier (under $800 / $800-1500 / $1500+), OS preference if any]

User selects: heavy coding/dev work, $800-1500, no OS preference.

Claude: [Searches current buying guides and reviews for dev-focused laptops in that price range, cross-checks recommendations and specs across multiple sources]

For dev work in the $800-1500 range, current reviews consistently point to three real options:

Lenovo ThinkPad T14 / T16 - widely recommended across programming-laptop guides right now for its durable keyboard, mostly non-soldered components (so RAM/storage are upgradeable later), and it runs Linux well. Tradeoff: bulkier and heavier than a MacBook, and the base config often needs a RAM bump to hit 32GB.

Framework Laptop 13 - built to order, and the standout pick if repairability matters: swap ports, RAM, storage, or the mainboard yourself later instead of replacing the whole machine. Tradeoff: shorter reliability track record than Lenovo, and pricing depends heavily on the configuration chosen.

Apple MacBook Pro (M-series) - rated as the top overall pick in more than one current comparison for raw performance and display quality, if macOS is acceptable. Tradeoff: sits at the top of this budget range and RAM can't be upgraded after purchase, so buy more than you think you need up front.

Every current guide agrees on one thing regardless of brand: prioritize RAM over CPU speed or screen resolution for coding workloads, since IDE plus browser plus containers plus AI tooling running at once is what actually strains a machine day to day.

What I didn't confirm: exact current prices and configurations change often enough that I'd verify the specific model and RAM configuration against the retailer at the time of purchase, and whether discrete graphics matters (e.g. for local ML work) - let me know and I can narrow further.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.