New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Analyzing Logs

by jeremylongshore in jeremylongshore/tons-of-skills-marketplace

Analyze application logs for performance insights and issue detection including slow requests, error patterns, and resource usage.

MITAuto-check passedDevelopment

Install Analyzing Logs

skills CLI
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill analyzing-logs -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install jeremylongshore/tons-of-skills-marketplace analyzing-logs --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/.curated/analyzing-logs .claude/skills/analyzing-logs && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
analyzing-logs
GitHub stars
2.8k
Token cost
~1.1k tokens
SKILL.md length
492 words
Files
6 (incl. scripts, references, assets)
Skills in repo
3,342
Repo updated
First seen
Licence
MIT

At a glance

Analyze application logs for performance insights and issue detection including slow requests, error patterns, and resource usage.

  • Works in 4 steps: Initiate Analysis: Claude activates the… → Log Data Extraction: The tool extracts… → Pattern Identification: The tool… → …
  • Troubleshooting performance issues
  • SKILL.md covers Overview, How It Works, When to Use This Skill and Examples, plus 7 more sections
  • Runs Python scripts from its folder

What it does

Analyzing Logs is an agent skill from jeremylongshore/tons-of-skills-marketplace. 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".

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 8 other files, including scripts, reference files and assets (for example `assets/README.md`, `references/README.md` and `scripts/README.md`). Compatibility notes: Designed for Claude Code

It sits in Development. The repository describes itself as: Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com. The licence is MIT.

When your agent uses it

  • Troubleshooting performance issues
  • Debugging errors
  • With phrases like analyze logs
  • Find slow requests

Example prompts

  • “analyze logs”
  • “find slow requests”
  • “detect error patterns”
  • “/analyzing-logs”

Requirements

  • Python 3
  • Compatibility (from SKILL.md): Designed for Claude Code
  • Pre-approved tools (allowed-tools): Read, Write, Bash(logs:*), Bash(grep:*), Bash(awk:*), Grep

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  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.

What it can do on your machine

Read from SKILL.md and the folder at commit d57fcd5. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Write
    • Bash(logs:*)
    • Bash(grep:*)
    • Bash(awk:*)
    • Grep

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 3 files in scripts/ (Python), which the agent can run.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    Designed for Claude Code

    From compatibility in the SKILL.md frontmatter.

Context cost

Analyzing Logs loads about 1.1k tokens when it runs, and up to ~1.1k if it reads all its reference files. Until then it costs about 76 tokens; SKILL.md has 492 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~76
When it runs · the whole SKILL.md, loaded when a task matches
~1.1k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~1.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from jeremylongshore/tons-of-skills-marketplace at commit d57fcd5, republished under its MIT licence (© jeremylongshore). 492 words, ~1,077 tokens.

