Skip to content
Skills Library
Programming · Analysis

analyzing-logs

/analyzing-logs

Analyze application logs for performance insights and issue detection including slow requests, error patterns, and resource usage. Use when troubleshooting performance issues or debugging errors. Trigger with phrases like "analyze logs", "find slow requests", or "detect error patterns".

Licence
MIT
Last repository change
26.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
6
Scripts
2
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 26.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What to check before installing
  • 2 scripts in this package. Review them before installing, as Claude may execute them.

Scripts: scripts/aggregate_logs.py, scripts/analyze_log_file.py

What it does and when to use it

Analyze application logs for performance insights and issue detection including slow requests, error patterns, and resource usage. Use when troubleshooting performance issues or debugging errors. Trigger with phrases like "analyze logs", "find slow requests", or "detect error patterns".

Triggers from the description

analyze logsfind slow requestsdetect error patterns
Original author description

Analyze application logs for performance insights and issue detection including slow requests, error patterns, and resource usage. Use when troubleshooting performance issues or debugging errors. Trigger with phrases like "analyze logs", "find slow requests", or "detect error patterns".

How it works

  1. Overview
  2. How It Works
  3. When to Use This Skill
  4. Examples
  5. Best Practices
  6. Integration
  7. Prerequisites
  8. Instructions
  9. Output
  10. Error Handling
Original SKILL.md headings · 97 lines, 531 words
SKILL.md preview
---
name: analyzing-logs
description: Analyze application logs for performance insights and issue detection
  including slow requests, error patterns, and resource usage. Use when troubleshooting
  performance issues or debugging errors. Trigger with phrases like "analyze logs",
  "find slow requests", or "detect error patterns".
version: 1.24.0
allowed-tools: Read, Write, Bash(logs:*), Bash(grep:*), Bash(awk:*), Grep
license: MIT
author: Jeremy Longshore <jeremy@intentsolutions.io>
tags:
- performance
- debugging
- analyzing-logs
compatibility: Designed for Claude Code
---
# Log Analysis Tool

Analyze application logs to identify slow requests, recurring error patterns, and resource usage anomalies with structured reporting and optimization recommendations.

## Overview

This skill empowers Claude to automatically analyze application logs, pinpoint performance bottlenecks, and identify recurring errors. It streamlines the debugging process and helps optimize application performance by extracting key insights from log data.

## How It Works

1. **Initiate Analysis**: Claude activates the log analysis tool upon detecting relevant trigger phrases.
2. **Log Data Extraction**: The tool extracts relevant data, including timestamps, request durations, error messages, and resource usage metrics.
3. **Pattern Identification**: The tool identifies patterns such as slow requests, frequent errors, and resource exhaustion warnings.
4. **Report Generation**: Claude presents a summary of findings, highlighting potential performance issues and optimization opportunities.

## When to Use This Skill

This skill activates when you need to:

- Identify performance bottlenecks in an application.
- Debug recurring errors and exceptions.
- Analyze log data for trends and anomalies.
- Set up structured logging or log aggregation.

## Examples

### Example 1: Identifying Slow Requests

User request: "Analyze logs for slow requests."

The skill will:

1. Activate the log analysis tool.
2. Identify requests exceeding predefined latency thresholds.
3. Present a list of slow requests with corresponding timestamps and durations.

### Example 2: Detecting Error Patterns

User request: "Find error patterns in the application logs."

The skill will:

1. Activate the log analysis tool.
2. Scan logs for recurring error messages and exceptions.
3. Group similar errors and present a summary of error frequencies.

## Best Practices

- **Log Level**: Ensure appropriate log levels (e.g., INFO, WARN, ERROR) are used to capture relevant information.
- **Structured Logging**: Implement structured logging (e.g., JSON format) to facilitate efficient analysis.
- **Log Rotation**: Configure log rotation policies to prevent log files from growing excessively.

## Integration

This skill can be integrated with other tools for monitoring and alerting. For example, it can be used in conjunction with a monitoring plugin to automatically trigger alerts based on log analysis results. It can also work with deployment tools to rollback deployments when critical errors are detected in the logs.

## Prerequisites

- Access to application log files in ${CLAUDE_SKILL_DIR}/logs/
- Log parsing tools (grep, awk, sed)
- Understanding of application log format and structure
- Read permissions for log directories

## Instructions

1. Identify log files to analyze based on timeframe and application
2. Extract relevant data (timestamps, durations, error messages)
3. Apply pattern matching to identify slow requests and errors
4. Aggregate and group similar issues
5. Generate analysis report with findings and recommendations
6. Suggest optimization opportunities based on patterns

## Output

- Summary of slow requests with response times
- Error frequency reports grouped by type
- Resource usage patterns and anomalies
- Performance bottleneck identification
- Recommendations for log improvements and optimizations

## Error Handling

If log analysis fails:

- Verify log file paths and permissions
- Check log format compatibility
- Validate timestamp parsing
- Ensure sufficient disk space for analysis
- Review log rotation configuration

## Resources

- Application logging best practices
- Structured logging format guides
- Log aggregation tools documentation
- Performance analysis methodologies
Files in this package (6)
  • SKILL.md 4 KB
  • assets/README.md 1 KB
  • references/README.md 1 KB
  • scripts/README.md 1 KB
  • scripts/aggregate_logs.py 3 KB
  • scripts/analyze_log_file.py 5 KB

Versions

RepositoryScoreLicence
This page · jeremylongshore/tons-of-skills-marketplace100MIT
HelixDevelopment/agent100MIT

Identical content appears in 1 other GitHub folders. We show one copy with the highest score.

Database snapshot: 13.11.2026 · package version b6c0173e1849 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100analyze-logs
    Analyze application logs from the .evlog/logs/ directory. Use when debugging errors, investigating slow requests, understanding request patterns, or answering questions about application behavior. Reads structured NDJSON wide events written by evlog's file system drain.
  • 100analyze-logs
    Analyze application logs from the .evlog/logs/ directory. Use when debugging errors, investigating slow requests, understanding request patterns, or answering questions about application behavior. Reads structured NDJSON wide events written by evlog's file system drain.
  • 100analyze-logs
    Analyze application logs from the .evlog/logs/ directory. Use when debugging errors, investigating slow requests, understanding request patterns, or answering questions about application behavior. Reads structured NDJSON wide events written by evlog's file system drain.
  • 100analyze-logs
    Analyze application logs from the .evlog/logs/ directory. Use when debugging errors, investigating slow requests, understanding request patterns, or answering questions about application behavior. Reads structured NDJSON wide events written by evlog's file system drain.
  • 100detecting-memory-leaks
    Detect potential memory leaks and analyze memory usage patterns in code. Use when troubleshooting performance issues related to memory growth or identifying leak sources. Trigger with phrases like "detect memory leaks", "analyze memory usage", or "find memory issues".
  • 100detecting-memory-leaks
    Detect potential memory leaks and analyze memory usage patterns in code. Use when troubleshooting performance issues related to memory growth or identifying leak sources. Trigger with phrases like "detect memory leaks", "analyze memory usage", or "find memory issues".

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.