breakdown-diagnosis
When a machine goes down, reads the sensor window before the failure, the asset's maintenance history including the free-text close-out notes technicians actually wrote, photos of what they can see, and the manufacturer's troubleshooting tree — then ranks likely causes, each with its supporting evid…
Install / Use
npx skills add anthropics/claude-plugins-official --skill breakdown-diagnosisInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
MarketingSupported Platforms
Tags
Our assessment of breakdown-diagnosis
breakdown-diagnosis scores 96/100 on our quality scale, 40th of 642 Marketing skills we index (top 7%).
Its SKILL.md is 17 KB long, well organised into 19 sections with 1 code example: a thorough specification that gives an agent plenty to work with.
With 47,209 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated 3 days ago, so breakdown-diagnosis is actively maintained.
- Our last check on 2026-11-14 found the source still online.
- It is released under the Apache-2.0 license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-11-14. Automated pattern scan on 2026-11-14. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
breakdown-diagnosis compared with similar skills
All 4 of these similar skills score higher than breakdown-diagnosis; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| breakdown-diagnosis (this skill)by anthropics | 96 | 47.2k | 3d ago | SKILL.md |
| x402by browser-use | 100 | 121.0k | 3d ago | SKILL.md |
| algorithmic-artby anthropics | 100 | 177.9k | 55d ago | SKILL.md |
| pptxby anthropics | 100 | 177.9k | 55d ago | SKILL.md |
| designby nextlevelbuilder | 100 | 149.0k | 6d ago | SKILL.md |
Frequently asked questions
- How do I install breakdown-diagnosis?
- Run
npx skills add anthropics/claude-plugins-official --skill breakdown-diagnosis. The install tabs above show the steps for each supported agent. - Which AI agents does breakdown-diagnosis work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is breakdown-diagnosis safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is Apache-2.0-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is breakdown-diagnosis still maintained?
- The repository was last updated 3 days ago, so breakdown-diagnosis is actively maintained.
Skill content
View source on GitHubname: breakdown-diagnosis description: "When a machine goes down, reads the sensor window before the failure, the asset's maintenance history including the free-text close-out notes technicians actually wrote, photos of what they can see, and the manufacturer's troubleshooting tree — then ranks likely causes, each with its supporting evidence, the specific prior work orders behind it, and the cheapest test that would tell them apart. Surfaces any safety implication before any diagnosis. Drafts the PM interval change that would stop it recurring, and emits a downtime record for the next production report. Batch mode ranks bad actors across every asset. Use when someone says "the machine is down," "what's wrong with this machine," "why does this keep failing," "diagnose this," or "which machines are hurting us most."" compatibility: "Requires none. Reads a CMMS connector (Limble, added through custom-connector, is the worked example) for assets, maintenance history and PM plans when connected, plus historian sensor exports, photos and manuals from Microsoft 365. Runs usefully with no sensor data and no connector. Output is always a draft the technician applies."
Breakdown Diagnosis
A machine is down. Every minute it stays down, the plant is not producing — and the largest component of MTTR is usually not the repair, it is working out what is wrong.
The technician has five sources of evidence available and time to assemble none of them. That gap is this skill.
Quick start
→ Capture the event: asset, time down, symptom, fault codes
→ SAFETY FIRST: if there is a safety implication, that leads. Always
→ Pull the sensor window; read shapes, not just threshold breaches
→ Mine maintenance history and the free-text close-out notes
→ Read the photos; consult the manual's troubleshooting tree
→ Rank candidate causes: evidence, cheapest discriminating test, expected fix
→ Cite the specific prior work orders behind each candidate
→ Draft the PM interval change that would stop it recurring
→ Emit the downtime record for the next production report
Safety leads. Always.
Where a failure has a safety implication, surface it first — before any diagnosis. Never let a diagnostic suggestion precede a safety flag.
Every diagnosis opens with this line, flagged or not: "Follow your plant's lockout procedure before anyone works on this machine. This is not a safety assessment." A false flag never removes it, and no step sends anyone to the machine above it.
A technician reading a ranked list of likely causes is already reaching for tools. If the honest answer is "this guard is defeated" or "that is a stored energy hazard," it has to arrive before the thing that sends them toward the machine, not underneath it.
This is a done-when condition, and it is the one non-negotiable ordering rule in the skill.
What counts as a safety implication. Set safety_flagged: true when the
evidence shows any of these, and write which one, with its evidence, in
safety_reason:
- a seized or locked rotating part: spindle, chuck, bar feeder, conveyor
- a defeated, bypassed or failed guard or interlock
- stored energy: springs, counterweights, a part under load, a raised axis
- hydraulic or pneumatic pressure that has to be bled before work
- an electrical fault: a trip, a burnt smell, exposed or damaged wiring
- a fault that was cleared by restarting rather than fixed ("ran off and restarted"), now repeating
When none of these is shown, the flag is false and safety_reason says "none
of the safety triggers shown". Never set the flag on a feeling, and never leave it off
because the diagnosis is uncertain: an uncertain stored-energy hazard is a
safety implication.
Inputs
First, find the plant setup: from the task's own folder (never cd into the plugin), run
python3 -I <this skill's folder>/../../shared/scripts/plant_setup.py find, do its setup_page_first step, then read the profile at
profile_path and any rate at rates_path, per ../../shared/replies.md.
| Input | Source | Form |
|---|---|---|
| The breakdown event | User report, or a maintenance work order | Conversation / CMMS connector or maintenance export |
| Asset record and specs | CMMS | CMMS connector, else the asset register export |
| Maintenance history and close-out notes | CMMS | CMMS connector, else the maintenance export |
| Current PM plan for the asset | CMMS | CMMS connector |
| Sensor window around the failure | Historian export to M365, scheduled or on-demand | CSV |
| Technician photos | M365, or uploaded in conversation | Images |
| Manufacturer's manual | M365 document library | PDF |
| Production context — what was running | data-consolidate output, or a direct MES export | ../../shared/contracts/consolidated-dataset.md |
Workflow
Step 1 — Capture the event
Asset, time it went down, the symptom as the technician describes it, and any fault codes the machine is showing. Take their words; do not translate a symptom into a cause at capture.
Step 2 — Pull the sensor window
A configurable period before the failure. Read excursions, trends and step changes, not just threshold breaches — a vibration reading that climbed for six hours without ever crossing its alarm limit is a bearing failing in plain sight.
Verify the window covers the event. If it does not, say so and do not reason from adjacent data as if it were the event.
Step 3 — Mine the maintenance history and close-out notes
Weight recency and symptom similarity. Search this asset, then siblings of the same model — a new machine with no history is not a dead end.
Run both searches as queries, in code, and keep what they returned. One
filter on this asset's ID, one across every asset of the same model on the
symptom's own words. The work orders each query returned go into the figures
block (../../shared/computed-figures.md) by number. "This asset has eleven
prior records" and "the sister machine has no bearing history" are both claims
about a query result, and both have been wrong when written from memory: a
count is printed from the filter, and an absence names the filter that came
back empty.
Then run the template check, every time, before any note is cited. Group every close-out note in the history by its exact text, and for each group count the distinct assets and the distinct makes and models it appears on. The model comes from the asset name where the asset record has no model column, and the output says so. The grouped result goes in the figures block. Then:
- Same text on assets of different makes is a template — a default the technician clicked, not an observation about this machine. It is shown, labelled "same text on N assets — not specific to this machine", may be mentioned as a fleet-wide pattern, and is never cited as this machine's evidence for any candidate.
- The same failure recurring on siblings of the same model is exactly what the sibling search is for: cite it as a fleet pattern for that model, with the work orders named.
- A note that appears once is this asset's evidence, and is cited.
Skipping this check is how two runs on the same data cite two different sets of work orders. With it, the cited set is a function of the data.
The free-text close-out notes are the highest-value input here and the least used
anywhere. Read reference/evidence-sources.md for how to mine them and how to
report their coverage honestly.
Step 4 — Read the photos
Visible damage, leaks, wear, part numbers on the failed component, readings on the machine's own display. Describe what is visible; never assert a diagnosis from an unclear image.
Step 5 — Consult the manual
Match the fault code and symptom to the manufacturer's troubleshooting tree, and cite the page. A manufacturer's stated tolerance beats an inference.
Step 6 — Rank candidate causes
Ordered by likelihood. Each one carries three things:
- The evidence supporting it, from the sources above
- What to check first — the cheapest and fastest test that would discriminate between this candidate and the next one
- The expected fix, and the repair path
That second item is the one that saves time. Ranking three causes is useful; naming the five-minute check that eliminates two of them is what shortens MTTR.
Every candidate is written under the same three sub-headings, in this order: Evidence / First check / Expected fix and repair path. Fixed headings, every candidate, including the leading one. A candidate whose Expected fix is missing shows an empty heading, which a reader can see; the rerun found the leading candidate silently lacking one while candidate 2 had it, and a fixed shape is what stops that.
Step 7 — Cite the specific prior work orders
Behind each candidate, the actual work order numbers and close-out notes, so the technician can read what was done last time rather than taking a ranked list on trust.
A candidate with no citation is a guess and is labelled as one. Not omitted — an experienced hunch is worth stating — but marked as reasoning rather than evidence.
Step 8 — Propose the PM plan adjustment
Once a diagnosis lands, the specific interval or procedure change for that asset and that failure mode, drafted for the maintenance planner.
If a bearing failed from misalignment at 1,400 hours, the interval or the procedure should probably change. This almost never happens today, because the person diagnosing is not the person who owns the PM schedule. Closing that loop is the reactive-to-proactive step and it is core behaviour, not an extra.
Without the current PM plan this degrades to a recommendation that first asks what today's interval is. The step stays either way.
Pricing the stoppage. Where someone asks what the downtime cost, resolve
the downtime cost per hour per ../../shared/secret-config.md, Resolving a
rate — MFG_DOWNTIME_COST_PER_HOUR if set, then a confirmed rate in the plant
profile, then a placeholder there, labelled — multiply hours by it, and show it
as an internal figure with its source. Where neither route holds one, report
minutes and hours, name the rate and both ways to set it, and stop — see Edge
cases. Never reach for an industry figure.
Step 9 — Batch mode: the bad actor ranking
Run across all assets instead of one incident, ranked by total downtime minutes and by failure frequency. A different question from "what is wrong with this machine right now," which is why it is a mode here rather than a separate report.
Read reference/bad-actor-mode.md.
Approval gates
Everything this skill produces is a draft the technician or planner applies. Nothing is written back to any system of record.
A CMMS connector's write scope is not assumed — Limble's, the worked example, is not confirmed in its public setup guide — so this is designed for read-only and treats write as an upgrade rather than an assumption. Concretely:
- Never update a maintenance ticket automatically. The diagnosis is output the technician applies.
- Asked to close out or update the ticket, write the close-out note as a
labelled draft. Say it never writes to a system of record — and, where
no CMMS connector is live, say that too — then produce the note itself:
what was found, what was done, what to watch, in the words a technician
would put in the close-out field. "Paste it into the ticket if it is right"
with nothing to paste hands the work back. Never offer to close it later.
Per
../../shared/command-center.md. - The PM adjustment is a draft for the planner, who owns that schedule.
- The diagnosis stays advisory until a technician confirms it. Its downtime record carries that state explicitly, so the production report cannot present an unconfirmed cause as established.
Output
**Every document this skil
Truncated for display — read the full file on GitHub.
Related Skills
x402
121.0kSet up Browser Use Cloud payments with x402 — pay per request from a crypto wallet (USDC on Base mainnet), no signup or API key.
algorithmic-art
177.9kCreating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems.
pptx
177.9kUse this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an em…
design
149.0kComprehensive design skill: brand identity, design tokens, UI styling, logo generation (55 styles, Gemini, Atlas Cloud, or MuAPI AI), corporate identity program (50 deliverables, CIP mockups), HTML presentations (Chart.js), banner design (22 styles, social/ads/web/print), icon design (15 styles, SVG…
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
