Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    Repair Diagnosis from Messy History

    1

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

    $5

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security 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

    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.

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

    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.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Business & Operations.

    Requires a descriptive narrative input to function. Cannot predict hardware failures without specific symptoms, codes, or history provided in the source text.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 2 months ago

    Permissions

    No special permissions declared or detected

    Listed2 months ago
    Updated12 days ago

    What's inside

    Frequently Asked Questions

    This skill acts as a pre-processor for service teams, stripping away conversational 'fluff' and emotional venting from customer reports to generate a structured, safety-prioritized technical brief and diagnostic checklist.

    The skill is designed to be platform-agnostic and works with any major LLM (such as GPT-4, Claude, or Llama) that supports text-based reasoning and structured output.

    Yes, this skill is specifically designed to recognize and flag recurring intermittent faults by comparing current symptoms against the historical 'past attempts' and 'environmental context' data extracted from logs.

    Upon purchase, you receive the production-ready logic package, a guide for integrating it into your existing workflow (like a CRM or Helpdesk), and a set of sample inputs to test accuracy.

    While the skill is highly effective at organizing messy text, it cannot diagnose hardware issues if the source text lacks specific details, such as error codes or observable symptoms.

    New in Business & Operations