inspect-logs

Inspect server and workstation logs for inbound attacks and outbound connections using CrowdSec.

2|Updated Jun 14, 2026
One-click install
npx skills add https://github.com/odysseyalive/claude-watchman --skill inspect-logs-odysseyalive
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: inspect-logs
Source: https://github.com/odysseyalive/claude-watchman/tree/main/skills/grammar/inspect-logs
Command: npx skills add https://github.com/odysseyalive/claude-watchman --skill inspect-logs-odysseyalive

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually hunting through web server, auth, and system logs for attack patterns or suspicious outbound connections is slow and error-prone. This Skill automates that inspection, detecting inbound attack patterns on servers and unexpected outbound connections on workstations, and records findings in a deduplicated journal. ## Core Features & Use Cases - CrowdSec-first detection: Queries CrowdSec alerts and decisions via cscli in alert-only mode, falling back to direct log scanning when CrowdSec is absent. - Profile-aware direction: On servers it hunts inbound attack patterns (auth-failure bursts, 4xx floods); on workstations it compares outbound connections against a network baseline. - Request-rate spike detection: Identifies per-IP request floods exceeding a configurable threshold and journals offenders with a firewall remediation proposal. - Use Case: During a scheduled security audit loop on a Linux web server, the skill scans nginx access logs and sshd auth logs, finds a brute-force cluster from one IP, and journals a security finding with a firewall_deny remediation for operator review. ## Quick Start Ask the AI to run the inspect-logs audit to check this machine's web and auth logs for attack patterns and unexpected outbound connections.

Frequently Asked Questions about inspect-logs

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

FAQPage Schema
How do I detect brute-force attacks in web server logs?▼

The skill scans config-derived web server log paths for repeated 4xx and 401 auth-failure bursts, and checks auth logs via journalctl or platform equivalents. Findings are journaled as security entries with stable fingerprints so re-runs update rather than duplicate.

How does CrowdSec integration work for log analysis?▼

When cscli is available, the skill queries CrowdSec alerts and decisions in alert-only mode, never auto-banning. If CrowdSec is missing, it journals a low-severity config finding recommending installation and falls back to direct log scanning.

Does this log inspection work on macOS and Windows?▼

Yes, the skill branches on the detected platform family. On macOS it uses lsof for connections and the unified log for sshd events; on Windows it uses Get-WinEvent for Security 4625 failed-logon events and Get-NetTCPConnection for connections.

Can the skill block attacking IP addresses automatically?▼

No, the skill is strictly read-only and never blocks or bans. It journals a firewall_deny remediation proposal per offending IP, which a separate operator-confirmed fixer skill applies under review-tier controls.

What happens when log scanning is too heavy for the system?▼

The skill checks I/O pressure before scanning and defers heavy work when the system is loaded, journaling a diagnostic_deferred info entry instead. Rate detection also reads logs incrementally, processing only new lines since the last pass.