auto-troubleshooter

Name: auto-troubleshooter
Availability: InStock
Author: Star

Detect new error patterns in system logs and append drafts to TROUBLESHOOTING.md.

Updated Aug 27, 2026

Search Tags:#automation #debugging #error detection #troubleshooting #log analysis #system monitoring

Ready to run

npx skills add https://github.com/WangK0221/OpenClaw_Shrimp --skill auto-troubleshooter-wangk0221

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: auto-troubleshooter
Source: https://github.com/WangK0221/OpenClaw_Shrimp/tree/main/skills/auto-troubleshooter
Command: npx skills add https://github.com/WangK0221/OpenClaw_Shrimp --skill auto-troubleshooter-wangk0221

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automatically identifies and documents new, recurring error patterns found in system logs, preventing issues from being overlooked and streamlining the troubleshooting process.

Core Features & Use Cases

Automated Log Analysis: Scans critical log files for new error signatures.
Issue Documentation: Appends newly detected errors to a central TROUBLESHOOTING.md file with a proposed structure for investigation.
Notification: Alerts relevant channels about newly identified issues.
Use Case: When a new, unhandled exception occurs in the system, this Skill will detect it, add it to the troubleshooting log, and notify the engineering team so it can be addressed promptly.

Quick Start

Run the auto-troubleshooter skill to scan logs for new issues.

Frequently Asked Questions about auto-troubleshooter

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate log analysis for new error patterns?▼

Automated log analysis scans system logs like wrapper_lifecycle.log and daily memory logs to detect new error signatures, normalizes them, and compares them against existing documented issues to identify undocumented problems.

What is the best way to detect undocumented errors in system logs?▼

Detecting undocumented errors involves comparing normalized error signatures from logs against existing documented issues. When new recurring patterns are found, draft entries are appended to a central troubleshooting file for investigation.

How do I append new issues to a troubleshooting log automatically?▼

You can append new issues automatically by running an error detection scan that analyzes logs for undocumented signatures. Newly detected errors are appended to TROUBLESHOOTING.md with a proposed structure for investigation.

Can I receive notifications when new error patterns are detected?▼

Yes, notifications are sent via Feishu card tool upon the discovery of undocumented errors. This alerts relevant channels about newly identified issues so the engineering team can address them promptly.

Does this automated troubleshooting tool require any external dependencies?▼

No dependencies are required. The Skill operates independently using scripts to analyze wrapper_lifecycle.log and daily memory logs for error detection without needing external packages.