Locate dev-only agent diagnostics under BRAIN_HOME and correlate them with logs via agentTurnId.
npx skills add https://github.com/cirne/brain-app --skill debug-agent-cirne
Please help me install this Agent Skill. Skill: debug-agent Source: https://github.com/cirne/brain-app/tree/main/.cursor/skills/debug-agent Command: npx skills add https://github.com/cirne/brain-app --skill debug-agent-cirne
Locates brain-app dev-only per-turn agent diagnostics under BRAIN_HOME (JSONL lines per agent turn + small JSON for suggest-repair) and correlates them with structured logs via agentTurnId and session IDs to surface actionable debugging artifacts.
Run the debug-agent workflow to locate and correlate dev-only agent diagnostics with structured logs by agentTurnId and sessionId.
High-intent search queries and answers about installing and using this skill.
You can locate dev-only agent diagnostics by scanning the BRAIN_HOME directory for JSONL files containing per-turn agent data and small JSON files for suggest-repair. This Skill surfaces those autogenerated diagnostic artifacts reliably during local development.
Yes, you can correlate structured logs with agent diagnostics by matching agentTurnId and sessionId across both datasets. This correlation surfaces actionable debugging artifacts across individual agent turns during development.
The on-disk layout consists of JSONL lines recording each agent turn alongside small JSON files for suggest-repair, organized under BRAIN_HOME. The Skill relies on AGENT_DIAGNOSTICS_SCHEMA_VERSION and known file naming schemes to interpret this layout.
This diagnostics approach is strictly dev-only. It is designed to locate autogenerated diagnostic files and diagnose specific agent or LLM tool turns from local logs during development, not in production environments.
Diagnose a specific agent turn by running the debug-agent workflow to locate and correlate dev-only diagnostics with structured logs using agentTurnId and sessionId. This surfaces actionable artifacts tied to that exact turn.
AGENT_DIAGNOSTICS_SCHEMA_VERSION is needed because it ensures the Skill correctly interprets the on-disk file layout and JSONL diagnostics structure. Relying on this version and known naming schemes surfaces relevant artifacts reliably.
openeuler-mirrorAnalyze iBMC out-of-band logs to diagnose server boot failures.
matchojeckiDiagnose and fix Open Mercato standalone app issues through a structured workflow.
krzemienskiAnalyze Shannon log files for session traces, health checks, and audits.
PieroSierraImport markdown content into the raw/ directory of the Second Brain knowledge base.
