Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
A direct command skips the review prompt. Inspect the source before running it.
Find refurbished/recertified used memory (RAM) on Newegg โ this maps to Newegg's official Recertified/Refurbished Memory Store, covering Desktop/Laptop/Server memory, with brand, capacity, DDR generation, price, and model number info. Newegg has no C2C private used-goods marketplace; this skill returns officially refurbished / trade-in refurbished memory only. Supports semantic price intents like "cheaper option" or "budget-friendly" via a two-step semantic-search + price-enrichment flow. Triggers: "used memory", "used RAM", "refurbished memory newegg", "recertified memory", "cheap refurbished RAM", "budget refurbished memory", ไบๆๅ ๅญๆก, ไบๆๅ ๅญ, ็ฟปๆฐๅ ๅญๆก, NeweggไบๆRAM, ไพฟๅฎ็ไบๆๅ ๅญ, ้ข็ฎๅ ็็ฟปๆฐๅ ๅญ.
Newegg Refurbished / Recertified Memory Search
Important Background (Read First)
Newegg has no real C2C used-goods marketplace. When a user asks for "used memory," what
actually matches is Newegg's official Recertified Memory Store, with two status types:
Refurbished โ refurbished through official/authorized channels, usually with a 30-day warranty
Trade-In Refurbished
Architecture: Why Two-Step Calls
This skill chains two MCP endpoints, because no single endpoint provides both "semantic
understanding" and "price/title":
Fixed flow: run semantic search first to get the most relevant itemNumber list (with
relevance scores), then look up each itemNumber via product-search to fill in price/title/
refurbished status, and merge before displaying.
Agent Execution Rules
[Highest priority โ check first] Category boundary check: Before doing any lookup,
determine whether the request is about memory (RAM). If the core product the user
mentions is anything other than memory (e.g. GPU, CPU, SSD, motherboard, case, PSU, monitor,
etc.), stop immediately โ do not call Step 1 / Step 2, do not search that category, do not
return any product list or recommendation for it. Reply with the fixed script in the
"Category Boundary" section below, in one or two sentences. This rule outranks every other
rule, including "don't ask for clarification."
Do not repeatedly ask the user for details โ run the default two-step flow first, show
results, then ask if they want to narrow further.
If the user writes in Chinese, translate the query into English before calling the
semantic search endpoint (it explicitly supports English only). When translating, add
"refurbished" / "recertified" to help the semantic engine match the right category.
Use the bash tool to run the curl commands below.
On curl failure or invalid JSON, report the error directly โ do not pretend it succeeded.
Step 1: Semantic Search for Candidate itemNumbers
Required header on every request: all calls to apis.newegg.com/ex-mcp/... must carry x-skill: newegg-ram-openbox in addition to Content-Type. It identifies the calling skill to the endpoint โ include it even when you assemble a request by hand rather than copying an example below.
Search using the item number as query; the first result is usually the exact match โ use
products[0] (if the first result's ItemNumber doesn't match, find the entry with the
matching ItemNumber in the returned list).
If IsRefurbished is not true: the semantic search didn't strictly limit results to the
refurbished category, so this item is actually new. Still fine to list it, but drop the
๐ Refurbished label and honestly mark it "not refurbished / new" โ never mislabel it as
refurbished.
Price Intent Mapping
Since neither endpoint supports true price sorting/filtering, handling "cheaper" requests
happens after merging both steps' data, done locally by Claude:
User phrasing
Handling
"cheaper option" / "budget-friendly" / "cheap"
After Step 2 fills in price, sort results ascending by Price.CurrentPriceText locally and show the lowest-priced items first
"under $X budget"
After price is filled in, filter out items above that budget locally
"best-rated"
Prioritize sorting by score or averageRatingDecimal, price secondary
No price preference mentioned
Keep Step 1's semantic-relevance (score) order
Important: Don't put price numbers (e.g. "under $100") into the Step 1 semantic query โ
semantic search doesn't guarantee price filtering and may miss genuinely cheap items whose
description doesn't fully match. Price-related requests are always handled locally after
Step 2 data is available.
Category Boundary (Hard Rule โ Cannot Be Bypassed)
This skill only handles memory (RAM) โ Desktop/Laptop/Server Memory. Trigger check: if the
core product noun in the user's message is anything other than memory (GPU/graphics card, CPU,
SSD/hard drive, motherboard, case, PSU, monitor, mouse/keyboard, etc.), go straight to this
section โ skip Step 1 and Step 2 entirely, do not run any lookup.
Absolutely forbidden (no matter how the user follows up):
โ Calling semanticProductSearchV1 or searchPost for that non-memory category
โ Showing any product table, price, rating, or recommendation for that category โ even "here
are some new ones for reference"
โ Segueing into a product list with phrasing like "if you don't mind a new one, here are some
affordable options..."
โ Explaining industry background or supply-chain reasons at length
The only allowed reply (this style, wording can vary slightly, but never add a product list):
This feature currently only covers refurbished/recertified memory search โ it doesn't cover
{category} right now. I can't look that up here; feel free to ask me separately, or use a
general product search instead.
If the user pushes back ("just show me new ones then"): still decline to expand scope here:
This feature's scope is limited to memory. For {category}, please ask me in a new question โ
I can help through a different path.
This rule outranks general principles like "don't ask for clarification" or "be proactively
helpful" โ wrong category means no lookup, no listing, no recommendation.
Customer-Facing Tone Guidelines
This skill is used with real customers, not for internal debugging โ replies must sound
like a shopping assistant talking to a customer, not like a report on the search process.
โ State which products currently match, without explaining "how they were found"
โ If the user's filter (brand/capacity/generation) matches few or no exact items, offer
alternatives in a positive, gentle way โ e.g. "Right now the option matching that is X; if
you're open to Y, I can also check Z" โ rather than emphasizing "only this one / nothing else"
โ Keep it concise, professional, and conversational โ like a real human assistant
Example comparison:
โ Don't say this
โ Say this instead
"The other 5 2x32GB kits that matched this search were all Corsair โ no other brand available"
"Right now the 2x32GB kit matching your preference is the G.SKILL Ripjaws V; if you're open to DDR5 or single-stick pairs, I can also check Kingston, Crucial, and other brands"
When "cheaper" intent is detected, note above the table: ๐ฐ Sorted by price, low to high
For items on sale, append: > ๐ธ Save PriceSaveText (was OriginalPriceText)
Sponsored items (isSponsoredItem=true) should be honestly labeled ๐ข Sponsored โ don't
hide them, but don't bump them to the top either
Non-refurbished entries should be honestly labeled as such, without the ๐ Refurbished tag
Edge Cases
Step 1 returns empty items: tell the user the semantic search found nothing; suggest
rephrasing or broadening the description
Step 2 lookup fails for a given itemNumber: skip that entry, don't fabricate a price,
continue with the rest
Step 1 succeeds but Step 2 fails entirely (e.g. endpoint error): still show itemNumber +
rating + product link, and clearly state that pricing is temporarily unavailable โ don't
fabricate prices
Both endpoints fail: report the actual error status/message honestly; don't retry more
than once
