error-tracker

Monitor application logs to detect, group, and triage errors by severity and frequency.

Updated Feb 18, 2026
One-click install
npx skills add https://github.com/Greenmamba29/skillsdotmd_web --skill error-tracker
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: error-tracker
Source: https://github.com/Greenmamba29/skillsdotmd_web/tree/main/.agents/skills/error-tracker
Command: npx skills add https://github.com/Greenmamba29/skillsdotmd_web --skill error-tracker

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the monitoring of application logs and error streams, enabling the detection, grouping, and triaging of errors based on their severity and frequency.

Core Features & Use Cases

  • Real-time Monitoring: Continuously monitors production application logs and error events.
  • Automated Ticketing: Automatically creates GitHub issues or Jira tickets for new or critical errors.
  • Team Notification: Notifies the on-call team via Slack or PagerDuty for critical errors.
  • Use Case: After a new deployment, this Skill can instantly alert the DevOps team to any critical errors that arise, preventing widespread user impact.

Quick Start

Use the error-tracker skill to monitor the CloudWatch log group 'app' for critical errors and send alerts to the #ops-errors Slack channel.

Frequently Asked Questions about error-tracker

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

FAQPage Schema
How do I monitor application logs and automatically create Jira tickets for critical errors?

To monitor application logs and create Jira tickets, configure the log sources, monitoring intervals, and severity thresholds to automatically generate tickets for new or critical errors detected in your error streams.

What is the best way to alert the on-call DevOps team in Slack when production errors occur?

The best way to alert the on-call DevOps team in Slack is to configure your notification channels to send real-time alerts when the monitoring system detects critical errors in your production application logs.

How does error grouping and triage by severity and frequency work?

Error grouping and triage works by continuously monitoring error streams, analyzing the frequency and severity of application errors, and automatically categorizing them to prioritize incident response.

Can I use PagerDuty for alerting when monitoring error streams for new deployments?

Yes, you can use PagerDuty for alerting by configuring it as your notification channel to instantly alert the on-call team to critical errors that arise after a new deployment.

Do I need to configure log sources and monitoring intervals before tracking application errors?

Yes, you need to configure log sources, monitoring intervals, severity thresholds, and notification channels before tracking application errors to ensure accurate detection and automated alerting.

How do I detect and group application errors from CloudWatch log groups?

You detect and group application errors from CloudWatch log groups by configuring the log group as your log source, allowing the system to monitor error events and categorize them by severity and frequency.