Agent skill

Monitoring Error Rates

by jeremylongshore in jeremylongshore/tons-of-skills-marketplace

Monitor and analyze application error rates to improve reliability.

MITAuto-check passedDevOps & Cloud

Install Monitoring Error Rates

skills CLI
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill monitoring-error-rates -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install jeremylongshore/tons-of-skills-marketplace monitoring-error-rates --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/.curated/monitoring-error-rates .claude/skills/monitoring-error-rates && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
monitoring-error-rates
GitHub stars
2.8k
Token cost
~1.2k tokens
SKILL.md length
548 words
Files
6 (incl. scripts, references, assets)
Skills in repo
3,342
Repo updated
First seen
Licence
MIT

At a glance

Monitor and analyze application error rates to improve reliability.

  • Works in 3 steps: Analyze Error Sources: Identifies… → Define Monitoring Criteria: Establishes… → Configure Alerting: Sets up alerts to…
  • Tracking errors in applications including HTTP errors
  • SKILL.md covers Overview, How It Works, When to Use This Skill and Examples, plus 7 more sections
  • Runs Python scripts from its folder

What it does

Monitoring Error Rates is an agent skill from jeremylongshore/tons-of-skills-marketplace. Monitor and analyze application error rates to improve reliability. Use when tracking errors in applications including HTTP errors, exceptions, and database issues. Trigger with phrases like "monitor error rates", "track application errors", or "analyze error patterns".

Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 8 other files, including scripts, reference files and assets (for example `assets/README.md`, `references/README.md` and `scripts/README.md`). Compatibility notes: Designed for Claude Code

It sits in DevOps & Cloud, covering Background jobs. The repository describes itself as: Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com. The licence is MIT.

When your agent uses it

  • Tracking errors in applications including HTTP errors
  • Database issues
  • With phrases like monitor error rates
  • Track application errors

Example prompts

  • “monitor error rates”
  • “track application errors”
  • “analyze error patterns”
  • “/monitoring-error-rates”

Requirements

  • Python 3
  • Compatibility (from SKILL.md): Designed for Claude Code
  • Pre-approved tools (allowed-tools): Read, Bash(monitoring:*), Bash(metrics:*), Bash(logs:*), Grep, Glob

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

  1. Analyze Error Sources: Identifies potential error sources within the application architecture, including HTTP endpoints, database queries…
  2. Define Monitoring Criteria: Establishes specific error types and thresholds for each source, such as HTTP status codes (4xx, 5xx)…
  3. Configure Alerting: Sets up alerts to trigger when error rates exceed defined thresholds, notifying relevant teams or individuals for…

What it can do on your machine

Read from SKILL.md and the folder at commit cfae287. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Bash(monitoring:*)
    • Bash(metrics:*)
    • Bash(logs:*)
    • Grep
    • Glob

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 3 files in scripts/ (Python), which the agent can run.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    Designed for Claude Code

    From compatibility in the SKILL.md frontmatter.

Context cost

Monitoring Error Rates loads about 1.2k tokens when it runs, and up to ~1.2k if it reads all its reference files. Until then it costs about 73 tokens; SKILL.md has 548 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~73
When it runs · the whole SKILL.md, loaded when a task matches
~1.2k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~1.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from jeremylongshore/tons-of-skills-marketplace at commit cfae287, republished under its MIT licence (© jeremylongshore). 548 words, ~1,176 tokens.

