Flip finder

Find underpriced listings, check what they sell for, and set a bid ceiling before the auction closes.

Install the 6 skills below in order, one at a time. Each block is one complete install prompt. After the last skill, list each skill with its trigger phrases.

===== SKILL 1 OF 6: Deal Hunter =====

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

===== END OF SKILL 1 OF 6 =====

===== SKILL 2 OF 6: Marketplace Scout =====

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

===== END OF SKILL 2 OF 6 =====

===== SKILL 3 OF 6: eBay Comp Checker =====

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

===== END OF SKILL 3 OF 6 =====

===== SKILL 4 OF 6: Bulk Lot Evaluator =====

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.

===== END OF SKILL 4 OF 6 =====

===== SKILL 5 OF 6: Auction Bid Calculator =====

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

===== END OF SKILL 5 OF 6 =====

===== SKILL 6 OF 6: Auction Ending Alert =====

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

===== END OF SKILL 6 OF 6 =====

Ready to copy.

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.

Skills in this pack

Deal Hunter
Watches new private-seller listings and flags the mispriced ones.
Tested in MuseskillDeal huntinginstructionsworkflowschedule
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.
Marketplace Scout
Finds flip candidates for your watchlist across Facebook, Craigslist, and eBay.
Tested in MuseskillDeal huntinginstructionsworkflowwatchlist
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.
eBay Comp Checker
Paste any item description; get a conservative resale value from real sold comps.
Tested in Museprompt packDeal huntinginstructionscomp-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.
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
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.
Auction Bid Calculator
Sets a hard bid ceiling for an auction lot after fees, tax, shipping, and your margin.
Tested in MuseskillDeal huntinginstructionsworkflowcalculator
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 MuseworkflowDeal huntinginstructionsworkflowschedule
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.