← iFixitCONTENT HISTORY
WHAT CHANGED
Update to iFixit
Snapshot Nov 17, 2026 · 00:12 UTC · version 1.3.18
Collection source: downloaded plugin package.
First saved snapshot
No earlier snapshot is available to establish a change.
Save iFixit and check future changes in Following.
Up to 3 plugins free · no card required.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "Find iFixit repair guides, troubleshoot an item, identify the correct model, or list maintenance schedules. Use for repairing or maintaining things, including requests to prepare a repair plan. iFixit has repair information for an astounding variety of things, from toasters to cars to appliances to chainsaws. Repair information does not require signing in; connect a user’s account to access their workbench with ownership history: purchase records, maintenance history, service information, parts and more.",
"included_files": [],
"name": "find-repair-information",
"skill_md_contents": "---\nname: find-repair-information\ndescription: >-\n Find iFixit repair guides, troubleshoot an item, identify the correct model, or\n list maintenance schedules. Use for repairing or maintaining things, including\n requests to prepare a repair plan. iFixit has repair information for an astounding\n variety of things, from toasters to cars to appliances to chainsaws. Repair\n information does not require signing in; connect a user’s account to access their\n workbench with ownership history: purchase records, maintenance history, service\n information, parts and more.\n---\n\nUse the iFixit MCP tools to ground the answer in the selected device's sources.\nThe user's requested scope determines how much of the workflow to perform.\n\n## Identify and retrieve\n\n- When the user mentions an item they own without naming its model, call\n `ifixit.list_items` before searching or asking. If one item matches, use it:\n its device for the search, its nickname and notes for details such as the\n year. `ifixit.get_item` adds notes and recent repairs, such as the last oil\n change. Ask for the model when none do, and then add the item to their\n workbench once you've identified it.\n- If the model or the exact symptom is still missing, ask only for what you\n need to continue. Ask one focused question at a time, even when that one\n question asks for both the model and the symptom.\n- Use `ifixit.search` with the model and symptom or repair as `query`, and the\n item alone as `device` (\"Samsung washer\"). Ask for a model number whenever\n possible; similar models require materially different instructions or parts.\n- Use `ifixit.get_device` with the exact \"Device title\" a search result lists,\n not its URL. Its `wikiid` identifies a model, not a device someone owns.\n\n## Deliver the guide\n\nWhen a guide answers the request, send the user to the guide instead of\nretyping it.\n\n- Read the best-matching guide with `ifixit.get_guide`, using the \"Guide ID\"\n from search, before recommending it. Search results alone don't show what\n the guide covers or needs. Results include all steps and inline\n prerequisite steps.\n- Link the guide's `url`. Add one or two sentences on what it covers and its\n difficulty and time, then invite the user to ask about any step.\n- Don't list, summarize, or paraphrase the guide's steps, and never write them\n out as a numbered list. A paraphrase loses the photos and the warnings on\n each step, and a dropped warning can hurt someone. The guide page is the\n source of truth.\n- When the user asks about a step, answer that question directly and keep the\n step's cautions. Don't walk through the rest of the guide. Link the step as\n `{url}#s{stepid}`, copying `stepid` from the guide, and don't give a step\n number you counted yourself.\n- You can still explain a concept, define a term, or add safety context in\n your own words. Keep model variants, parts compatibility, and tool\n requirements tied to the guide.\n\n## Maintenance\n\nUse `ifixit.get_maintenance` with the exact device title. An empty schedule\nmeans iFixit has no published schedule yet. It does not mean the device needs\nno maintenance.\n\n## Parts\n\nFind a part for the exact model the repair is on. Use `ifixit.search` for a\nspecific part, such as \"iPhone 14 battery\". Suggest a part only for the repair\nat hand, and link its page: the purchase happens on ifixit.com.\n\n## Answer and follow through\n\nLink the selected guide or device page and explain why it fits the request.\nSummarize the useful result instead of repeating every search card. If a price is\nunavailable, omit the amount rather than substituting another product's price.\nA failed tool call is not an empty search or evidence that no guide exists.\n\nPublic research and planning require no login. Adding an owned item or saving a\nrepair requires authenticated Workbench tools. If those tools are unavailable,\nkeep the plan in the conversation and explain that nothing has been saved. Never\nclaim that a research call added a device, recorded maintenance, or set a reminder.\n"
}SHA-256 of public snapshot: 8d51c041af66aefa52ed7ddc9c5178867580474d87a71c2e2a5dca530dfb72ed