linux-forensics

Collect Linux forensic evidence and produce NIST SP 800-86 findings documents.

Updated Mar 11, 2026
One-click install
npx skills add https://github.com/robit-man/transcribe-cli --skill linux-forensics
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: linux-forensics
Source: https://github.com/robit-man/transcribe-cli/tree/main/.claude/skills/linux-forensics
Command: npx skills add https://github.com/robit-man/transcribe-cli --skill linux-forensics

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the process of collecting and analyzing forensic data from Linux systems, regardless of their distribution family, ensuring a consistent and thorough investigation.

Core Features & Use Cases

  • Distribution Agnostic: Detects and adapts to Debian/Ubuntu, RHEL/CentOS/Rocky, and SUSE families.
  • Comprehensive Evidence Collection: Gathers data on package integrity, authentication logs, scheduled tasks, persistence mechanisms, network state, and kernel information.
  • Use Case: When a production server shows signs of compromise, this skill can be triggered to collect critical forensic data for analysis, helping to identify the scope and nature of the incident.

Quick Start

Run linux forensics on the remote host [email protected] to investigate.

Frequently Asked Questions about linux-forensics

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

FAQPage Schema
How do I automate Linux incident response on a compromised production server?

Automate Linux incident response by triggering a structured collection process that gathers forensic evidence including package integrity, authentication logs, and network state to identify the scope of compromise.

Does Linux forensic analysis work across different distributions like Debian, RHEL, and SUSE?

Yes, Linux forensic analysis adapts collection and verification procedures to detected distribution families like Debian, RHEL, and SUSE, ensuring consistent evidence gathering regardless of the system distribution.

What evidence does a Linux forensic investigation collect for system analysis?

A Linux forensic investigation collects evidence including package integrity, authentication logs, scheduled tasks, persistence mechanisms, network state, and kernel information to produce a findings document.

How are forensic findings documented during Linux incident response?

Forensic findings are documented by aligning the collected evidence and analysis results with NIST SP 800-86, producing a structured findings document for incident response and system analysis.

Can I use this to investigate scheduled tasks and persistence mechanisms on Linux?

Yes, you can investigate scheduled tasks and persistence mechanisms on Linux as the forensic collection process specifically gathers data on these elements to identify how an attacker maintained access.

What's the best way to collect network state and kernel information during a Linux security incident?

The best way to collect network state and kernel information during a Linux security incident is to run an automated forensic collection script that captures this data alongside authentication logs and package integrity.