log-analyzer
A log analysis tool for MikoPBX Docker containers to diagnose errors and monitor system behavior.
Install
mkdir -p .claude/skills/log-analyzer && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/2841" && unzip -o skill.zip -d .claude/skills/log-analyzer && rm skill.zipInstalls to .claude/skills/log-analyzer
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Анализ файлов логов MikoPBX (system/messages, PHP, Asterisk, nginx, fail2ban) в Docker контейнере для диагностики проблем. Использовать при отладке ошибок, отслеживании процессов воркеров, исследовании проблем API или анализе причин после упавших тестов.Key capabilities
- →Search and filter system, PHP, and Asterisk logs
- →Correlate errors across multiple log files
- →Identify active worker process status
- →Parse Docker container logs efficiently
How it works
Uses standard Linux tools like grep and read to parse and correlate text-based logs stored in predefined host or container directories.
Inputs & outputs
When to use log-analyzer
- →Debug API connection errors
- →Monitor Asterisk worker processes
- →Analyze failed test logs
- →Track system health metrics
About log-analyzer
Intelligently searches and filters logs from system, PHP, Asterisk, and Nginx. It correlates issues across files and tracks worker process status to provide actionable debugging insights.
Анализ логов Docker контейнера для диагностики проблем и мониторинга здоровья системы. Использовать при отладке ошибок, отслеживании процессов воркеров, исследовании проблем API или мониторинге поведения системы после тестов.
When not to use it
- →When logs are not available on the local filesystem or inside containers
- →When the system is not MikoPBX
Prerequisites
Limitations
- →Requires filesystem access to log directories
- →Limited by the verbosity of current log settings
How it compares
Offers specific knowledge of MikoPBX log structure and file locations instead of performing generic log searching.
Compared to similar skills
log-analyzer side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| log-analyzer (this skill) | 2 | 4mo | Review | Beginner |
| incident-response-smart-fix | 4 | 5mo | No flags | Advanced |
| debug-cluster | 2 | 10mo | Review | Intermediate |
| k8s-diagnostics | 1 | 8mo | No flags | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by mikopbx
View all by mikopbx →You might also like
incident-response-smart-fix
sickn33
[Extended thinking: This workflow implements a sophisticated debugging and resolution pipeline that leverages AI-assisted debugging tools and observability platforms to systematically diagnose and res
debug-cluster
openshift
Provides systematic debugging approaches for HyperShift hosted-cluster issues. Auto-applies when debugging cluster problems, investigating stuck deletions, or troubleshooting control plane issues.
k8s-diagnostics
rohitg00
Kubernetes diagnostics for metrics, health checks, resource comparisons, and cluster analysis. Use when analyzing cluster health, comparing environments, or gathering diagnostic data.
langfuse-local-dev-loop
jeremylongshore
Set up Langfuse local development workflow with hot reload and debugging. Use when developing LLM applications locally, debugging traces, or setting up a fast iteration loop with Langfuse. Trigger with phrases like "langfuse local dev", "langfuse development", "debug langfuse traces", "langfuse hot reload", "langfuse dev workflow".
railway-deployment
davila7
Manage Railway deployments - view logs, redeploy, restart, or remove deployments. Use for deployment lifecycle (remove, stop, redeploy, restart), deployment visibility (list, status, history), and troubleshooting (logs, errors, failures, crashes). NOT for deleting services - use railway-environment skill with isDeleted for that.
doctor
louisphamdev
**SKILL** — Doctor Agent diagnostic & self-healing toolkit for Turing OS. Use when: diagnosing errors, fixing system issues, checking Docker/container health, querying known issues database, running self-healing scripts, tracking fix metrics, or generating GitHub issues. Triggers: "doctor", "diagnos