Skip to content
cccskills
FreePublished on GitHub

analyzing-logs

Analyze application logs to find slow requests, recurring errors, and unusual resource usage. Group related issues into reports with response times, error frequencies, and recommendations for performance improvements and clearer logging.

OriginalShow the original 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".

Run score Not tested

See how to install

Good for

  • Finding requests that exceed response time thresholds
  • Grouping recurring errors and exceptions
  • Investigating unusual resource usage
  • Reviewing log trends and opportunities for improvement

Files included (6)

  • SKILL.md4.2 KB
  • assets/README.md160 B
  • references/README.md60 B
  • scripts/aggregate_logs.py3.0 KB
  • scripts/analyze_log_file.py4.9 KB
  • scripts/README.md810 B

SKILL.md (original)

Review the instructions the agent will receive before you install.

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

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Add a synthetic-data CI gate for customer-owned Abridge integration code. Test consent handling, note-review handoffs, redaction, and rollback behavior with mocked vendor boundaries, without connecting CI to a live Abridge or EHR tenant.

  • Adding regression checks to an Abridge integration repository
  • Testing consent and note-release handling
  • Checking logs for sensitive data exposure
jeremylongshore/tons-of-skills-marketplace2.9KUpdated Oct 23, 2026

Triage Abridge recording, note review, Epic handoff, and access problems using observed symptoms and approved guidance. Identify the affected workflow stage, organize a minimal timeline, and prepare a redacted escalation record for the responsible team.

  • Separate recording problems from upload failures
  • Investigate note creation delays and editor issues
  • Identify the responsible team for Epic handoff failures
jeremylongshore/tons-of-skills-marketplace2.9KUpdated Oct 23, 2026

Map and review an Abridge clinical documentation workflow from consent and recording through draft review, evidence checks, edits, and final disposition. Keep clinician approval explicit, identify failure exits, and separate verified facts from tenant-specific details and pending approvals.

  • Map a clinical note workflow for a care setting
  • Check where consent and patient identity are verified
  • Review draft notes against linked evidence before sign-off
jeremylongshore/tons-of-skills-marketplace2.9KUpdated Oct 23, 2026

Audit how clinician-reviewed Abridge note sections map into Epic templates and downstream workflows. Use approved test records to document destinations, exceptions, evidence, rollback steps, and a go or no-go decision for a specific environment.

  • Checking Abridge note section mappings to Epic templates
  • Auditing a department’s approved documentation handoff
  • Preparing test evidence and a go or no-go decision
jeremylongshore/tons-of-skills-marketplace2.9KUpdated Oct 23, 2026

Review Abridge adoption and workflow value using local usage records, clinician feedback, and verified contract costs. Build an evidence based decision table covering adoption, quality, support burden, and options to expand, hold, or improve the rollout.

  • Reviewing adoption after an Abridge rollout
  • Preparing evidence for a renewal decision
  • Comparing workflow outcomes across care settings
jeremylongshore/tons-of-skills-marketplace2.9KUpdated Oct 23, 2026

Prepare a bounded support bundle for an Abridge issue using allowlisted operational details such as versions, coarse timestamps, and correlation references. Exclude recordings, transcripts, patient identifiers, credentials, and unrestricted logs, then document redactions and review details.

  • Preparing reviewed evidence for an Abridge support case
  • Documenting redactions and excluded data
  • Collecting approved operational details for an incident
jeremylongshore/tons-of-skills-marketplace2.9KUpdated Oct 23, 2026

See all skills by jeremylongshore

Report a problem with this skill