Skip to content
TrustedSkillsbeta
Back to all skills

Log Coverage Analyzer

Checked
openharmonyinsight·vlatest·testing

Analyzes application logs to identify gaps in test coverage, ensuring comprehensive testing and reducing potential bugs.

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 openharmonyinsight/openharmony-skills --skill log-coverage-analyzer -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

openharmonyinsight

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 openharmonyinsight/openharmony-skills at 5ae988cab6.

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

Commit
5ae988cab6
Manifest
skills/log-coverage-analyzer/SKILL.md
Scanned
1 file, 390 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

The log-coverage-analyzer skill analyzes log files to determine the percentage of code covered by those logs. It identifies gaps in logging, helping developers understand which parts of their system are not adequately monitored. This allows for more targeted and effective debugging and performance optimization efforts.

When to use it

  • Debugging complex issues: Use it when troubleshooting a problem where you suspect missing or insufficient log data is hindering diagnosis.
  • Performance tuning: Identify areas of code that lack logging, potentially masking performance bottlenecks.
  • Post-release monitoring: After deploying new features or updates, verify adequate logging coverage to ensure proper observability.
  • Code review process: Integrate it into your development workflow to proactively identify and address logging gaps during code reviews.

Key capabilities

  • Log file analysis
  • Code coverage percentage calculation
  • Gap identification in log data

Example prompts

  • "Analyze the /var/log/myapp.log file for code coverage."
  • "What percentage of my application's codebase is covered by logs?"
  • "Show me areas of my system with low logging coverage based on the production.log file."

Tips & gotchas

The accuracy of the analysis depends heavily on the quality and completeness of your log files and how well they correlate to code execution. Ensure you have sufficient logging statements in critical sections of your application for meaningful results.