What problem does it solve?
This Skill helps engineers rapidly diagnose agent reasoning failures by mapping observed symptoms to the exact kernel phases and source files to inspect, avoiding broad codebase exploration and guesswork.
Core Features & Use Cases
- Symptom → Phase Mapping: A concise table that maps common failure symptoms (missing tool calls, loops, silent failures, context compaction, final-answer gating) to the responsible kernel phase and files.
- Targeted Grep Commands: Ready-to-run grep commands tailored to each symptom to quickly find related code and configuration.
- Debug Workflow & Tips: Practical steps including enabling full model I/O logging and choosing whether to inspect state.messages[] or state.steps[] for root-cause analysis.
- Use Case: When an agent never calls tools, use the mapping to check context-builder, guard chains, and FC schema generation instead of searching the entire repository.
Quick Start
Use the kernel-debug guidance to map an observed symptom such as agent never calls tools to the specific kernel phase, files, and grep commands to inspect.
