Works with the AI Agents you already use
Syslog Analyzer
Automated Linux syslog and journalctl parser for detecting security breaches, hardware failures, and service crashes.
$2.99
Syslog Analyzer
Example session with this skill installed
Analyze these logs from web-server-01 and db-prod for the last 24 hours. I suspect an SSH brute force attack and I'm seeing service instability. Output a summary table.
- Read your context and instructions
- Compiled the syslog analyzer
I have analyzed the provided logs from web-server-01 and db-prod. The analysis identified a high-volume SSH brute force attempt originating from three distinct IPs and a recurring OOM kill event affecting the database service.
System Log Analysis Summary
| Category | Source Host | Event Type | Details | Severity |
|---|---|---|---|---|
| Security | web-server-01 | SSH Brute Force | 1,420 failed attempts from 192.168.1.45 (user: root) | High |
| Security | web-server-01 | Suspicious Login | User 'admin' logged in after 12 failures from 45.67.8.12 | Critical |
| Kernel | db-prod | OOM Kill | Process 'postgres' (PID 4021) killed by kernel | High |
| Service | web-server-01 | Restart Loop | nginx.service restarted 14 times in 60 minutes | Medium |
| System | db-prod | Disk I/O | /dev/sda1: sector 450212 read error | High |
| Auth | web-server-01 | Sudo Failure | User 'dev-temp' not in sudoers file | Low |
Log Volume Insights
- Noisiest Program:
sshd(82% of total volume) - Peak Activity: 03:00 - 04:00 UTC (4,200 events)
- Log Gaps: None detected in the last 24 hours.
Next steps
- Block IP
192.168.1.45and45.67.8.12at the firewall level immediately. - Investigate memory limits for the Postgres process on
db-prodto prevent further OOM kills. - Check Nginx configuration on
web-server-01for syntax errors or failing upstream dependencies.
Connects securely to your tools. The creator never sees your data.
About this skill
Manually auditing Linux logs is slow and error-prone. This skill automates the extraction of critical system events from massive log files, surfacing only what requires immediate attention. It handles standard syslog formats and modern JSON exports to detect security threats and hardware failures.
What it does
- Security Audit identifies SSH brute-force sources, targeted usernames, and successful logins following multiple failures.
- Privilege Monitoring tracks all sudo usage, including unauthorized attempts and users not present in the sudoers file.
- Hardware Health flags kernel OOM kills, disk I/O errors, filesystem corruption, and NIC link flaps.
- Service Stability reports on systemd services stuck in restart loops or unexpected crashes.
- Anomaly Detection finds gaps in logging history and calculates volume spikes by program or hour.
How it works
- Input Collection accepts standard syslog files, auth.log, or
journalctl -o jsonexports. - Context Setting allows you to define years for RFC 3164 logs or set specific time windows with
--sinceand--until. - Threshold Tuning lets you configure brute-force sensitivity and gap detection parameters.
- Data Output generates a summary of findings or a structured CSV for external reporting.
Frameworks & tools
The skill utilizes Python-based parsing logic compatible with RFC 3164, RFC 5424, and rsyslog high-precision formats. It works with standard Linux log locations and systemd journal exports.
Why this beats prompting it yourself
Generic LLM prompts struggle with the high-volume noise of system logs and often hallucinate timestamps or log sequences. This skill uses specific parsing rules for systemd and syslog standards to ensure every detected OOM kill or SSH attack is grounded in real log lines.
Use cases
- Incident Response to quickly find the root cause of a service outage or crash.
- Security Triage to identify IP addresses performing coordinated brute-force attacks.
- Daily Review to monitor sudo escalations and disk health across multiple hosts.
Known limitations
RFC 3164 logs lack year data and require manual year flagging. Large log files require local Python execution for parsing before analysis.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Security.
RFC 3164 logs require a manual --year flag. Log parsing occurs via Python scripts; ensure the environment has the provided analyzer scripts available.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 1 month ago