Bulk Lot Evaluator

Point it at a lot listing; get a max bid and a walk-away price.

Tested in MuseskillDeal huntinginstructionsworkflowvaluation-method

by Muse Skills editors · Written for this directory

Install 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.

View source

Ready to copy.

Details

Type: skill
Category: Deal hunting
Version: 1.0.0
Added: 9 Sep 2026
Author: Muse Skills editorsWritten for this directory
Includes: instructionsworkflowvaluation-method
Source: github.com/…/bulk-lot-evaluator.md

Install 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.

Before you install

A shared skill carries somebody else's instructions. Read the source before you install it.
Never paste an API key, password, or token into anything a skill asks for. Legitimate skills use Muse's own secure flows.
Installing copies the setup into your own environment. It gives the author nothing.

What it does

Bulk Lot Evaluator is for the “200 records, $150, must take all” listings. It reads the photos and description, values what it can actually see from sold comps, discounts the total for everything it can’t verify, and hands you a max bid and a walk-away price.

The core discipline: unseen items count as $0. Only what is visible gets valued.

What it includes

Photo-based item identification (visible / partial / unseen)
Conservative per-item comps from sold data
The 0.6 lot discount for unsellable and uncertain items
Max bid at 50% of the discounted total, plus a walk-away call

Example

Input: a listing photo showing roughly 200 LPs, asking $150.

Output:

Lot: "200 vinyl records, rock lot" [link]
Ask: $150
Visible value: ~$310 (12 identifiable titles at conservative comps)
Discounted total: $186 (0.6 lot discount)
Max bid: $93
Walk-away: negotiate to $93; walk away above $120
Speculative upside: two box sets partially visible, not counted

What this one touches

Reads the listing you point it at and public sold data. Writes only the evaluation back to you. Never contacts the seller, never bids, never negotiates. Never needs a marketplace login.

Install

Copy this block and paste it into your Muse chat. Muse does the install and confirms when it's done.

Install prompt

Install 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.

Install 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.

Full source

This is the exact text Muse installs. Read it. That's the whole trust model.

SKILL.md

---
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.

---
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.

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.