gardener-inbox-error-reporting

Capture and log execution failure transcripts from automated agent workflows into a content-addressed journal.

3|2|Updated May 12, 2026

Search Tags:#automation #git #debugging #logging #resilience #error-reporting

Ready to run

npx skills add https://github.com/kriscendobot/garden --skill gardener-inbox-error-reporting

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gardener-inbox-error-reporting
Source: https://github.com/kriscendobot/garden/tree/main/skills/gardener-inbox-error-reporting
Command: npx skills add https://github.com/kriscendobot/garden --skill gardener-inbox-error-reporting

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill solves the issue of silent failures in automated agent workflows by ensuring that unexpected errors are captured, logged, and made visible to human maintainers.

Core Features & Use Cases

Automated Error Trapping: Automatically traps ERR and EXIT signals in worker scripts to capture failure transcripts.
Durable Reporting: Commits failure logs to a content-addressed journal branch, ensuring they are reachable off-host for remote debugging.
Use Case: When a background worker script fails during a GitHub PR review, this skill captures the exact execution transcript and appends a detailed report to the gardener's inbox, allowing the maintainer to inspect the failure immediately.

Quick Start

Invoke the report-error script with the path to your failed transcript and the relevant lane identifier to log the error to the gardener inbox.

Frequently Asked Questions about gardener-inbox-error-reporting

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

FAQPage Schema

How do I capture silent execution failures in automated agent workflows?▼

To capture silent execution failures in automated agent workflows, you can trap ERR and EXIT signals in worker scripts to automatically generate and log detailed execution transcripts for debugging.

What is the best way to log background worker error transcripts for remote debugging?▼

Logging error transcripts for remote debugging is best achieved by committing failure logs to a content-addressed git journal branch, ensuring records remain reachable and durable across distributed host environments.

How do I automate error reporting when a GitHub PR review script fails?▼

Automating error reporting for failed GitHub PR review scripts requires trapping execution failures and appending the resulting transcript to a centralized inbox, allowing maintainers to inspect the failure immediately.

Does this automated error trapping require any external logging dependencies?▼

Automated error trapping does not require external logging dependencies because it implements robust error handling entirely through git-based storage and internal script signal capturing.

Why should I use a content-addressed journal for distributed error logging?▼

Using a content-addressed journal for distributed error logging ensures that committed failure transcripts are immutable and reachable off-host, providing reliable state tracking across distributed worker environments.

How do I report a failed execution transcript to a centralized inbox?▼

To report a failed execution transcript to a centralized inbox, invoke the report-error script with the path to the failed transcript file and the relevant lane identifier to commit the log.