log-analyze — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited log-analyze (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
log-sleuth is an observability toolkit for analyzing log files. It detects patterns and anomalies in logs, provides structured search across log data, recommends logging best practices, and correlates events across multiple services for distributed debugging.
Activate this skill when the user asks to:
Analyzes log files to detect patterns, recurring errors, anomalies, and trends. Produces a summary report with error frequency, timeline analysis, and root cause suggestions.
Use when: The user wants to understand what is happening in their logs, find the most common errors, identify anomalies, or get a high-level overview of system behavior from log data.
Searches log files using structured queries with filters for log level, timestamp ranges, service names, request IDs, and custom field values. Supports regex patterns and full-text search.
Use when: The user wants to find specific log entries, filter logs by severity or time window, trace a request by ID, or search for specific error messages.
Analyzes the codebase's logging practices and provides actionable recommendations for improvement. Checks for missing error context, inconsistent log levels, unstructured log formats, and missing correlation IDs.
Use when: The user wants to improve their logging strategy, adopt structured logging, ensure adequate observability coverage, or follow logging best practices.
Correlates log events across multiple services using request IDs, timestamps, and causal relationships. Builds a timeline of events across service boundaries for distributed system debugging.
Use when: The user needs to trace a request across microservices, debug a distributed system issue, or understand the sequence of events across multiple services during an incident.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.