Works with the AI tools you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIGitHub CopilotGitHub CopilotGemini CLIGemini CLI+20 more

    Repair Diagnosis from Messy History

    1

    Converts messy customer complaints into structured technical diagnostic reports and safety-first checklists.

    $9

    Secure checkout via Stripe

    30-day refund guarantee

    Converts to your local currency at checkout

    0 installsSecurity scanned
    Repair Diagnosis from Messy History

    Repair Diagnosis from Messy History

    Example session with this skill installed

    The customer says the unit started smoking a bit yesterday. They tried replacing the fuse twice but it just blows again. It only happens when the dryer is set to high heat. They are very upset.

    • Read your context and instructions
    • Compiled the repair diagnosis from
    • Generated the document

    I have analyzed the customer report and filtered the narrative to focus on the technical data and safety risks.

    [Repair Diagnostic Report]

    ⚠️ Safety Warnings:

    • CRITICAL: Customer reported unit "started smoking." Potential fire hazard or internal component short.
    • ELECTRICAL: Recurring blown fuses indicate a high-current short circuit or grounded heating element.

    🔍 Extracted Technical Data:

    • Symptoms: Unit smoking during operation; fuse blows repeatedly.
    • Error Codes/Indicators: None reported; physical smoke observed.

    Past Failed Attempts: Replaced fuse twice (both failed/blew). DO NOT attempt to replace the fuse again without identifying the short.

    • Context: Issue is heat-dependent; occurs only when set to "high heat."

    🛠️ Step-by-Step Diagnostic Checklist:
    1.

    Visual Inspection: Disconnect power and inspect the heating element assembly for charred coils or contact with the housing.
    2. Continuity Test: Check the heating element for a short to ground.
    3.

    Wiring Harness Audit: Inspect the high-heat circuit wiring for melted insulation or pinched wires between the selector switch and the element.
    4.

    Load Test: If no shorts are found, check the blower motor for seizing, which may cause overheating on high settings.

    ❓ Clarification Questions for Customer:

    • Did the smoke have a specific smell (e.g., ozone, plastic, or lint)?
    • Was there a loud pop or flash when the fuse blew?

    [Self-Check]

    • Technical 4 data points extracted and categorized
    • Irrelevant customer rambling filtered out
    • Diagnostic checklist is logical, sequential, and avoids past failed attempts
    • Safety warnings prominently flagged if present

    Next steps

    1. Review the heating element continuity results.
    2. Inspect the high-limit thermostat for signs of heat stress.
    3. Order replacement wiring harness if insulation is compromised.

    repair-diagnosis-from-messy-history.pdf

    PDF · document

    Generated

    Example file from a real run - the skill writes it into your workspace.

    Connects securely to your tools. The creator never sees your data.

    What you get

    Extract technical facts from rambling customer emails and transcripts.Identify recurring faults by analyzing messy historical repair logs.Generate prioritized troubleshooting steps that avoid past failed attempts.Flag safety hazards like electrical shorts or burning smells immediately.

    About this skill

    The problem

    Technicians lose hours sifting through rambling customer emails, vague voice transcripts, and messy work orders. Missing a single detail about a past failed fix or a specific error code leads to redundant labor and incorrect parts orders.

    What it does

    • Extracts the "Technical 4": primary symptoms, error codes, past attempts, and environmental context.
    • Filters out emotional venting and irrelevant backstory to focus on repair data.
    • Generates a logical, sequential diagnostic checklist from easiest to most complex.
    • Flags critical safety hazards like burning smells or electrical sparks at the top of the report.

    Why this beats prompting it yourself

    General LLMs often include the customer's narrative fluff or suggest troubleshooting steps that the customer has already tried. This skill enforces a strict exclusion policy for failed attempts and prioritizes safety-first diagnostic logic tailored for hands-on technical work.

    Use cases

    • Converting customer support tickets into structured service bay work orders.
    • Analyzing long historical repair logs to identify recurring intermittent faults.
    • Triaging remote equipment failures based on non-technical user descriptions.
    • Standardizing diagnostic procedures across a team of junior technicians.

    Known limitations

    Requires a descriptive narrative input to be effective. It cannot predict hardware failures without specific symptoms or codes provided in the text.

    How to install

    Works the same in every agent - Claude, Cursor, Codex, Copilot and 20+ more.

    ~30 seconds
    1. 1

      Download the ZIP

      Free skills download straight away. Paid skills unlock right after purchase.

    2. 2

      Unzip into your skills folder

      Every agent reads skills from one folder on your machine. Drop the unzipped folder in there.

    3. 3

      Ask your agent to use it

      Restart the agent if it was already running. It picks the skill up automatically - no config needed.

    Skills folder by agent

    Click the path to copy it. Create the folder if it does not exist yet.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill passes our trust checks below.

    Security scanned

    Passed our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    30-day refund

    Not a fit? Get your money back

    Trust & safety

    Security scanned

    Verified clean 19 days ago

    • Passed all security checks, Safe to install

    Listed19 days ago

    What's inside

    Frequently Asked Questions