Skill

log-agent-issue

Fire-and-forget structured issue logger for subagents

Install

Run in your terminal

npx claudepluginhub nathanvale/side-quest-marketplace-old --plugin log-agent-issue

Tool Access

This skill is limited to using the following tools:

Bash

Skill Content

Similar Skills

cache-components

Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.

cache-components

138.7k

claude-opus-4-5-migration

2 files

Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.

claude-opus-4-5-migration

83.2k

bmad-brainstorming

11 files

Facilitates interactive brainstorming sessions using diverse creative techniques and ideation methods. Activates when users say 'help me brainstorm' or 'help me ideate'.

bmad-pro-skills

43.8k

Stats

Parent Repo Stars4

Parent Repo Forks0

Last CommitJan 29, 2026

Actions

View Source View Plugin View on GitHub View README

How to Log

Pipe a JSON payload to the script via Bash with run_in_background: true:

echo '{"agentId":"<your-agent-id>","issues":[{"type":"error","message":"<what happened>","toolName":"<tool>","context":{"key":"value"},"suggestion":"<how to fix>"}]}' | bun ${CLAUDE_PLUGIN_ROOT}/src/log-issue.ts "${CLAUDE_SESSION_ID}" 2>/dev/null

Payload Shape

{ "agentId": "triage-worker", "issues": [ { "type": "error | warning | info", "message": "Human-readable description", "toolName": "optional — MCP tool that failed", "filePath": "optional — file involved", "context": "optional — object with extra details", "suggestion": "optional — remediation hint" } ] }

Rules

Always use run_in_background: true — never block on logging

Always include 2>/dev/null — silent failure, never interrupt workflow

Keep messages concise — one sentence, actionable

Batch related issues — use the issues array, don't make multiple calls

The script adds timestamp and sessionId automatically

Log Agent Issue

Structured issue logger for subagents. Appends JSONL entries to ~/.claude/logs/agent-issues.jsonl.

When to Log

Log issues when you encounter:

error — Tool failures, timeouts, unexpected exceptions
warning — Skipped steps, degraded results, fallback paths taken
info — Notable events worth tracking (optional, use sparingly)

How to Log

Pipe a JSON payload to the script via Bash with run_in_background: true:

echo '{"agentId":"<your-agent-id>","issues":[{"type":"error","message":"<what happened>","toolName":"<tool>","context":{"key":"value"},"suggestion":"<how to fix>"}]}' | bun ${CLAUDE_PLUGIN_ROOT}/src/log-issue.ts "${CLAUDE_SESSION_ID}" 2>/dev/null

Payload Shape

{
  "agentId": "triage-worker",
  "issues": [
    {
      "type": "error | warning | info",
      "message": "Human-readable description",
      "toolName": "optional — MCP tool that failed",
      "filePath": "optional — file involved",
      "context": "optional — object with extra details",
      "suggestion": "optional — remediation hint"
    }
  ]
}

Rules

Always use run_in_background: true — never block on logging
Always include 2>/dev/null — silent failure, never interrupt workflow
Keep messages concise — one sentence, actionable
Batch related issues — use the issues array, don't make multiple calls
The script adds timestamp and sessionId automatically