log-tail

Stream recent systemd journal logs for specified service units.

Updated Mar 7, 2026
One-click install
npx skills add https://github.com/billyfranklim1/claude-skills --skill log-tail
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: log-tail
Source: https://github.com/billyfranklim1/claude-skills/tree/main/plugins/log-tail/skills/log-tail
Command: npx skills add https://github.com/billyfranklim1/claude-skills --skill log-tail

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Quickly access recent systemd journal entries for a specific service to speed up debugging, incident triage, and runtime diagnostics without manually constructing journalctl commands.

Core Features & Use Cases

  • Service-filtered log viewing: Display recent journal logs for a named systemd unit with control over the number of lines shown.
  • Real-time following: Attach to a service's live log stream to monitor events as they occur during testing or incident response.
  • Use Case: Inspect the last 50 lines of a crashed web service and follow new logs while reproducing the failure to capture relevant errors.

Quick Start

Run the log-tail command with the unit name to show the last 50 lines and add --follow to stream new entries in real time.

Frequently Asked Questions about log-tail

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

FAQPage Schema
How do I stream recent systemd journal logs for a specific service?

To stream recent systemd journal logs, you can use a tool that runs journalctl with a specified unit name and line count, optionally adding a follow flag to attach to live log output for real-time monitoring.

What is the best way to follow live systemd logs during incident triage?

The best way to follow live systemd logs during incident triage is to attach to the service's live log stream using a follow flag, which displays new journal entries as they occur to help capture relevant errors immediately.

Does viewing journalctl logs for a service require special permissions?

Viewing journalctl logs for a service requires availability of the journalctl command on a systemd-based Linux host and permissions to read the system journal to access the specified service unit output.

Can I limit the number of lines shown when debugging systemd service logs?

You can limit the number of lines shown when debugging systemd service logs by passing an argument for the desired line count, allowing you to inspect only the recent output instead of the entire journal history.

Why use a command wrapper instead of manually constructing journalctl commands for debugging?

Using a command wrapper instead of manually constructing journalctl commands speeds up debugging and runtime diagnostics by quickly accessing recent journal entries for a specific service without remembering complex command syntax.

Can I monitor system journal logs for multiple units on Linux?

Monitoring system journal logs is currently designed to target a specified single service unit at a time on systemd-based Linux hosts, filtering output to show recent lines or follow live entries for that specific service.