← Back to Skills Marketplace
harrylabsj

Appliance Failure Troubleshooting Log

by haidong · GitHub ↗ · v1.0.1 · MIT-0
cross-platform ✓ Security Clean
86
Downloads
0
Stars
0
Active Installs
2
Versions
Install in OpenClaw
/install appliance-failure-troubleshooting-log
Description
Creates a repair-ready appliance failure log with symptoms, timing, model details, error codes, safe checks, photo evidence, warranty questions, and technici...
README (SKILL.md)

Appliance Failure Troubleshooting Log

Overview

Appliance Failure Troubleshooting Log helps a user organize an appliance problem before contacting a landlord, warranty provider, manufacturer, or repair technician. It turns scattered observations into a clear incident log: what failed, when it happens, what evidence exists, what safe user-level checks were tried, and what questions need answers.

This skill does not diagnose appliance failures or provide risky repair instructions. It supports documentation, communication, and preparation only.

When to Use

Use this skill when the user is dealing with:

  • A refrigerator, washer, dryer, dishwasher, oven, HVAC unit, water heater, microwave, or other household appliance behaving strangely
  • Intermittent symptoms that are hard to explain to a technician
  • Error codes, noises, leaks, smells, lights, temperature changes, or performance problems
  • Warranty, landlord, or service-call preparation
  • A need to track attempted fixes, costs, follow-ups, and repair promises

Trigger phrases: "help me log an appliance problem", "appliance troubleshooting log before repair", "prepare for appliance repair call", "track this washer issue", "what should I tell the technician"

Required Inputs

Ask for what the user knows:

  • Appliance type, brand, model number, serial number, age, and location
  • Warranty, lease, or service plan status if known
  • Main symptom in plain language
  • When the issue started and how often it happens
  • Error codes, lights, sounds, smells, leaks, temperatures, or unusual behavior
  • Safe checks already tried, such as resetting a breaker, cleaning a filter, checking a door seal, or confirming power
  • Photos or videos the user can capture safely

If the user reports a hazard, shift to safety guidance and professional help instead of routine logging.

Workflow

Step 1 - Identify the Appliance

Capture appliance type, brand, model, serial number, age, purchase date, installation date, location, and warranty or landlord responsibility if known. Mark unknown fields clearly.

Step 2 - Describe the Symptom Plainly

Write a clear symptom summary in the user's words. Include what the appliance should do, what it is doing instead, and whether the problem is constant or intermittent.

Step 3 - Build the Incident Timeline

Record dates, times, frequency, duration, and conditions. Include context such as load size, cycle, temperature setting, recent power outage, weather, new installation, maintenance, or heavy use.

Step 4 - Capture Observable Details

Log evidence that can help a repair conversation:

  • Error codes or indicator lights
  • Sounds, vibration, smells, smoke, sparks, or heat
  • Leaks, moisture, frost, food temperature, drainage, or residue
  • Photos or videos to capture safely
  • Screenshots of app alerts or manuals if already available

Step 5 - List Safe User-Level Checks

Document only low-risk checks the user has already tried or can do without opening sealed panels, handling wiring, moving gas lines, bypassing switches, or defeating safety mechanisms. Examples include checking the plug, confirming settings, cleaning a visible lint screen, checking a filter, or restarting according to the manual.

Step 6 - Create Warranty and Responsibility Questions

Generate questions for the landlord, warranty provider, retailer, manufacturer, or technician. Include proof-of-purchase needs, coverage dates, service fees, exclusions, and who authorizes repairs.

Step 7 - Prepare the Service Call Packet

Produce a concise script and information packet for the call or visit: appliance details, symptom summary, timeline, evidence, safe checks tried, urgency, access notes, and desired next step.

Step 8 - Track Follow-up

Create a follow-up tracker with date contacted, person or company, case number, appointment window, quoted cost, promised action, parts ordered, warranty decision, and next deadline.

Output Format

Use this structure:

  • Appliance Failure Troubleshooting Log
  • Appliance Details:
  • Symptom Summary:
  • Incident Timeline:
  • Observable Evidence:
  • Safe Checks Tried:
  • Photos and Videos to Capture:
  • Warranty or Landlord Questions:
  • Service Call Script:
  • Follow-up Tracker:
  • Safety Notes:

