Index of every page on this site: llms.txt
All skills
jeremylongshore avatar

/aggregating-performance-metrics

@820dfc8
Run it yourself

Aggregate and centralize performance metrics from applications, systems, databases, caches, and services. Use when consolidating monitoring data from multiple sources. Trigger with phrases like "aggregate metrics", "centralize monitoring", or "collect performance data".

Use this Skill: https://skilld.dev/gh/jeremylongshore/tons-of-skills-marketplace/aggregating-performance-metrics

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈76 tokens for metadata: the name and description. ≈1k when used: this file. ≈253 more on demand in 3 files.

Description uses 3.8% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈304 characters, or 3.8%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Metrics Aggregator

Aggregate and centralize performance metrics from applications, databases, caches, and infrastructure into Prometheus, StatsD, or CloudWatch with unified naming conventions.

Overview

This skill empowers Claude to streamline performance monitoring by aggregating metrics from diverse systems into a unified view. It simplifies the process of collecting, centralizing, and analyzing performance data, leading to improved insights and faster issue resolution.

How It Works

  1. Metrics Taxonomy Design: Claude assists in defining a clear and consistent naming convention for metrics across all systems.
  2. Aggregation Tool Selection: Claude helps select the appropriate metrics aggregation tool (e.g., Prometheus, StatsD, CloudWatch) based on the user's environment and requirements.
  3. Configuration and Integration: Claude guides the configuration of the chosen aggregation tool and its integration with various data sources.
  4. Dashboard and Alert Setup: Claude helps set up dashboards for visualizing metrics and defining alerts for critical performance indicators.

When to Use This Skill

This skill activates when you need to:

  • Centralize performance metrics from multiple applications and systems.
  • Design a consistent metrics naming convention.
  • Choose the right metrics aggregation tool for your needs.
  • Set up dashboards and alerts for performance monitoring.

Examples

Example 1: Centralizing Application and System Metrics

User request: "Aggregate application and system metrics into Prometheus."

The skill will:

  1. Guide the user in defining metrics for applications (e.g., request latency, error rates) and systems (e.g., CPU usage, memory utilization).
  2. Help configure Prometheus to scrape metrics from the application and system endpoints.

Example 2: Setting Up Alerts for Database Performance

User request: "Centralize database metrics and set up alerts for slow queries."

The skill will:

  1. Help the user define metrics for database performance (e.g., query execution time, connection pool usage).
  2. Guide the user in configuring the aggregation tool to collect these metrics from the database.
  3. Assist in setting up alerts in the aggregation tool to notify the user when query execution time exceeds a defined threshold.

Best Practices

  • Naming Conventions: Use a consistent and well-defined naming convention for all metrics to ensure clarity and ease of analysis.
  • Granularity: Choose an appropriate level of granularity for metrics to balance detail and storage requirements.
  • Retention Policies: Define retention policies for metrics to manage storage space and ensure data is available for historical analysis.

Integration

This skill integrates with other plugins that manage infrastructure, deploy applications, and monitor system health. For example, it can be used in conjunction with a deployment plugin to automatically configure metrics collection after a new application deployment.

Prerequisites

  • Access to metrics collection tools (Prometheus, StatsD, CloudWatch)
  • Network connectivity to metric sources
  • Metrics storage configuration in ${CLAUDE_SKILL_DIR}/metrics/
  • Understanding of metrics taxonomy

Instructions

  1. Design consistent metrics naming convention
  2. Select appropriate aggregation tool for environment
  3. Configure metric collection from all sources
  4. Set up centralized storage and retention policies
  5. Create dashboards for visualization
  6. Define alerts for critical metrics

Output

  • Metrics aggregation configuration files
  • Unified naming convention documentation
  • Dashboard definitions for key metrics
  • Alert rules for performance thresholds
  • Integration guides for metric sources

Error Handling

If metrics aggregation fails:

  • Verify network connectivity to sources
  • Check authentication credentials
  • Validate metrics format compatibility
  • Review storage capacity and retention
  • Ensure aggregation tool configuration

Resources

  • Prometheus aggregation documentation
  • StatsD protocol specifications
  • CloudWatch metrics API reference
  • Metrics naming best practices

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts2mo3 checks · Risk SAFE
  • Gen Agent Trust Hub2mo

    The skill automates the collection, aggregation, and export of performance metrics using local Python scripts. It interacts with well-known monitoring platforms including Datadog, Splunk, and Grafana. The analysis identified an indirect prompt injection surface through the ingestion of external metric data and the use of scoped shell commands for automation. No malicious obfuscation, persistence, or privilege escalation patterns were detected.

  • Socket2mo

    No alerts

  • Snyk2mo

    Risk: LOW · No issues

Signed by skilld at 820dfc8. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 3 months ago
What it can do
Reads files Edits files Runs commands
version
1.21.0
author
Jeremy Longshore <jeremy@intentsolutions.io>
tags
[
  "performance",
  "database",
  "monitoring"
]
All 6 allowed tools
ReadWriteBash(prometheus:*)Bash(metrics:*)Bash(monitoring:*)Grep
Other metadata
compatibility
Designed for Claude Code

README badge

README badge for jeremylongshore/tons-of-skills-marketplace/aggregating-performance-metrics