Skip to content
TrustedSkillsbeta
Back to all skills

Observability Analyze Logs

Checked
dawiddutoit·vlatest·devops

Analyze application logs to identify errors, performance bottlenecks, and potential security threats in real time.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add dawiddutoit/custom-claude --skill observability-analyze-logs -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

dawiddutoit

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned dawiddutoit/custom-claude at 17b45a90a6.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
17b45a90a6
Manifest
skills/observability-analyze-logs/SKILL.md
Scanned
7 files, 3,737 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill allows you to analyze log data and extract meaningful insights. It can identify error patterns, summarize key events from logs, and help pinpoint the root cause of issues within a system. The skill is designed to process large volumes of log entries efficiently and provide concise summaries for faster troubleshooting.

When to use it

  • Troubleshooting application errors: Quickly understand the sequence of events leading up to an error by analyzing relevant log files.
  • Identifying performance bottlenecks: Analyze logs related to specific services or endpoints to identify slow response times or resource contention.
  • Security incident investigation: Examine security-related logs for suspicious activity and potential breaches.
  • Monitoring system health: Regularly analyze logs to proactively detect anomalies and prevent future issues.

Key capabilities

  • Log parsing and analysis
  • Error pattern identification
  • Log summarization
  • Root cause analysis assistance

Example prompts

  • "Analyze the application logs from the last 24 hours and identify any recurring error patterns."
  • "Summarize the key events related to user authentication failures in the security logs."
  • "What are the top 5 most frequent errors logged by the database server?"

Tips & gotchas

The skill's effectiveness depends on well-structured and consistently formatted log data. Ensure your logging practices include sufficient context for accurate analysis.