Download SKILL.mdSave it as .claude/skills/monitoring-error-rates/SKILL.md (or your agent's skills folder). This skill also uses 5 other files; get the full folder from GitHub.
name
monitoring-error-rates
description
Monitor and analyze application error rates to improve reliability. Use when tracking errors in applications including HTTP errors, exceptions, and database issues. Trigger with phrases like "monitor error rates", "track application errors", or "analyze error patterns".
allowed-tools
Read, Bash(monitoring:*), Bash(metrics:*), Bash(logs:*), Grep, Glob
compatibility
Designed for Claude Code
version
1.22.0
license
MIT
author
Jeremy Longshore <jeremy@intentsolutions.io>
tags
performance, database, monitoring

Error Rate Monitor

Monitor and analyze application error rates across HTTP endpoints, database queries, external APIs, and background jobs with threshold-based alerting and error budget tracking.

Overview

This skill automates the process of setting up comprehensive error monitoring and alerting for various components of an application. It helps identify, track, and analyze different types of errors, enabling proactive identification and resolution of issues before they impact users.

How It Works

  1. Analyze Error Sources: Identifies potential error sources within the application architecture, including HTTP endpoints, database queries, external APIs, background jobs, and client-side code.
  2. Define Monitoring Criteria: Establishes specific error types and thresholds for each source, such as HTTP status codes (4xx, 5xx), exception types, query timeouts, and API response failures.
  3. Configure Alerting: Sets up alerts to trigger when error rates exceed defined thresholds, notifying relevant teams or individuals for investigation and remediation.

When to Use This Skill

This skill activates when you need to:

  • Set up error monitoring for a new application.
  • Analyze existing error rates and identify areas for improvement.
  • Configure alerts to be notified of critical errors in real-time.
  • Establish error budgets and track progress towards reliability goals.

Examples

Example 1: Setting up Error Monitoring for a Web Application

User request: "Monitor errors in my web application, especially 500 errors and database connection issues."

The skill will:

  1. Analyze the web application's architecture to identify potential error sources (e.g., HTTP endpoints, database connections).
  2. Configure monitoring for 500 errors and database connection failures, setting appropriate thresholds and alerts.
Example 2: Analyzing Error Rates in a Background Job Processor

User request: "Analyze error rates for my background job processor. I'm seeing a lot of failed jobs."

The skill will:

  1. Focus on the background job processor and identify the types of errors occurring (e.g., task failures, timeouts, resource exhaustion).
  2. Analyze the frequency and patterns of these errors to identify potential root causes.
Show full SKILL.md (231 more words)Show less

Best Practices

  • Granularity: Monitor errors at a granular level to identify specific problem areas.
  • Thresholding: Set appropriate alert thresholds to avoid alert fatigue and focus on critical issues.
  • Context: Include relevant context in error messages and alerts to facilitate troubleshooting.

Integration

This skill can be integrated with other monitoring and alerting tools, such as Prometheus, Grafana, and PagerDuty, to provide a comprehensive view of application health and performance. It can also be used in conjunction with incident management tools to streamline incident response workflows.

Prerequisites

  • Access to application logs and metrics
  • Monitoring infrastructure (Prometheus, Grafana, or similar)
  • Read permissions for log files in ${CLAUDE_SKILL_DIR}/logs/
  • Network access to monitoring endpoints

Instructions

  1. Identify error sources by analyzing application architecture
  2. Define error types and monitoring thresholds
  3. Configure alerting rules with appropriate severity levels
  4. Set up dashboards for error rate visualization
  5. Establish notification channels for critical errors
  6. Document error baselines and SLO targets

Output

  • Error rate metrics and trends
  • Alert configurations for critical thresholds
  • Dashboard definitions for error monitoring
  • Reports on error patterns and root causes
  • Recommendations for error reduction strategies

Error Handling

If monitoring setup fails:

  • Verify log file permissions and paths
  • Check monitoring service connectivity
  • Validate metric export configurations
  • Review alert rule syntax
  • Ensure notification channels are configured

Resources

  • Monitoring platform documentation (Prometheus, Grafana)
  • Application log format specifications
  • Error taxonomy and classification guides
  • SLO/SLI definition best practices

© jeremylongshore, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 5 other files (scripts, references, assets) in skills/.curated/monitoring-error-rates of jeremylongshore/tons-of-skills-marketplace.

  • SKILL.md
  • assets/README.md
  • references/README.md
  • scripts/README.md
  • scripts/analyze_errors.py
  • scripts/generate_error_report.py

Open the folder on GitHubat commit cfae287

Compare with similar skills

Monitoring Error Rates next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Monitoring Error Rates compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Monitoring Error Rates this skilljeremylongshore/tons-of-skills-marketplace2.8k—~1.2kAutomated safety check: PassMIT
Loki Logsletsrevel/revel-backend110—~918Automated safety check: NotesMIT
Gke Batch Hpcgoogle/skills21k—~1.4kAutomated safety check: PassApache-2.0
Temporal Helpershepherdjerred/monorepo112—~601Automated safety check: PassGPL-3.0
Mirrord Temporalmetalbear-co/mirrord5.4k1 repos~5.1kAutomated safety check: PassMIT
Trigger.dev Cost Savings Auditpapermark/papermark9.2k—~1.3kAutomated safety check: PassCustom licence

Similar skills

  • Loki Logs

    letsrevel/revel-backend

    A skill your agent uses when investigating production behaviour from logs — a 500/error in prod, a failing or stuck Celery task, tracing one request/traceid/user across services, or confirming a…

    110 GitHub stars~918 tokensUpdated 4 days ago
    DevOps & CloudAuto-check: notes
  • Gke Batch Hpc

    google/skills

    Official

    Runs batch and HPC workloads on GKE, utilizing job queues and parallel processing.

    21k GitHub stars~1.4k tokensUpdated yesterday
    DevOps & CloudAuto-check passed
  • Temporal Helper

    shepherdjerred/monorepo

    Safely design, implement, test, deploy, debug, and operate Temporal durable applications, with current TypeScript SDK, Workflow, Activity, Worker, Task Queue, Schedule, CLI, Cloud/server, replay…

    112 GitHub stars~601 tokensUpdated yesterday
    DevOps & CloudAuto-check passed
  • Mirrord Temporal

    metalbear-co/mirrord

    Helps DevOps engineers configure mirrord Operator's Temporal task queue splitting feature end-to-end.

    5.4k GitHub starsUsed in 1 repo~5.1k tokens
    DevOps & CloudAuto-check passed
  • Audits Trigger.dev tasks, schedules and run history for wasteful machine sizes, retries, polling and cron frequency to cut spend.

    9.2k GitHub stars~1.3k tokensUpdated 1 mo ago
    DevOps & CloudAuto-check passed
  • Agent Advisor

    aws/agent-toolkit-for-aws

    Official

    Entry point for AI-agent work on AWS: pick a runtime, plan a migration for existing workloads, and build an executable POC — one phased flow.

    2.8k GitHub stars~4.9k tokensUpdated yesterday
    DevOps & CloudAuto-check passed

More from jeremylongshore/tons-of-skills-marketplace

All 3,342 skills in this repo
  • Performing Security Code Review

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to conduct a security-focused code review using the security-agent plugin.

    2.8k GitHub starsUsed in 2 repos~1.3k tokens
    Auto-check: notes
  • Adapting Transfer Learning Models

    jeremylongshore/tons-of-skills-marketplace

    Build this skill automates the adaptation of pre-trained machine learning models using transfer learning techniques.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Agent Context Loader

    jeremylongshore/tons-of-skills-marketplace

    Execute proactive auto-loading: automatically detects and loads agents.md files.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Aggregating Performance Metrics

    jeremylongshore/tons-of-skills-marketplace

    Aggregate and centralize performance metrics from applications, systems, databases, caches, and services.

    2.8k GitHub stars~1.2k tokensUpdated today
    Auto-check passed
  • Analyzing Capacity Planning

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to analyze capacity requirements and plan for future growth.

    2.8k GitHub stars~947 tokensUpdated today
    Auto-check passed
  • Analyzing Database Indexes

    jeremylongshore/tons-of-skills-marketplace

    Process use when you need to work with database indexing. An agent skill from jeremylongshore/tons-of-skills-marketplace.

    2.8k GitHub stars~2k tokensUpdated today
    Auto-check passed

Questions about Monitoring Error Rates

What does Monitoring Error Rates do?

Monitor and analyze application error rates to improve reliability. Monitoring Error Rates is an agent skill from jeremylongshore/tons-of-skills-marketplace. Monitor and analyze application error rates to improve reliability.

When should I use Monitoring Error Rates?

Monitoring Error Rates fits situations like: tracking errors in applications including HTTP errors; database issues; with phrases like monitor error rates; track application errors.

How do I install Monitoring Error Rates in Claude Code?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill monitoring-error-rates -a claude-code`. Or copy the skill folder (skills/.curated/monitoring-error-rates in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/monitoring-error-rates in your project. Claude Code loads it when a task matches its description.

How do I install Monitoring Error Rates in Codex?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill monitoring-error-rates -a codex`. Or copy the skill folder (skills/.curated/monitoring-error-rates in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/monitoring-error-rates in your project. Codex loads it when a task matches its description.

Can I use Monitoring Error Rates in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill monitoring-error-rates -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/monitoring-error-rates, .gemini/skills/monitoring-error-rates, .github/skills/monitoring-error-rates and .opencode/skills/monitoring-error-rates in your project.

What does Monitoring Error Rates need to run?

Going by SKILL.md and its folder, Monitoring Error Rates needs Python for the scripts in its folder. Our summary lists: Python 3. Its frontmatter pre-approves these tools: Read, Bash(monitoring:*), Bash(metrics:*), Bash(logs:*), Grep, Glob. Compatibility (from SKILL.md): Designed for Claude Code.

Does Monitoring Error Rates access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Monitoring Error Rates safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Monitoring Error Rates use?

Monitoring Error Rates is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Monitoring Error Rates use?

About 1.2k tokens (SKILL.md is roughly 4.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 16 tokens, read only when the agent opens those files.

What are the alternatives to Monitoring Error Rates?

Skills that share tags, products or a category with Monitoring Error Rates: Loki Logs (letsrevel/revel-backend, 110 stars), Gke Batch Hpc (google/skills, 21k stars), Temporal Helper (shepherdjerred/monorepo, 112 stars) and Mirrord Temporal (metalbear-co/mirrord, 5.4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Monitoring Error Rates?

jeremylongshore (a GitHub user) maintains it in jeremylongshore/tons-of-skills-marketplace, which has 2,827 GitHub stars. The repository holds 3,342 skills in this directory. The repository was last updated on October 10, 2026.

Source: jeremylongshore/tons-of-skills-marketplace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.