shopping
Skill0 starsChanged 6 days agoMITView on GitHub
Research and compare products before purchase using current prices, exact-model specifications, seller terms, and reviews from across the wider web, not only the webshop being browsed. Use when asked what to buy, whether a product is good, to compare products or listings, find the best value or deal, validate retailer claims, assess reliability and owner experience, or investigate an EAN, GTIN, UPC, SKU, manufacturer part number, or exact product ID. Browse by default because products, prices, availability, reviews, recalls, and policies change. Do not execute a purchase without explicit user authorization.
9 other projects use a version of this.
Adopted by
Most recently taken up by
- ai-search-guru/getcito-worlds-first-open-source-aio-aeo-or-geo-tooltheir own version, first seen Nov 8, 2026
- gokite-ai/passport-skillstheir own version, first seen Nov 8, 2026
- codewhale-hq/codewhale-plugin-marketplacetheir own version, first seen Nov 8, 2026
- ansvisor/ansvisortheir own version, first seen Nov 1, 2026
- obra/muse-skillstheir own version, first seen Oct 13, 2026
- sneakers-the-rat/muse-skillstheir own version, first seen Oct 13, 2026
Used with
Projects with it also use generate_podcast, muse_db and 5 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
jacobwellSkillgenerate_podcast
Compose and deliver audio content: a podcast episode, briefing, or narrated summary, with one or more voices, as an MP3. For reading supplied text aloud verbatim, use tts.
Also in 3 projects that use this
jacobwellSkillmuse_db
Inspect database-backed Muse records for diagnosis and cross-table tracing when purpose-built product tools do not expose the needed state.
Also in 3 projects that use this
ourinesSkillforget
Delete saved knowledge from ~/.claude/learnings/ and optionally clean up knowledge graph.
Also in 4 projects that use this
SentrySkilltts
Generates spoken narration with Gemini TTS through Vercel AI Gateway. Use for text-to-speech, audio samples, voiceovers, or speaking as Junior with the reusable Junior voice. Do not use for transcription, voice cloning, music generation, or rendering a video without a narration request.
Also in 4 projects that use this
QuixiAISkillspotify
Search Spotify, inspect current playback and devices, and control playback with explicit approval
Also in 3 projects that use this
refly-aiSkillgmail
Integrate with Gmail for email management and automation. Use when you need to: (1) send and compose emails with attachments, (2) read and search emails by criteria, (3) manage drafts and email labels, or (4) reply to email threads and conversations.
Also in 3 projects that use this
- +1 more from jacobwell
Other versions9 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 9
- ai-search-guru/getcito-worlds-first-open-source-aio-aeo-or-geo-tool★ 432same name
- ansvisor/ansvisor★ 233same name
- sneakers-the-rat/muse-skills★ 24same name
- FoneClaw-AI/foneclaw-android★ 21same name
- obra/muse-skills★ 20same name
- jacobwell/muse-skills★ 8same name
- codewhale-hq/codewhale-plugin-marketplace★ 5same name
- gokite-ai/passport-skills★ 2same name
- lstmemery/skills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository25 other files it gives its agents.
- batch-issuesSkill
- batch-planSkill
- champion-challengerSkill
- coding-guidelinesSkill
- convert-documentsSkill
- convert-mediaSkill
- create-pull-requestSkill
- dockerfileSkill
- email-campaignSkill
- git-commitSkill
- github-actionsSkill
- github-issueSkill
- merge-pull-requestSkill
- prod-huntSkill
- programming-goSkill
- programming-pythonSkill
- programming-rustSkill
- programming-typescriptSkill
- pr-stewardSkill
- pull-requestSkill
- refactor-debts-and-smellsSkill
- ruthless-criticSkill
- security-invariantsSkill
- squash-pull-requestSkill
- support-ticketSkill
The file
We split this skill into the rules it gives an agent
9 rules. 0 are common, 9 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 9 edited versions we read keep these.
9
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
- Distinctive: line 16
Ask one narrow question when an unresolved answer would materially change the candidates.
- Distinctive: line 21
When the user supplies an EAN, GTIN, UPC, ISBN, SKU, manufacturer part number, model number, or similarly specific identifier, that exact …
- Distinctive: line 23
Search the identifier verbatim, including punctuation, and determine whether it is a global identifier, manufacturer identifier, or …
- Distinctive: line 24
Verify it against the manufacturer or another authoritative catalog and establish the exact product name, variant, dimensions, region, …
- Distinctive: line 46
Prefer reviewers that show test methods, measurements, comparison sets, sample limitations, update dates, and conflicts or affiliate …
- Distinctive: line 47
Use owner reports for recurring durability, usability, support, and compatibility patterns.
- Distinctive: line 49
Treat marketplaces and affiliate deal pages cautiously for identity, authenticity, availability, and price.
- Distinctive: line 51
Never compare aggregate star ratings across sites as if they used equivalent populations or moderation.
- Distinctive: line 84
Do not add items to a cart, create an account, expose personal details, contact a seller, or complete a purchase unless the user explicitly …
“Common” is measured: kept by at least 6 in 10 of the 9 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.
Files
Shopping
Recommend the best fit for the user's needs, not the loudest marketing or the highest storefront rating. A retailer page is one offer from one interested party, never sufficient evidence of product quality.
Establish the Buying Brief
- Before comparing products, establish the intended outcome. When a category serves materially different goals, ask what the user will do with it: a dark rum for sipping neat, standing out in a drink, blending into a drink, cooking, or gifting can each favor a different rum.
- Turn that goal into category-specific selection criteria: product category, use case, budget, location and currency, deadline, and any retailer or condition constraints.
- Separate non-negotiable requirements from preferences, including compatibility, dimensions, accessibility, repairability, privacy, ongoing costs, and expected service life when relevant.
- Ask one narrow question when an unresolved answer would materially change the candidates; otherwise state assumptions and continue.
- Identify the exact model, generation, year, size, region, configuration, and SKU. Do not merge evidence from similar names or materially different variants.
Resolve Exact Identifiers First
When the user supplies an EAN, GTIN, UPC, ISBN, SKU, manufacturer part number, model number, or similarly specific identifier, that exact product is the primary research subject.
- Search the identifier verbatim, including punctuation, and determine whether it is a global identifier, manufacturer identifier, or retailer-specific SKU.
- Verify it against the manufacturer or another authoritative catalog and establish the exact product name, variant, dimensions, region, generation, and package contents. Do not accept a search engine's substituted or near-match result.
- Research that exact product's specifications, offers, reviews, known problems, and suitability before any alternative:
De Buyer 5680.28is that specific 28 cm model, not cookware generally or the whole Mineral B range. - Label model-family or neighboring-size evidence as indirect; attribute it to the exact product only when the source explicitly covers that identifier or confirmed variant.
- Broaden to similar products only after presenting the exact product assessment, when the identifier cannot be resolved, or when the user asks for comparisons or alternatives, and say why.
Research Beyond the Webshop
Browse the wider web for every recommendation or quality assessment, even when the user supplies a retailer link or is already on a specific site. Use the web search and page-fetch tools you have; without any, say so, give no prices, availability, or review counts, and stop at the buying brief.
For each serious candidate, seek these independent evidence classes when available:
- the manufacturer for specifications, compatibility, warranty, manuals, and support lifecycle;
- independent editorial or laboratory reviews that disclose methods and test the properties in the buying brief;
- owner feedback outside the current webshop, preferably from more than one other retailer, specialist forum, community, or long-term ownership source;
- regulator, recall, certification, repairability, and support records when safety or longevity matters;
- current offers from at least two reputable sellers for price, availability, delivery, warranty, and returns.
Search the exact model identifier with review, long term, problems, failure, returns, support, the user's key use case, and complaint language found during research. If the evidence does not span multiple source classes, say so and lower confidence rather than falling back to the current webshop's reviews.
Evaluate Sources by What They Can Prove
- Manufacturer sources prove specifications and policies, not impartial verdicts.
- Prefer reviewers that show test methods, measurements, comparison sets, sample limitations, update dates, and conflicts or affiliate relationships.
- Use owner reports for recurring durability, usability, support, and compatibility patterns; an individual report is an anecdote until corroborated.
- Retailer ratings are directional only. Inspect review count, distribution, recency, variant mixing, verified-purchase rules, incentives, suspicious repetition, and whether reviews concern the product or the seller.
- Treat marketplaces and affiliate deal pages cautiously for identity, authenticity, availability, and price; commission-driven rankings are not product evidence.
Never compare aggregate star ratings across sites as if they used equivalent populations or moderation. Never infer a defect rate from voluntary reviews without a sound denominator.
Synthesize the Review Evidence
- Extract recurring strengths and complaints tied to the user's priorities.
- Distinguish widespread patterns from isolated incidents, and first impressions from long-term ownership.
- Compare publication dates and firmware, revision, or manufacturing changes that may explain disagreement.
- Separate product problems from shipping damage, counterfeit inventory, seller service, incorrect setup, and incompatible use.
- Surface contradictions among professional tests, owner experience, and retailer reviews, and say which evidence is more relevant and why.
- Quantify only what the inspected sources support. Do not invent counts, consensus, failure rates, or sentiment scores.
For products with meaningful safety, health, privacy, or financial risk, prioritize current official warnings, recalls, certifications, and primary evidence; reviews do not replace professional or regulatory guidance.
Compare the Complete Offer
Compare the delivered price, taxes, shipping, seller identity, stock status, included accessories, regional compatibility, warranty provider, return window, restocking fees, subscriptions, consumables, energy use, repair costs, and likely resale value when material. Distinguish a good product, a good listing, and a trustworthy seller.
Timestamp volatile findings such as price and availability. Link directly to the supporting product, policy, review, or recall page, beside the claim it supports.
Deliver a Decision
Present a compact comparison containing:
- exact product and variant;
- current delivered price and seller;
- fit against the user's non-negotiables;
- cross-web review consensus and important disagreements;
- recurring strengths, problems, and long-term ownership signals;
- warranty, returns, support, and ongoing-cost differences;
- evidence confidence and important unknowns.
Give a recommendation, a runner-up, and the reason to choose each when the evidence supports them. State when waiting, buying used or refurbished, choosing a cheaper model, or buying nothing is the better decision. Do not claim a universal "best" when the result depends on priorities.
Do not add items to a cart, create an account, expose personal details, contact a seller, or complete a purchase unless the user explicitly asks. Before an irreversible order, show the exact product, seller, condition, quantity, delivered total, and return terms and obtain confirmation.
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
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.

