error-logging

Log command failures and Python tracebacks in append-only JSONL format.

Updated Jun 4, 2025
One-click install
npx skills add https://github.com/expectedparrot/vernon --skill error-logging
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: error-logging
Source: https://github.com/expectedparrot/vernon/tree/main/macaw/ep-agent/skills/error-logging
Command: npx skills add https://github.com/expectedparrot/vernon --skill error-logging

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill provides a standardized protocol for logging errors encountered during automated tasks, ensuring that all issues are captured systematically for later review and resolution.

Core Features & Use Cases

  • Structured Error Recording: Logs errors in an append-only JSONL format for easy parsing and analysis.
  • Contextual Information: Captures essential details like timestamps, error messages, commands executed, and attempted fixes.
  • Use Case: When a script fails due to an unexpected output, this Skill ensures the exact error, the command that caused it, and the output are recorded before any fix is attempted, facilitating efficient debugging.

Quick Start

Log an error encountered while running a command by appending a JSON object to the errors.jsonl file.

Frequently Asked Questions about error-logging

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

FAQPage Schema
How do I log Python tracebacks and command failures in JSONL format for debugging?

Record unexpected script outputs in an append-only JSONL log by appending a JSON object with contextual details, the command executed, the output received, and any attempted fixes to ensure systematic debugging.

What is the best way to systematically capture missing file errors during task execution?

Capture missing file errors systematically by using an append-only JSONL logging protocol that records the exact error, the command that caused it, and the resulting output before any fix is attempted, facilitating efficient debugging.

Does append-only JSONL error logging work for automated processes without external dependencies?

Yes, append-only JSONL error logging requires no external dependencies. It provides a standardized protocol for capturing command failures and surprising behavior during task execution using a simple file append mechanism.

Why should I record fix attempts and command context when troubleshooting script failures?

Recording fix attempts and command context when troubleshooting script failures provides essential historical details for post-execution review. This systematic capture ensures the exact error and attempted resolutions are available for analysis.

What limitations should I expect when using JSONL files for error logging in scripting?

When using JSONL files for error logging in scripting, limitations include the append-only format lacking built-in management or rotation. The system relies entirely on the user to provide detailed context, commands, and fix attempts for effective review.