Deal hunting

Skills that watch marketplaces and flag underpriced listings before anyone else sees them.

9 of 9 skills

type

Open Box Hunter
Hunts open-box, refurbished, and clearance deals on the exact product you name, and ranks them by real savings over new.
skillinstructionsworkflowprice-comparisoncondition-checklist
by Muse Skills editors · Written for this directory
ViewInstall the "Open Box Hunter" skill. Its full source is below. Create it at ~/workspace/skills/open-box-hunter/SKILL.md following skill-creator conventions (name and description frontmatter; Purpose, Workflow, Output Contract, Operating Rules sections). Then confirm it is installed and tell me the trigger phrases. --- SOURCE --- --- name: open-box-hunter description: Finds open-box, refurbished, and clearance deals on a product you name: compares retailer prices, checks condition grades, and ranks offers by real savings. Trigger phrases: "find an open-box deal on", "cheapest refurbished", "clearance price for", "open box deals", "refurbished alternative". --- # Purpose Do one narrow job: when you already know the product you want but would rather not pay full retail, find the best discounted way to buy it. The skill searches open-box listings, certified refurbished stock, and clearance markdowns across major retailers, compares the effective price (after shipping, tax, and warranty differences), and ranks offers by true savings against the current new price. It never hides what is missing: every verdict shows condition, accessories, return window, and warranty side by side, so a cheap price with a 14-day return and no charger does not win by accident. # Workflow 1. Collect the inputs: the exact product name or model number, your acceptable condition grades (open-box excellent, good, or fair; certified refurbished; store clearance), your max budget, and whether accessories and manuals must be intact. 2. Establish the baseline: find the current new price from a major retailer, not the list price, so savings are measured against what you would actually pay today. 3. Build the candidate list: check the big open-box sources (Best Buy open-box, Amazon Warehouse, manufacturer refurbished stores, manufacturer clearance pages), plus reputable general marketplaces, for the exact model. 4. For each candidate record the price, shipping cost, condition grade, what is included or missing, the return window, and the warranty status. 5. Compute true savings per offer versus the new-price baseline, then rank the offers. Flag any deal where missing accessories or a short return window erase the apparent discount. 6. Present the ranked list with links and a one-line verdict on each: worth it, borderline, or skip. Ask about budget and condition limits before starting if the user did not give them. # Output Contract - The current new price used as the baseline, with its source - A ranked list of offers: price, shipping, condition grade, included and missing items, return window, warranty - True savings per offer versus new, in dollars and percent - A one-line verdict on each offer: worth it, borderline, or skip, with the reason - A note on any candidate that could not be verified with a live listing # Operating Rules - Always compare against the live new price, not the list price, so savings are real. - Never hide missing accessories, short return windows, or warranty gaps in a verdict. Show them next to the price. - Never recommend an offer you cannot verify with a live listing; say which offers you could not check. - Never push the buyer below the minimum condition grade they set. - Never share the buyer's personal or location data in any search you run.
Auction Bid Calculator
Sets a hard bid ceiling for an auction lot after fees, tax, shipping, and your margin.
Tested in Museskillinstructionsworkflowcalculator
by Muse Skills editors · Written for this directory
ViewInstall the "Auction Bid Calculator" skill. Its full source is below. Create it at ~/workspace/skills/auction-bid-calculator/SKILL.md following skill-creator conventions (name and description frontmatter; Purpose, Workflow, Output Contract, Operating Rules sections). Then confirm it is installed and tell me the trigger phrases. --- SOURCE --- --- name: auction-bid-calculator description: Computes your maximum bid for an estate or online auction lot, accounting for buyer premium, sales tax, shipping, and your target margin. Trigger phrases: "what should I bid", "auction bid ceiling", "is this lot worth bidding on". --- # Purpose Set a hard ceiling for an auction lot before the bidding starts, so the fees and taxes do not turn a win into a loss. # Workflow 1. Read the lot details: item description, current bid, estimate, and the auction's buyer premium percentage and payment terms. 2. Read the sales tax rate for the auction location and the shipping cost if it is not local pickup. 3. Read the target: the item's conservative resale value and the margin the user wants to keep. 4. Compute the ceiling: the highest hammer price such that the hammer price plus buyer premium plus sales tax plus shipping plus any other fees stays at or below the target value after the margin. 5. Show the math line by line, then the ceiling as one bold number. 6. Optionally produce a bid plan: the opening bid and the last comfortable step below the ceiling. # Output Contract - One-line verdict: the maximum hammer price to bid, plus the all-in cost at that price. - A short math breakdown: hammer price, buyer premium, sales tax, shipping, other fees, total. - Target resale value and the dollar margin the plan protects. - If the current bid already exceeds the ceiling, say so in the first sentence and do not propose higher bids. # Operating Rules - Never guess the buyer premium, tax rate, or shipping cost; ask for each value if the user has not supplied it, and mark any assumption plainly when the user approves a default. - Never recommend bidding above the computed ceiling. - Never fabricate resale comps; use comps the user confirms or recent sold data, and state the low end of the range. - Never place bids or access an auction account; this is math and planning only.
Auction Ending Alert
Watches your saved auctions; pings before close with your max bid.
Tested in Museworkflowinstructionsworkflowschedule
by Muse Skills editors · Written for this directory
ViewSet up the "Auction Ending Alert" workflow. Its full source is below. Default schedule: every 30 minutes. Ask me to confirm or change the cadence before you create the recurring job. Once I confirm, create the job. Tell me the job name and the confirmed schedule when it is set up. --- SOURCE --- name: auction-ending-alert description: Watch a list of auctions and alert before each one closes, with the current price, your max bid, and whether the deal still clears your bar. Trigger phrases: "watch these auctions", "alert me before my auctions end", "track my bids". schedule: every 30 minutes. Confirm the cadence with the user before the first scheduled run. trigger: the scheduled time, or a manual "watch these auctions" request with links. steps: 1. Ask the user for the auction links and a max bid for each. Save the watch list. 2. Each run: check the current price, bid count, and time remaining for every watched auction. 3. Alert rules: - Ending within 2 hours: send the pre-close alert. - Price already above the user's max: mark "over your max" and stop watching it unless told otherwise. - Auction ended: report the outcome (won/lost, final price) once, then drop it from the list. 4. The pre-close alert uses the Output shape. output: - Ending soon: item, time left, current price, your max bid - Deal check: current price vs. your max, one line - Over your max: listed separately, dropped from watch - Ended: outcome, one line each rules: - Read only. Never place a bid, never snipe, never contact the seller. - Max bids are the user's. Ask once per item, reuse until it ends. - One alert per auction per stage. No repeat pings. - Run only on the confirmed cadence or when asked.
Estate Sale Scout
Thursday-night scan of weekend estate sales, ranked by your categories.
Tested in Museskillinstructionsworkflowreport-format
by Muse Skills editors · Written for this directory
ViewInstall the "Estate Sale Scout" skill. Its full source is below. Create it at ~/workspace/skills/estate-sale-scout/SKILL.md following skill-creator conventions (name and description frontmatter; Purpose, Workflow, Output Contract, Operating Rules sections). Then confirm it is installed and tell me the trigger phrases. --- SOURCE --- --- name: estate-sale-scout description: Scan weekend estate-sale listings Thursday night and rank them by your collecting categories, so Friday morning you know where to go. Trigger phrases: "scout this weekend's estate sales", "any good estate sales coming up", "plan my Saturday sales route". --- # Purpose Estate sales reward the early and the informed. This skill reads the weekend's listings Thursday night and ranks them against what you actually collect, so you spend Saturday at the two sales worth your time instead of driving to six. # Workflow 1. Ask the user once for: home base (for drive time), search radius, and collecting categories in priority order (e.g. vinyl, cameras, tools, mid-century furniture). 2. On request (or Thursday evening if scheduled): pull the weekend's estate-sale listings from the main listing sites within the radius. 3. Score each sale: category matches in the listing photos or description (2 points per top-category match, 1 per lower), minus 1 point per 15 minutes of drive time over 30. 4. Report the top 5 in the Output Contract shape, with the rest as one-line honorable mentions. # Output Contract - Weekend shortlist: top 5 sales, ranked: address, day/hours, why it scored (which categories matched), drive time - Honorable mentions: one line each for the rest - Suggested route: the order to hit the top picks on Saturday morning - Slow weekends: "Nothing in your categories this week." # Operating Rules - Public listings only. Never contact organizers or RSVP. - Scores come from the listing text and photos, not from assumptions. If a listing is vague, say so instead of inflating it. - Drive time is an estimate. Name the source (maps); never present it as exact. - One scan per request or per scheduled Thursday run. No drip-feed alerts through the weekend.
Bulk Lot Evaluator
Point it at a lot listing; get a max bid and a walk-away price.
Tested in Museskillinstructionsworkflowvaluation-method
by Muse Skills editors · Written for this directory
ViewInstall the "Bulk Lot Evaluator" skill. Its full source is below. Create it at ~/workspace/skills/bulk-lot-evaluator/SKILL.md following skill-creator conventions (name and description frontmatter; Purpose, Workflow, Output Contract, Operating Rules sections). Then confirm it is installed and tell me the trigger phrases. --- SOURCE --- --- name: bulk-lot-evaluator description: Evaluate a bulk lot listing (records, games, cameras, tools) from its photos and description: per-item value estimate, a max bid, and a walk-away price. Trigger phrases: "evaluate this lot", "what's this lot worth", "should I buy this lot". --- # Purpose Decide fast whether a bulk lot is worth buying, and at what price. Built for listings where the seller doesn't know what they have: one photo, a vague description, a single asking price. # Workflow 1. Read the listing: photos, description, asking price, location. 2. Identify every item you can see or reasonably infer. Group them: clearly visible, partially visible, described-but-unseen. 3. For each clearly visible item of value, estimate a conservative resale value from recent sold comps (lowest of matches, never the average). 4. For partially visible or unseen items, assign $0 in the base case and note the upside only as speculation. 5. Add the conservative values. Apply the lot discount: multiply by 0.6 (you will not sell everything, and condition is uncertain). 6. Set the max bid at 50% of the discounted total. If the asking price exceeds the max bid, the call is "negotiate to $X" when the gap is small and "walk away" when it is not. 7. Report in the Output Contract shape. # Output Contract - Lot: listing title and link - Ask: dollar amount - Visible value: itemized conservative values, one line each - Discounted total: the 0.6-adjusted sum - Max bid: dollar amount - Walk-away: "buy" / "negotiate to $X" / "walk away", with one line of reasoning - Speculative upside: items that could add value but were not counted # Operating Rules - Never count value for items you cannot see or verify. Unseen = $0 in the base case. - Never use asking prices as comps; sold data only, low end of the range. - If the photos are too poor to identify anything of value, say so and stop. - Report only. Never contact the seller, bid, or negotiate on the user's behalf.
Deal Hunter
Watches new private-seller listings and flags the mispriced ones.
Tested in Museskillinstructionsworkflowschedule
by Muse Skills editors · Written for this directory
ViewInstall the "Deal Hunter" skill. Its full source is below. Create it at ~/workspace/skills/deal-hunter/SKILL.md following skill-creator conventions (name and description frontmatter; Purpose, Workflow, Output Contract, Operating Rules sections). Then confirm it is installed and tell me the trigger phrases. --- SOURCE --- --- name: deal-hunter description: Scan marketplace listings for brand-new, private-seller items priced well below conservative resale value. Trigger phrases: "run deal hunter", "check for underpriced listings", "scan marketplace for deals". --- # Purpose Find listings that are mispriced by a wide margin, not merely cheap. A candidate meets three conditions at the same time: the listing is new since the last run, the seller is a private party, and the ask sits well under a conservative resale value. # Workflow 1. Read the watch config: category or keyword list, target marketplaces, and area or radius. The user sets these once, and Deal Hunter reuses them until the user changes them. 2. Pull listings posted since the last successful run. Discard any listing already seen in a prior run. 3. Discard any listing from a dealer, a store account, or a seller with a storefront profile. Keep private-party listings only. 4. For each remaining listing, estimate a conservative sold value. Use recent sold or completed listings for the same item and condition, and take the lower end of that range, not the average. 5. Compute the ask as a percentage of the conservative sold value, and the upside in dollars: conservative sold value minus the ask. 6. Keep a listing only if the ask is at most 50% of the conservative sold value AND the upside is at least $40. 7. Sort the surviving candidates by upside, highest first. 8. If no candidate survives, end the run. Send nothing. 9. If at least one candidate survives, write the report in the Output Contract shape and send it. 10. Record the run timestamp and the listing IDs seen, so the next run only looks at what is new. # Output Contract A short list, one line per candidate, in this order: - Listing: title and link - Ask: dollar amount - Conservative comp: dollar amount and how it was set (for example, "lowest of 3 sold comps") - Upside: dollar amount No candidates: no message at all. This is a quiet job by design. # Operating Rules - Never message, offer on, or contact a seller. Report only. - Never place a bid, a hold, or a purchase. - Never ask the user for a marketplace login, cookie, or API key. Use the assistant's own connected browsing session. - Never treat an average or asking-price comp as the conservative value; use the low end of actual sold data. - If sold data is too thin to set a confident comp, skip the listing rather than guess. - Run only on the schedule the user confirms; do not run ad hoc without being asked.
eBay Comp Checker
Paste any item description; get a conservative resale value from real sold comps.
Tested in Museprompt packinstructionscomp-methodconfidence-rating
by Muse Skills editors · Written for this directory
ViewInstall the "eBay Comp Checker" prompt pack. Its full source is below. Save it at ~/workspace/prompts/ebay-comp-checker.md exactly as given, with the frontmatter (name and description) and the prompt body. Do not run it now. Then confirm it is saved and tell me the trigger phrases: "comp this item", "find eBay comps", "price this eBay item". --- SOURCE --- # eBay Comp Checker How to use: paste an item description with as much detail as you have: brand, model, size or variant, condition, and anything that affects value (edition, year, completeness). Ask for "comp this" any time you are staring at a listing and wondering if the price is real. Trigger phrases: "comp this item", "find eBay comps", "price this eBay item". ## The prompt You are pricing a used item from eBay sold data. Work in this order: 1. Search eBay's sold and completed listings for the closest matches: same brand and model, same size or variant, comparable condition. 2. Collect the 5 most recent matching sold prices. Ignore active listings, asking prices, and outliers more than 2x the median. 3. Set the conservative comp to the LOWEST of the matched sold prices, not the average, not the median. 4. Report in this shape: - Item: what you matched on - Sold comps: the matched prices, newest first, with dates - Conservative comp: $X (lowest of N matches) - Confidence: high / medium / low, with one line on why 5. If fewer than 3 solid matches exist, say so plainly and mark confidence low. Never pad thin data with guesses. 6. Never invent a sold listing. If you cannot find real sold data, say that instead of estimating. Rules: report only. Never contact a seller, place a bid, or suggest a listing strategy beyond the comp itself.
Garage Sale Route Planner
Friday-night sweep of yard and estate sales, mapped into a Saturday route.
Tested in Museworkflowinstructionsworkflowschedule
by Muse Skills editors · Written for this directory
ViewInstall the "Garage Sale Route Planner" workflow. Its full source is below. Create it at ~/workspace/skills/garage-sale-route-planner/SKILL.md following skill-creator conventions (name and description frontmatter; Purpose, Workflow, Output Contract, Operating Rules sections). Confirm it is installed and tell me the trigger phrases. Then, as a separate step, propose the default schedule (Friday at 19:00 local time) and wait for me to confirm or change it before you create any recurring job. --- SOURCE --- name: garage-sale-route-planner description: Friday-evening sweep of yard sales, garage sales, and estate sales near the user, scored against an interest list and mapped into a Saturday morning route. Trigger phrases: "plan my Saturday route", "find weekend sales", "plan my garage sale route". schedule: weekly, Friday at 19:00 local time (cron: 0 19 * * 5). Confirm the time with the user before the first scheduled run. trigger: the scheduled time, or a manual "plan my Saturday route" request. route_config: area, radius in miles (default 20), and interest keywords (for example: vinyl records, film cameras, tools, mid-century furniture). The user sets these once; the workflow reuses them until changed. steps: On first run, ask the user for area, radius, and interest keywords, and store them for later runs. 1. Sweep local listings for Saturday sales: Craigslist garage/yard sale section, Facebook Marketplace local sale posts, and estate-sale aggregators covering the user's area. 2. Keep sales within the radius happening Saturday morning. Drop sales with no address or no start time. 3. Score each sale on interest-keyword hits in its listing text. Sales mentioning a keyword rank above general sales. 4. Order the kept sales into a route: earliest start time first, then nearest to the previous stop. Estimate total driving miles. 5. Write the route in the Output shape and send it Friday night. If nothing scores above a general sale, say so in one line instead of sending a thin route. output: - One numbered stop per sale: start time, sale type, address, and the keyword hit that earned its place - Total driving distance for the route - One line on anything worth skipping rules: - Report only. Never contact a seller or RSVP to anything. - Never use asking prices or sale hype as a signal; keywords and proximity only. - Run only on the confirmed schedule or when asked.
Marketplace Scout
Finds flip candidates for your watchlist across Facebook, Craigslist, and eBay.
Tested in Museskillinstructionsworkflowwatchlist
by Muse Skills editors · Written for this directory
ViewInstall the "Marketplace Scout" skill. Its full source is below. Create it at ~/workspace/skills/marketplace-scout/SKILL.md following skill-creator conventions (name and description frontmatter; Purpose, Workflow, Output Contract, Operating Rules sections). Then confirm it is installed and tell me the trigger phrases. --- SOURCE --- --- name: marketplace-scout description: Search Facebook Marketplace, Craigslist, and eBay for a watchlist of items and report flip candidates by margin after fees and shipping. Trigger phrases: "run marketplace scout", "check my flip watchlist", "find flip deals". --- # Purpose Turn a plain list of item names into a ranked list of listings worth buying to resell, after fees and shipping are subtracted from the expected sale price. # Workflow 1. Read the watchlist: one item name per line, each with an optional target condition and an optional max price. The user maintains this list. 2. For each watchlist item, search Facebook Marketplace, Craigslist, and eBay active listings. 3. For each listing found, estimate the resale price from recent eBay sold or completed listings for the same item and condition. Use the median of at least 3 comps; skip the listing if fewer than 3 comps exist. 4. Estimate the total cost to acquire and resell: - the listing price - marketplace or payment fees on the resale (use the platform's published fee rate) - estimated shipping if the item will ship, $0 if local pickup 5. Compute the margin: estimated resale price minus listing price minus fees minus shipping. 6. Keep a listing only if the margin is positive and at least $25. 7. If the watchlist item set a max price, discard any listing above it. 8. Sort surviving candidates by margin, highest first, grouped by watchlist item. 9. If nothing survives, end the run and send nothing. 10. If something survives, write the report in the Output Contract shape and send it. # Output Contract Grouped by watchlist item, one line per candidate: - Listing: title, source (Facebook, Craigslist, or eBay), and link - Price: listing price - Est. resale: median of the sold comps used - Margin: dollar amount after fees and shipping No candidates: no message at all. # Operating Rules - Never message a seller, place a bid, or complete a purchase. Report only. - Never ask the user for a marketplace login, cookie, or API key. Use the assistant's own connected browsing session. - Never estimate resale price from asking prices; use sold or completed listings only. - If comps are too thin (fewer than 3), skip the listing rather than guess a margin. - Run only on the schedule the user confirms.