Safety Boundaries

  • Do not instruct the user to open electrical panels, handle wiring, move gas lines, bypass sensors, defeat safety locks, or perform repairs beyond safe user-level checks.
  • If there is gas smell, smoke, sparks, burning odor, active flooding, electrical shock risk, carbon monoxide alarm, or suspected fire risk, tell the user to stop using the appliance and contact emergency services, utility provider, landlord, or a qualified professional as appropriate.
  • Do not claim a diagnosis from symptoms alone.
  • Do not guarantee warranty coverage, refund outcomes, or repair costs.
  • Keep the work to documentation, questions, scripts, and tracking.

Example Prompts

  • "My refrigerator is making a loud buzzing noise and the freezer isn't staying cold. Help me log everything before the repair technician arrives."
  • "The washing machine shows error code E3 and stops mid-cycle. Build me a troubleshooting log with timeline and evidence."
  • "My oven heats unevenly — some spots burn while others stay raw. Help me document symptoms, model details, and warranty questions."

Quality Bar

A strong result gives the user a technician-ready record that reduces vague calls, repeat explanations, and lost warranty details while keeping safety first.

Usage Guidance
This appears safe to use as a documentation aid. Only include appliance, warranty, photos, or landlord details you are comfortable sharing in the chat, and follow the skill’s safety advice to contact professionals or emergency services for gas smell, smoke, sparks, flooding, shock risk, or carbon monoxide concerns.
Capability Analysis
Type: OpenClaw Skill Name: appliance-failure-troubleshooting-log Version: 1.0.1 The skill is a documentation tool designed to help users organize appliance failure details for repair or warranty purposes. It contains no executable code, network requests, or requests for sensitive system data, and it includes explicit safety boundaries to prevent hazardous repair instructions. All files (SKILL.md, skill.json, and ACCEPTANCE.md) are consistent with the stated purpose of creating a structured incident log.
Capability Tags
cryptocan-make-purchases
Capability Assessment
Purpose & Capability
The stated purpose is coherent with the instructions: it organizes appliance symptoms, timelines, evidence, warranty questions, and follow-up notes for repair preparation.
Instruction Scope
The workflow is document-focused and includes explicit safety boundaries against diagnosis, hazardous repair instructions, wiring, gas lines, sealed panels, and bypassing safety mechanisms.
Install Mechanism
There is no install spec, executable code, package dependency, shell command, or install hook in the provided artifacts.
Credentials
The metadata declares no API, no network, and no credentials, which matches the prompt-only document-generation behavior shown in the files.
Persistence & Privilege
The artifacts do not request elevated privileges, account access, background operation, persistent memory, or access to local files beyond user-provided appliance details.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install appliance-failure-troubleshooting-log
  3. After installation, invoke the skill by name or use /appliance-failure-troubleshooting-log
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.1
V2 remediation: add Example Prompts, Clean Scan Evidence, Install-First Success Path
v1.0.0
Initial release of Appliance Failure Troubleshooting Log. - Provides a structured log for appliance issues, including symptom timeline, model details, evidence, and follow-up tracking. - Guides users to record only safe checks, avoiding risky repair actions. - Supports preparation for technician visits, warranty claims, and landlord communications. - Emphasizes clear documentation to streamline repair or support calls. - Includes strong safety warnings; directs users to seek professional help for hazards.
Metadata
Slug appliance-failure-troubleshooting-log
Version 1.0.1
License MIT-0
All-time Installs 0
Active Installs 0
Total Versions 2
Frequently Asked Questions

What is Appliance Failure Troubleshooting Log?

Creates a repair-ready appliance failure log with symptoms, timing, model details, error codes, safe checks, photo evidence, warranty questions, and technici... It is an AI Agent Skill for Claude Code / OpenClaw, with 86 downloads so far.

How do I install Appliance Failure Troubleshooting Log?

Run "/install appliance-failure-troubleshooting-log" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Appliance Failure Troubleshooting Log free?

Yes, Appliance Failure Troubleshooting Log is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does Appliance Failure Troubleshooting Log support?

Appliance Failure Troubleshooting Log is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Appliance Failure Troubleshooting Log?

It is built and maintained by haidong (@harrylabsj); the current version is v1.0.1.

💬 Comments