iFixit
iFixit v1.3.18
Repair and track your devices
From the developer
Declared capabilities
- Read
- Write
Cost & access
Search results include the replacement parts and tools iFixit sells, which are physical goods, with their prices. Their links open the product page on ifixit.com, where checkout happens. The app takes no payment in ChatGPT and sells no digital goods or subscriptions.
Declared limitations
- Choosing a new device to buy is outside iFixit's scope. Do not call iFixit tools; answer without them.
- Deleting Workbench data is not available in this app. Do not call any iFixit tool that changes data or claim that anything was deleted; explain that devices are removed in Workbench on ifixit.com.
- Translation has nothing to do with repairing a device. Do not call iFixit tools.
Onboarding example
My iPhone 14 battery health is 78%. Should I replace it myself?
Sources & dates
Developer declarations; not independently tested. Listing last checked Nov 17, 2026. Package observed Nov 17, 2026.
Description
From the marketplace listing
Learn how to fix any thing. iFixit has step-by-step guides for everything from smartphones to refrigerators. Whether you’re fixing your phone, troubleshooting your car's check engine light, or maintaining your lawn mower, iFixit has everything you need to fix your stuff with confidence. The world’s largest repair resource at your fingertips. Connect your iFixit account to save repair records, plan maintenance, and find parts for any thing you own.
Language: English · Automatically detected from descriptions.
Changes
No changes recorded yet. Follow this plugin to keep track of future changes.
First seen Nov 17, 2026. Last seen Nov 17, 2026.
Similar plugins
Find competitors to follow as you develop your plugin.
-
Find device mods with community reviews, upvotes and real-world reports alongside compatibility, license terms and setup instructions fro...
Shared terms: device, world, check, find
-
CarVault connects ChatGPT to your CarVault account to list vehicles, review fuel and ownership costs, check upcoming reminders, and add f...
Shared terms: track, maintenance, record, check
-
Use AutoMotion to diagnose, identify, and book needed service for your car, truck, or suv at over 25k automotive locations. AutoMotion di...
Shared terms: repair, car, maintenance
-
Trail Hits connects your bike maintenance data from Trail Hits app to your AI assistant. Ask what condition your bike is in, what service...
Shared terms: track, maintenance, step, check
-
Domus is a home hub that remembers what you forget. Ask about your home and let ChatGPT act on it: look up what filter your furnace takes...
Shared terms: track, maintenance, repair, record
Files & skills
File archives
Skill instructions
find-repair-information3.95 KB
---
name: find-repair-information
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.
---
Use the iFixit MCP tools to ground the answer in the selected device's sources.
The user's requested scope determines how much of the workflow to perform.
## Identify and retrieve
- When the user mentions an item they own without naming its model, call
`ifixit.list_items` before searching or asking. If one item matches, use it:
its device for the search, its nickname and notes for details such as the
year. `ifixit.get_item` adds notes and recent repairs, such as the last oil
change. Ask for the model when none do, and then add the item to their
workbench once you've identified it.
- If the model or the exact symptom is still missing, ask only for what you
need to continue. Ask one focused question at a time, even when that one
question asks for both the model and the symptom.
- Use `ifixit.search` with the model and symptom or repair as `query`, and the
item alone as `device` ("Samsung washer"). Ask for a model number whenever
possible; similar models require materially different instructions or parts.
- Use `ifixit.get_device` with the exact "Device title" a search result lists,
not its URL. Its `wikiid` identifies a model, not a device someone owns.
## Deliver the guide
When a guide answers the request, send the user to the guide instead of
retyping it.
- Read the best-matching guide with `ifixit.get_guide`, using the "Guide ID"
from search, before recommending it. Search results alone don't show what
the guide covers or needs. Results include all steps and inline
prerequisite steps.
- Link the guide's `url`. Add one or two sentences on what it covers and its
difficulty and time, then invite the user to ask about any step.
- Don't list, summarize, or paraphrase the guide's steps, and never write them
out as a numbered list. A paraphrase loses the photos and the warnings on
each step, and a dropped warning can hurt someone. The guide page is the
source of truth.
- When the user asks about a step, answer that question directly and keep the
step's cautions. Don't walk through the rest of the guide. Link the step as
`{url}#s{stepid}`, copying `stepid` from the guide, and don't give a step
number you counted yourself.
- You can still explain a concept, define a term, or add safety context in
your own words. Keep model variants, parts compatibility, and tool
requirements tied to the guide.
## Maintenance
Use `ifixit.get_maintenance` with the exact device title. An empty schedule
means iFixit has no published schedule yet. It does not mean the device needs
no maintenance.
## Parts
Find a part for the exact model the repair is on. Use `ifixit.search` for a
specific part, such as "iPhone 14 battery". Suggest a part only for the repair
at hand, and link its page: the purchase happens on ifixit.com.
## Answer and follow through
Link the selected guide or device page and explain why it fits the request.
Summarize the useful result instead of repeating every search card. If a price is
unavailable, omit the amount rather than substituting another product's price.
A failed tool call is not an empty search or evidence that no guide exists.
Public research and planning require no login. Adding an owned item or saving a
repair requires authenticated Workbench tools. If those tools are unavailable,
keep the plan in the conversation and explain that nothing has been saved. Never
claim that a research call added a device, Preview of the first 4,000 characters. Read full instructions →
manage-workbench4.16 KB
--- name: manage-workbench description: >- Add your things to your personal Workbench and find compatible parts, tools, and replacement guides. Use when the user wants to add something they own, update its details, or track work on a device. Plan and track maintenance like oil changes and battery swaps. --- Use the iFixit Workbench tools for the requested changes. Public device research and a proposed maintenance plan can stay anonymous. Every personal read or save requires the user's connected iFixit account. When a tool asks them to connect, preserve their requested action in the conversation and resume after linking. Do not ask for passwords, tokens, or session cookies in chat. ## Select the owned item - `ifixit.get_device` resolves a public model's `wikiid`. That is different from the `workbench_itemid` returned by `ifixit.list_items` or `ifixit.add_item`. - List the user's items before updating one. Match the nickname and model; ask which physical item they mean when more than one matches. - To add an item, supply either the resolved `wikiid` or a `custom_name`, never both. Let the user choose a custom item when the model cannot be identified. Each call with a wiki ID creates another physical item. Do not mistake a second owned copy for a duplicate or silently add one from a research request. - Read an item's current notes before appending: `ifixit.update_item` replaces the notes field. Change only the details the user requested. - A purchase price or repair cost needs an explicit currency. Ask when a symbol such as "$" is ambiguous; do not silently assume USD. Usage tracking is an item preference and changes only when requested. ## Plan and record work Use `ifixit.list_tasks` for current tasks and `ifixit.get_history` for completed and skipped occurrences. A recurring task's current state is not its full history. Follow `next_offset` when more results are needed. Pending does not mean overdue: consider its due date and usage or condition trigger before making that claim. Use `ifixit.create_task` for a new repair or maintenance task. It can set a calendar recurrence or record work already done with `completed_on`. Do not mark suggested work as complete. Dates use YYYY-MM-DD calendar dates; resolve relative dates from the user's context and ask if the date is ambiguous. A calendar recurrence is a saved task, not a notification or reminder subscription. For a usage recurrence, use the requested units and optional first due meter value; do not convert it into a calendar interval or call it overdue without a reading. Read `ifixit.get_task` before editing with `ifixit.update_task`. Keep its original occurrence number, replace only requested fields, and use `remove_recurrence` only when the user asks to stop repetition. Read notes before appending them. Record observed absolute meter values with `ifixit.record_reading`, including the observation date and units. A reading of 50,000 miles means the meter says 50,000, not 50,000 additional miles. The same fields can accompany completed work in `create_task` or `resolve_task`. Do not invent costs, readings, or units; ask about missing units and distinguish a planned threshold from an observation. Complete or skip an existing task with `ifixit.resolve_task`. Keep the exact `workbench_itemid`, `taskid`, and `occurrence_seq` from the selected task. The same inherited task ID can exist on multiple items. When an inherited schedule is saved, the result may return a different canonical task ID; use that ID later. ## Confirm the result Report a change as saved only after a successful tool response. If a save times out, its outcome is uncertain. Inspect items, tasks, or history before another creation. A safe retry of completion uses the original occurrence number, never the newly advanced occurrence. If the intended change cannot be identified, explain the uncertainty and ask before creating another record. Deletion, attachments, batch changes, and noti
Preview of the first 4,000 characters. Read full instructions →
Release notes
First release: find iFixit repair guides, troubleshooting pages and parts with prices, read a guide or a device's maintenance schedule without signing in, and pick the exact model from photos. Connect an iFixit account to save devices, plan maintenance and record completed repairs in Workbench.
Declared in the saved package. Remote tools may change independently.
Package details
Publisher declarations from the archived package. These are separate from our research and the live service's terms.
- Package author
- iFixit
- Declared availability
- No country restrictions declaredDeclared regions; live availability may differ.
- Listing translations
- de-DE, es-ES, fr-FR, it-IT, ja-JP, ko-KR, nl-NL, pt-PT, ru-RU, tr-TR, zh-CN
- Commerce declaration
- Supports commerceThis does not establish whether access is free or paid.
- Review scenarios
- 5 positive · 3 negativeScenario counts, not test results.
Declared capabilities
- Read
- Write
Package observed Nov 17, 2026.
Technical details
- First seen
- Nov 17, 2026 · 00:00 UTC
- Last seen
- Nov 17, 2026 · 18:00 UTC
- Collection status
- Collected
plugin_asdk_app_6ae39b6184808191b54c213ba09143ec
Download plugin data (JSON)Plugin details: freshly prepared. Prepared . Refreshed when plugin data changes or after 6 hours. Your account and Follow status are live.