analyze-logs

Analyze Librova import logs to identify failures and actionable fixes.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/EvgeniiFenita/Librova --skill analyze-logs-evgeniifenita
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: analyze-logs
Source: https://github.com/EvgeniiFenita/Librova/tree/main/.agents/skills/analyze-logs
Command: npx skills add https://github.com/EvgeniiFenita/Librova --skill analyze-logs-evgeniifenita

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This analysis workflow converts noisy Librova import logs into a concise diagnostic that highlights failures, degradation patterns, and actionable fixes.

Core Features & Use Cases

  • Evaluate severity counts and top message families in import logs to surface recurring issues.
  • Reconstruct throughput and cancellation timelines across frontend/backend components to identify bottlenecks.
  • Produce prioritized, actionable recommendations distinguishing immediate fixes from backlog items, with evidence traceable to log patterns.

Quick Start

Provide the Librova import log file path or content and request a diagnostic report.

Frequently Asked Questions about analyze-logs

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I analyze Librova import logs to identify failures and degradation patterns?

To analyze Librova import logs, provide the log file path or content to extract severity counts, categorize errors, reconstruct throughput timelines, and generate prioritized actionable fixes for bottlenecks.

What is the best way to compare two Librova import runs using log diagnostics?

The best way to compare two Librova import runs is by evaluating severity metrics and reconstructing cancellation timelines across frontend and backend components to identify progressive degradation and distinct bottlenecks.

How does log analysis reconstruct throughput and progress timelines for cancelled imports?

Log analysis reconstructs throughput and progress timelines by correlating sequential log entries across frontend and backend components, mapping cancellation events against processing speed to pinpoint exact bottleneck origins.

Can I use log analysis to distinguish immediate fixes from backlog items for Librova imports?

Yes, you can distinguish immediate fixes from backlog items by categorizing extracted log errors and warnings into prioritized, actionable recommendations with evidence directly traceable to identified log patterns.

What log formats and components are supported for diagnosing Librova fb2 import issues?

Diagnosing Librova fb2 import issues supports standard text log formats from both frontend and backend components, extracting message families, severity counts, and cancellation timelines without requiring external dependencies.