Resolve a Lenovo machine type, serial number, or product slug to its canonical pcsupport.lenovo.com product page, then return the Hardware Maintenance Manual (HMM) PDF, part numbers (FRU/CRU), driver downloads, BIOS/UEFI updates, diagnostic tools, warranty status, and self-repair guide. Read-only.
Automate repetitive workflows and reduce manual effort
Example: Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example: Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example: Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
Time estimate: 15-45 minutes depending on use case complexity
Prerequisites
Submit your Claude Code skill and start earning
browse install support.lenovo.com/find-repair-guides-eg8mahCompatible with
Supported agents
| name | find-repair-guides |
| title | Lenovo Support Repair Guides & Parts Lookup |
| description | >- Resolve a Lenovo machine type, serial number, or product slug to its canonical pcsupport.lenovo.com product page, then return the Hardware Maintenance Manual (HMM) PDF, part numbers (FRU/CRU), driver downloads, BIOS/UEFI updates, diagnostic tools, warranty status, and self-repair guide. Read-only. |
| website | support.lenovo.com |
| category | support |
| tags | - lenovo - repair - hmm - drivers - warranty - thinkpad - support |
| source | 'browserbase: agent-runtime 2026-05-20' |
| updated | '2026-05-20' |
| recommended_method | hybrid |
| alternative_methods | - method: api rationale: >- The public REST API at supportapi.lenovo.com (Warranty, Catalog, Product, Content, Part, Accessory) requires a sales-issued ClientID header — verified inaccessible to agent-runtime. The undocumented /api/v4/mse/getproducts endpoint on pcsupport.lenovo.com is the one usable pure-JSON path: it resolves any identifier (machine type, serial, slug) to the canonical product slug in ~200ms without auth or proxy. Use it as step 1 of the hybrid flow. - method: browser rationale: >- Drivers, parts BOM, and the HMM PDF link are JS-hydrated and the XHR endpoints behind them (deny-access from outside the page context). Pure-browser fallback works if the JSON resolver is unavailable — start at the pcsupport homepage and use the product search box — but the hybrid path is materially faster. |
| verified | true |
| proxies | true |
Resolve a Lenovo product identifier (machine type like 21ML/20VE, serial number like PF2W2GLT, or marketing name like "ThinkPad T14 Gen 5") to its canonical pcsupport.lenovo.com slug, then enumerate the artifacts a repair tech actually needs: Hardware Maintenance Manual (HMM) PDF, part numbers (FRU/CRU), driver downloads, BIOS/UEFI updates, diagnostic tools, warranty status, and the Self-Repair Guide (ThinkPad/ThinkCentre/ThinkStation only). Read-only — never click "Order Part", "Start Repair", or warranty-claim CTAs.
The agent uses a hybrid path: an undocumented JSON resolver gets you from any identifier to the canonical product slug in one HTTP call, then you browse the rendered sub-pages with stealth+proxy to scrape the actual artifacts. Pure-API harvesting of drivers/parts is not available — the public REST API at supportapi.lenovo.com requires a sales-issued ClientID (verified 2026-05-20: docs page returns 200 but every endpoint demands ClientID: header), and the in-browser XHR endpoints (/api/v4/mse/getdocument, /api/v4/mse/getUserguide, etc.) are 404 or deny access from outside the page context.
GET https://pcsupport.lenovo.com/us/en/api/v4/mse/getproducts?productId={query}
{query} accepts:
21ML, 20VE) — returns Type: "Product.MachineType".PF2W2GLT) — returns Type: "Product.Serial" plus the parent machine-type chain in Id.ThinkPad+T14+Gen+5) — does NOT work, returns []. Use machine type or serial.The response is a JSON array; each entry has:
Id — slash-delimited slug (e.g. LAPTOPS-AND-NETBOOKS/THINKPAD-T-SERIES-LAPTOPS/THINKPAD-T14-GEN-5-TYPE-21ML-21MM/21ML). Lowercase this and append it to https://pcsupport.lenovo.com/us/en/products/ to build the product home URL.Name — human-readable label.Type — Product.MachineType, Product.SubSeries, or Product.Serial.Brand — TPG (ThinkPad-Gov / commercial), IDEA (consumer), etc.Multiple entries returned ⇒ pick the one matching Type == "Product.MachineType" for a clean machine-type query, or the entry whose Serial field equals the input for a serial query. Empty [] ⇒ unknown identifier; bail with success: false, error_reasoning: "product not found".
This call works without --verified and without --proxies — it's served straight from the API tier and is not gated by Akamai for JSON Accept. ~200ms typical.
https://pcsupport.lenovo.com/us/en/products/{lowercased Id}
Example: …/products/laptops-and-netbooks/thinkpad-t-series-laptops/thinkpad-t14-gen-5-type-21ml-21mm/21ml
The HTML pages are Akamai-fronted (_abck, bm_sz, ak_p cookies in every response). A bare Browserbase session typically gets through but stealth is recommended:
sid=$(browse cloud sessions create --keep-alive --verified --proxies | …)
browse open "$URL" --remote --session "$sid"
browse wait timeout 3000 --remote --session "$sid" # client-side hydration
browse snapshot --remote --session "$sid"
The product home page surfaces the four primary tab links (Drivers & Software, Diagnose & Fix, Guides & Manuals, Warranty & Service) — but you can navigate to each tab's URL directly (paths below).
Navigate to:
…/products/{lowercased Id}/document-userguide/doc_userguide
The HMM PDF link is not at a guessable filename. It's published at https://download.lenovo.com/pccbbs/{folder}_pdf/{combined-model-slug}_hmm_en.pdf where:
{folder} is mobiles_pdf for laptops/ThinkPad/IdeaPad, thinkcentre_pdf / desktops_pdf for desktops, motherboards_pdf for boards.{combined-model-slug} is a multi-model combined slug because Lenovo publishes one HMM per chassis-family. Verified 2026-05-20: T14 Gen 5 (21ML) HMM is at …/mobiles_pdf/t14g5_t16g3_p14sg5_hmm_en.pdf — covering T14 Gen 5 + T16 Gen 3 + P14s Gen 5 in one PDF.Don't guess the slug — scrape it from the rendered page. After wait timeout 3000, the doc list resolves and the URL is in the page HTML (search download\.lenovo\.com/pccbbs/[^"]+_hmm_en\.pdf after browse get html body). The clickable list shows href="#" placeholders pre-hydration, so don't extract from anchors before the wait.
Example one-liner (after navigating to the doc_userguide page):
browse get html body --remote --session "$sid" \
| grep -oE 'https?://download\.lenovo\.com/pccbbs/[^"]+_hmm_en\.pdf' \
| head -1
…/products/{lowercased Id}/downloads/driver-list
The page hydrates client-side and shows a category list (BIOS/UEFI, Chipset, Audio, Camera, Networking, Storage, …). Each category is collapsed; click the category row to expand and reveal individual driver rows (name, version, OS, severity, "Download" button). The flat XHR endpoint that backs this UI (/api/v4/downloads/drivers) returns {"body":"","message":"deny access"} to outside-page calls — there's no shortcut. Snapshot strategy:
browse open ".../downloads/driver-list" --remote --session "$sid"
browse wait timeout 3000 --remote --session "$sid"
browse snapshot --remote --session "$sid" # category refs
browse click "@<bios-category-ref>" --remote --session "$sid"
browse wait timeout 2000 --remote --session "$sid"
browse snapshot --remote --session "$sid" # individual drivers visible
The Download anchors are absolute URLs to download.lenovo.com/pccbbs/{folder}/...exe (Windows installers) or .../...iso for bootable BIOS update images.
Diagnostic tools: same page, look for the "Diagnostic Tools" category (when present) — typically Lenovo Diagnostics — Bootable USB ISO + Lenovo Diagnostics — Windows.
…/products/{lowercased Id}/parts/PARTS_BOM_LOOKUP
Renders a BOM table: part description, FRU number, CRU type (Self / Optional / N — "non-CRU, FRU only"), price (where available). The page is also JS-rendered — wait timeout 3000 then snapshot.
A separate site, not under the product slug:
https://support.lenovo.com/us/en/selfrepair/sr{NNNNNN}-{kebab-product-name}-self-repair-guide
The numeric sr{NNNNNN} ID has no derivation rule — it's not the machine type, not the GUID, not the slug hash. Discover it via search, not guessing: either (a) Browserbase Search (browse cloud search "lenovo {model} self-repair guide") — first hit is reliably the canonical SR URL — or (b) the "Repair & Service" tab on the product home page links into it.
Verified 2026-05-20: T14 Gen 5 → sr500045-thinkpad-t14-gen-5-21ml-21mm-self-repair-guide (covers all four sibling machine types 21ML, 21MM, 21MC, 21MD).
Self-Repair Guides are interactive HTML walkthroughs with embedded videos and step-by-step procedures — substantially friendlier than the HMM PDF for non-technicians.
https://pcsupport.lenovo.com/us/en/warrantylookup
(redirects to …/warranty-lookup#/)
The form requires a serial number — machine type alone returns nothing. The lookup is a single text input + Submit button. After submit:
wait timeout 4000Active / Expired), warranty type (e.g. Premium Care), start date, end date, country of purchase, model description.If the request only supplied a machine type (no serial), return warranty: null, warranty_note: "serial required". The pcsupport.lenovo.com warranty lookup is rate-limited if hammered — keep ≤ 1 req/sec sustained.
Service bulletins (a.k.a. "Solutions" / "Tip" articles) live at:
…/products/{lowercased Id}/solutions/documentation
Filter the list by category badge: "Tip" articles include known-issue advisories and bulletin-style notes. There is no separate "service bulletin" feed — Lenovo merges them with how-tos in the Solutions section.
supportapi.lenovo.com is gated. The docs page (/Documentation/Index.html) advertises Warranty, Catalog, Product, Content, Part, Accessory endpoints — but every call requires a ClientID: header obtained via "your account manager or sales representative." For agent-runtime use, this is unreachable. Don't waste budget probing it.mse/getproducts is the unsung hero. Smart resolver — accepts machine type (4-char), serial number (8-char), and full slug; returns the canonical Id slash-path you need to build every other URL. Marketing names ("ThinkPad T14") return empty. The endpoint works without proxy/stealth (no Akamai gate on Accept: application/json).mse/* endpoints look promising but are 404 or deny access from outside the rendered page context. Verified 2026-05-20: getdocument, getUserguide, getProductsBySerialId, downloads/drivers, contents/list, contents/getContentsByProductId, upgradableComponents/products/{...} all fail. The browser is required to render the JS app before these XHRs are accepted.--verified --proxies session passes uniformly. A bare session (no flags) also generally passes for pcsupport.lenovo.com page renders, but inconsistently — recommend --verified --proxies for reliability. The download.lenovo.com PDF/EXE host is not Akamai-gated; direct curl works.t14g5_t16g3_p14sg5_hmm_en.pdf. Don't try to derive the slug from the machine type — scrape it from the document-userguide/doc_userguide page after wait timeout 3000.document-userguide page anchors are href="#" pre-hydration. The actual PDF URLs land in a JS urlMap object that resolves on the click handler. After waiting 3s, the URLs are in the page HTML (just not in the anchor href — they're in script-tag JSON). Use a regex on browse get html body, not browse snapshot ref enumeration.browse cloud fetch --proxies will return a 502 "response body exceeded the maximum allowed size" — verify availability via HEAD or browser navigation, don't try to download through the proxy fetch.wait timeout 3000; individual drivers only appear after expanding a category (browse click @<category> → wait → snapshot). The XHR endpoint that backs this is gated to in-page calls only.srNNNNNN) are unguessable. No deterministic mapping from machine type to SR ID. Use Browserbase Search as a discovery shortcut — "lenovo {model} self-repair guide" reliably surfaces the canonical URL as result #1.mse/getproducts Brand codes: TPG = ThinkPad/Think commercial, IDEA = consumer (IdeaPad/Yoga/Legion), LEN/LCFC/etc. = OEM/legacy. Useful for routing — Self-Repair Guides only exist for TPG./us/en/ work for any machine type globally; non-US users are served the same artifacts. The X-Country header (referenced in the eSupport WebAPI docs) only matters for the gated REST API. For the public web UI just use /us/en/.{
"success": true,
"query": "21ML",
"product": {
"machine_type": "21ML",
"name": "T14 Gen 5 (Type 21ML, 21MM) Laptops (ThinkPad)",
"brand": "TPG",
"slug": "LAPTOPS-AND-NETBOOKS/THINKPAD-T-SERIES-LAPTOPS/THINKPAD-T14-GEN-5-TYPE-21ML-21MM/21ML",
"support_url": "https://pcsupport.lenovo.com/us/en/products/laptops-and-netbooks/thinkpad-t-series-laptops/thinkpad-t14-gen-5-type-21ml-21mm/21ml"
},
"hmm": {
"title": "ThinkPad T14 Gen 5 / T16 Gen 3 / P14s Gen 5 Hardware Maintenance Manual",
"pdf_url": "https://download.lenovo.com/pccbbs/mobiles_pdf/t14g5_t16g3_p14sg5_hmm_en.pdf"
},
"self_repair_guide_url": "https://support.lenovo.com/us/en/selfrepair/sr500045-thinkpad-t14-gen-5-21ml-21mm-self-repair-guide",
"downloads": [
{
"name": "BIOS Update Utility (Bootable CD)",
"category": "BIOS/UEFI",
"version": "1.34",
"os": "Bootable",
"severity": "Recommended",
"url": "https://download.lenovo.com/pccbbs/mobiles/n3sur05w.iso"
},
{
"name": "Intel Wi-Fi Driver",
"category": "Networking: Wireless LAN",
"version": "23.30.1",
"os": "Windows 11 (64-bit)",
"severity": "Recommended",
"url": "https://download.lenovo.com/pccbbs/mobiles/..."
}
],
"parts_url": "https://pcsupport.lenovo.com/us/en/products/laptops-and-netbooks/thinkpad-t-series-laptops/thinkpad-t14-gen-5-type-21ml-21mm/21ml/parts/PARTS_BOM_LOOKUP",
"service_bulletins_url": "https://pcsupport.lenovo.com/us/en/products/laptops-and-netbooks/thinkpad-t-series-laptops/thinkpad-t14-gen-5-type-21ml-21mm/21ml/solutions/documentation",
"diagnostic_tools_url": "https://pcsupport.lenovo.com/us/en/products/laptops-and-netbooks/thinkpad-t-series-laptops/thinkpad-t14-gen-5-type-21ml-21mm/21ml/downloads/driver-list",
"warranty": null,
"warranty_note": "serial required",
"error_reasoning": null
}
When called with a serial number, populate warranty:
{
"warranty": {
"status": "Active",
"type": "Premium Care",
"start_date": "2024-08-12",
"end_date": "2027-08-11",
"country_of_purchase": "United States",
"model_description": "ThinkPad T14 Gen 5"
}
}
When the identifier is unknown:
{
"success": false,
"query": "ZZZZ",
"error_reasoning": "product not found for query \"ZZZZ\" — mse/getproducts returned []"
}
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionfind-repair-guidesExecute the skills CLI command in your project's root directory to begin installation:
browse install support.lenovo.com/find-repair-guides-eg8mahFetches find-repair-guides from support.lenovo.com/find-repair-guides-eg8mah and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
.cursor/skills/find-repair-guides
Restart Cursor to activate find-repair-guides. Access via /find-repair-guidesin your agent's command palette.
Learn more:View source on GitHubSkills CLI docsAbout CursorWhat are agent skills?
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
find-repair-guides
support.hp.com/find-repair-guides-ks282r · support · 3 shared tags
find-repair-guides
dell.com/find-repair-guides-q4h1h4 · hardware-support · 3 shared tags
Legal Compliance Checker
msitarzewski/agency-agents · support · tag: support
Finance Tracker
msitarzewski/agency-agents · support · tag: support
Support Responder
msitarzewski/agency-agents · support · tag: support
Infrastructure Maintainer
msitarzewski/agency-agents · support · tag: support
find-repair-guides is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
We added find-repair-guides from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Solid pick for teams standardizing on skills: find-repair-guides is focused, and the summary matches what you get after install.
find-repair-guides fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
find-repair-guides is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Useful defaults in find-repair-guides — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Keeps context tight: find-repair-guides is the kind of skill you can hand to a new teammate without a long onboarding doc.
Useful defaults in find-repair-guides — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
find-repair-guides has been reliable in day-to-day use. Documentation quality is above average for community skills.
I recommend find-repair-guides for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
showing 1-10 of 63