Download SKILL.mdSave it as .claude/skills/analyzing-logs/SKILL.md (or your agent's skills folder). This skill also uses 5 other files; get the full folder from GitHub.
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".
allowed-tools
Read, Write, Bash(logs:*), Bash(grep:*), Bash(awk:*), Grep
compatibility
Designed for Claude Code
version
1.24.0
license
MIT
author
Jeremy Longshore <jeremy@intentsolutions.io>
tags
performance, debugging, analyzing-logs

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.
Show full SKILL.md (202 more words)Show less

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

© jeremylongshore, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 5 other files (scripts, references, assets) in skills/.curated/analyzing-logs of jeremylongshore/tons-of-skills-marketplace.

  • SKILL.md
  • assets/README.md
  • references/README.md
  • scripts/README.md
  • scripts/aggregate_logs.py
  • scripts/analyze_log_file.py

Open the folder on GitHubat commit d57fcd5

Compare with similar skills

Analyzing Logs next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Analyzing Logs compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Analyzing Logs this skilljeremylongshore/tons-of-skills-marketplace2.8k—~1.1kAutomated safety check: PassMIT
Vercel Composition Patternssupabase/supabase111k58 repos~726Automated safety check: PassMIT
Finishing a Development Branchobra/superpowers297k5 repos~1.9kAutomated safety check: PassMIT
Typescript Advanced Typesrolling-scopes/rsschool-app10k25 repos~4.2kAutomated safety check: PassMPL-2.0
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
Code Review ChecklistshareAI-lab/learn-claude-code78k4 repos~1.1kAutomated safety check: PassMIT

Similar skills

  • Vercel Composition Patterns

    supabase/supabase

    Official

    React composition patterns that scale. An agent skill from supabase/supabase.

    111k GitHub starsUsed in 58 repos~726 tokens
    DevelopmentAuto-check passed

  • Finishing a Development Branch

    obra/superpowers

    Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.

    297k GitHub starsUsed in 5 repos~1.9k tokens
    DevelopmentAuto-check passed

  • Typescript Advanced Types

    rolling-scopes/rsschool-app

    Master TypeScript's advanced type system including generics, conditional types, mapped types, template literals, and utility types for building type-safe applications.

    10k GitHub starsUsed in 25 repos~4.2k tokens
    DevelopmentAuto-check passed

  • PR Babysitter

    openinterpreter/openinterpreter

    Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.

    69k GitHub starsUsed in 3 repos~4.2k tokens
    DevelopmentAuto-check passed

  • Code Review Checklist

    shareAI-lab/learn-claude-code

    Reviews code against a five-part checklist covering security, correctness, performance, maintainability and testing, and reports findings in a fixed format.

    78k GitHub starsUsed in 4 repos~1.1k tokens
    DevelopmentAuto-check passed

  • Greploop

    onyx-dot-app/onyx

    Iteratively improves a PR (GitHub), MR (GitLab), or shelved changelist (Perforce) until Greptile gives it a 5/5 confidence score with zero unresolved comments.

    32k GitHub starsUsed in 4 repos~3.3k tokens
    DevelopmentAuto-check passed

More from jeremylongshore/tons-of-skills-marketplace

All 3,342 skills in this repo

  • Performing Security Code Review

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to conduct a security-focused code review using the security-agent plugin.

    2.8k GitHub starsUsed in 2 repos~1.3k tokens
    Auto-check: notes

  • Adapting Transfer Learning Models

    jeremylongshore/tons-of-skills-marketplace

    Build this skill automates the adaptation of pre-trained machine learning models using transfer learning techniques.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed

  • Agent Context Loader

    jeremylongshore/tons-of-skills-marketplace

    Execute proactive auto-loading: automatically detects and loads agents.md files.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed

  • Aggregating Performance Metrics

    jeremylongshore/tons-of-skills-marketplace

    Aggregate and centralize performance metrics from applications, systems, databases, caches, and services.

    2.8k GitHub stars~1.2k tokensUpdated today
    Auto-check passed

  • Analyzing Capacity Planning

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to analyze capacity requirements and plan for future growth.

    2.8k GitHub stars~947 tokensUpdated today
    Auto-check passed

  • Analyzing Database Indexes

    jeremylongshore/tons-of-skills-marketplace

    Process use when you need to work with database indexing. An agent skill from jeremylongshore/tons-of-skills-marketplace.

    2.8k GitHub stars~2k tokensUpdated today
    Auto-check passed

Categories

Questions about Analyzing Logs

What does Analyzing Logs do?

Analyze application logs for performance insights and issue detection including slow requests, error patterns, and resource usage. Analyzing Logs is an agent skill from jeremylongshore/tons-of-skills-marketplace. Analyze application logs for performance insights and issue detection including slow requests, error patterns, and resource usage.

When should I use Analyzing Logs?

Analyzing Logs fits situations like: troubleshooting performance issues; debugging errors; with phrases like analyze logs; find slow requests.

How do I install Analyzing Logs in Claude Code?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill analyzing-logs -a claude-code`. Or copy the skill folder (skills/.curated/analyzing-logs in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/analyzing-logs in your project. Claude Code loads it when a task matches its description.

How do I install Analyzing Logs in Codex?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill analyzing-logs -a codex`. Or copy the skill folder (skills/.curated/analyzing-logs in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/analyzing-logs in your project. Codex loads it when a task matches its description.

Can I use Analyzing Logs in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill analyzing-logs -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/analyzing-logs, .gemini/skills/analyzing-logs, .github/skills/analyzing-logs and .opencode/skills/analyzing-logs in your project.

What does Analyzing Logs need to run?

Going by SKILL.md and its folder, Analyzing Logs needs Python for the scripts in its folder. Our summary lists: Python 3. Its frontmatter pre-approves these tools: Read, Write, Bash(logs:*), Bash(grep:*), Bash(awk:*), Grep. Compatibility (from SKILL.md): Designed for Claude Code.

Does Analyzing Logs access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Analyzing Logs safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Analyzing Logs use?

Analyzing Logs is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Analyzing Logs use?

About 1.1k tokens (SKILL.md is roughly 4.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 15 tokens, read only when the agent opens those files.

What are the alternatives to Analyzing Logs?

Skills that share tags, products or a category with Analyzing Logs: Vercel Composition Patterns (supabase/supabase, 111k stars), Finishing a Development Branch (obra/superpowers, 297k stars), Typescript Advanced Types (rolling-scopes/rsschool-app, 10k stars) and PR Babysitter (openinterpreter/openinterpreter, 69k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Analyzing Logs?

jeremylongshore (a GitHub user) maintains it in jeremylongshore/tons-of-skills-marketplace, which has 2,831 GitHub stars. The repository holds 3,342 skills in this directory. The repository was last updated on October 11, 2026.

Source: jeremylongshore/tons-of-skills-marketplace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.