strace

Trace system calls and signals of a process to diagnose OS-level issues.

6|1|Updated Feb 16, 2026
One-click install
npx skills add https://github.com/L3DigitalNet/Claude-Code-Plugins --skill strace
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: strace
Source: https://github.com/L3DigitalNet/Claude-Code-Plugins/tree/main/plugins/linux-sysadmin/skills/strace
Command: npx skills add https://github.com/L3DigitalNet/Claude-Code-Plugins --skill strace

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps diagnose why a process fails to open files, connect to sockets, or behaves unexpectedly at the OS boundary by tracing its system calls and signals.

Core Features & Use Cases

  • System Call Tracing: Monitor all system calls made by a process.
  • Signal Monitoring: Observe signals sent to or received by a process.
  • Use Case: When a command like curl https://example.com fails with a network error, strace can reveal the exact connect() call that failed and why.

Quick Start

Use the strace skill to trace system calls for the command ls -l.

Frequently Asked Questions about strace

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

FAQPage Schema
How do I trace system calls to diagnose why a process fails to open files?

Tracing system calls allows you to monitor OS-level interactions to pinpoint file access errors. By tracing syscalls, you can observe the exact open call that fails and diagnose the underlying boundary issue.

How can I debug network connection failures using system call tracing?

System call tracing reveals network connection failures by showing failed socket operations. When commands like curl fail, tracing exposes the exact connect call that failed and why at the OS boundary.

Do I need the strace binary installed to trace process signals and syscalls?

Yes, you need the strace binary installed on your system to trace process signals and syscalls. This binary provides the core functionality required to monitor system calls and signals made by a process.

What is the best way to find out why a Linux command behaves unexpectedly?

Tracing system calls is the best way to find out why a Linux command behaves unexpectedly. It helps diagnose unexpected process behavior by observing its system calls and signals at the OS boundary.

Can I monitor signals received by a process during system call tracing?

Yes, you can monitor signals received by a process during system call tracing. The tracing mechanism monitors both the system calls made by a process and the signals sent to or received by it.