rdk-log-forensics

Extract kernel errors, failed systemd units, and coredump evidence from RDK device logs.

3|Updated Aug 6, 2026
One-click install
npx skills add https://github.com/D-Robotics/rdk-skills --skill rdk-log-forensics-d-robotics
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: rdk-log-forensics
Source: https://github.com/D-Robotics/rdk-skills/tree/main/skills/rdk-log-forensics
Command: npx skills add https://github.com/D-Robotics/rdk-skills --skill rdk-log-forensics-d-robotics

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? When a program crashes, a board reboots unexpectedly, or a service refuses to start on a D-Robotics RDK device, developers waste time pasting raw logs back and forth. This Skill turns scattered signals in dmesg, journalctl, and /var/crash into a structured evidence list for root-cause analysis. ## Core Features & Use Cases - Structured log collection: Runs a read-only script that counts kernel err-level messages, lists failed systemd units, detects coredumps and /var/crash files, and checks whether the last boot shut down cleanly, outputting JSON. - Guided root-cause workflows: Provides per-symptom playbooks for crashed services, sudden reboots, and user-pasted errors, with handoffs to sibling skills for thermal, memory, and model-inference issues. - Use Case: A user's board rebooted overnight. The agent runs the collector, finds last_boot.clean is false and a thermal error in kernel.recent_errors, then presents an evidence-to-hypothesis-to-verification chain instead of guessing. ## Quick Start Ask the agent to check the board's logs for clues about a crash or unexpected reboot and summarize the evidence.

Frequently Asked Questions about rdk-log-forensics

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

FAQPage Schema
How do I find why my RDK board rebooted unexpectedly?▼

Run the collect_logs.sh script on the board and inspect last_boot.clean and kernel.recent_errors. A false clean flag plus thermal, oops, or OOM keywords in recent kernel errors points to the likely cause, which is then handed to the appropriate diagnostic skill.

How do I debug a systemd service that will not start on Linux?▼

Start from the failed_units list in the script output, then run systemctl status and journalctl -u for that unit to pull the first ERROR line. The skill also searches official FAQ documentation for the same error message.

Does log collection require root permissions?▼

Full dmesg and journalctl history typically requires root. When run without privileges, the script reports kernel.readable as false and marks unavailable fields as null instead of fabricating empty results.

Can this skill analyze coredump files with gdb?▼

No. It only detects the presence of coredumps via coredumpctl and /var/crash file counts. Application-level core file analysis with gdb is out of scope and should be done on a development machine.

What is the difference between log forensics and live diagnostics?▼

Log forensics extracts historical crash evidence from dmesg, journalctl, and coredumps after an incident. Live performance snapshots such as temperature and BPU usage belong to the rdk-diagnostic skill, and memory measurement belongs to rdk-memory-audit.