skills.rest
tonehq
tonehqOFFICIAL
Explore all skills by this author →
GitHub

error-tracker

Parse and analyze .claude/error-log.md entries to diagnose errors by severity and recurring patterns.

11|3|Updated Aug 31, 2025
Search Tags:#debugging#tooling#observability#diagnostics#root-cause#log-analysis#error-tracking
One-click install
npx skills add https://github.com/tonehq/tone --skill error-tracker-tonehq
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: error-tracker
Source: https://github.com/tonehq/tone/tree/main/frontend/.claude/skills/error-tracker
Command: npx skills add https://github.com/tonehq/tone --skill error-tracker-tonehq

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a centralized mechanism to read, interpret, and diagnose errors across skills by parsing and organizing error logs, enabling faster root-cause analysis and reliability improvements.

Core Features & Use Cases

  • View error history with timestamps and resolutions to understand failure frequency.
  • Detect recurring patterns and categorize issues by severity, file, or skill.
  • Generate actionable insights and recommendations to reduce downtime and improve observability.

Quick Start

Run the error-tracker to view summaries, search for keywords, clear resolved issues, or fetch the most recent entries.

Frequently Asked Questions about error-tracker

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

FAQPage Schema
How do I parse and analyze centralized error logs for root-cause analysis?▼

You can track and triage skill errors instantly by applying a mode-driven workflow to parse centralized error logs. This approach enforces structured reading of the .claude/error-log.md format to deliver actionable reports with severity and recurring patterns.

How do I detect recurring error patterns and categorize them by severity?▼

To categorize issues by severity, file, or skill, parse the centralized error log to detect recurring patterns. Analyzing historical entries with timestamps reveals failure frequency and helps prioritize triage for development and testing pipelines.

Can I clear resolved issues from the error log during development pipelines?▼

Yes, you can clear resolved issues from the error log using the clear-resolved mode within the mode-driven workflow. This maintains a concise error history by removing fixed entries while preserving active unresolved errors for ongoing diagnostics.

What is the best way to search for specific keywords across multiple skill error logs?▼

The best way to search for specific keywords across multiple skill error logs is to apply the search mode within the mode-driven workflow. This queries the centralized .claude/error-log.md file to filter entries and surface targeted diagnostic insights.

Does error tracking work without external dependencies or observability platforms?▼

Yes, error tracking works without external dependencies or observability platforms. It operates independently by parsing the local .claude/error-log.md format to generate actionable insights and recommendations for improving skill reliability.

Related Skills

Explore More Software Engineering Skills→
OmarHosamCodesOmarHosamCodes
1

wiki-setup

Initialize and configure an Obsidian wiki vault with standardized folders and templates.

Community
Intermediate
HexAI-incHexAI-inc

debug-mastery

Enforce a four-phase debugging process for root cause investigation and resolution.

Official
Advanced
koralliskorallis
90

monitoring-observability

Implement monitoring, logging, metrics, and tracing with Grafana and Sentry.

Community
Intermediate
gil-kapelgil-kapel
2

error-detective

Analyze log and code error patterns to identify root causes across distributed systems.

Community
Advanced