aggregating-performance-metrics
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".
- License 许可
- MIT
- 最近更新
- 2026-05-26
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- aggregating-performance-metrics
- author
- Jeremy Longshore <jeremy@intentsolutions.io>
- license
- MIT
- version
- 1.0.0
- description
- 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".
- allowed-tools
- Read, Write, Bash(prometheus:*), Bash(metrics:*), Bash(monitoring:*), Grep
- compatible-with
- claude-code, codex, openclaw
02 资源文件 3
- 资产文件assets/README.md203 B
- 参考文档references/README.md62 B
- 脚本scripts/README.md746 B
03 SKILL.md 正文
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
- Metrics Taxonomy Design: Claude assists in defining a clear and consistent naming convention for metrics across all systems.
- Aggregation Tool Selection: Claude helps select the appropriate metrics aggregation tool (e.g., Prometheus, StatsD, CloudWatch) based on the user's environment and requirements.
- Configuration and Integration: Claude guides the configuration of the chosen aggregation tool and its integration with various data sources.
- 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:
- Guide the user in defining metrics for applications (e.g., request latency, error rates) and systems (e.g., CPU usage, memory utilization).
- 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:
- Help the user define metrics for database performance (e.g., query execution time, connection pool usage).
- Guide the user in configuring the aggregation tool to collect these metrics from the database.
- 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
- Design consistent metrics naming convention
- Select appropriate aggregation tool for environment
- Configure metric collection from all sources
- Set up centralized storage and retention policies
- Create dashboards for visualization
- 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
04 同仓库更多 Skills
zustand-store-ts
Create Zustand stores with TypeScript, subscribeWithSelector middleware, and proper state/action separation. Use when building React state management, creating global stores, or implementing reactive state patterns with Zustand.
zustand-store-creator
Zustand Store Creator - Auto-activating skill for Frontend Development. Triggers on: zustand store creator, zustand store creator Part of the Frontend Development skill category.
zero-trust-config-helper
Zero Trust Config Helper - Auto-activating skill for Security Advanced. Triggers on: zero trust config helper, zero trust config helper Part of the Security Advanced skill category.
zapier-integration-helper
Zapier Integration Helper - Auto-activating skill for Business Automation. Triggers on: zapier integration helper, zapier integration helper Part of the Business Automation skill category.
zai-cli
Execute z.AI CLI providing vision, search, reader, and GitHub exploration via CLI and MCP. Use when user needs image/video analysis, OCR, UI-to-code conversion, error diagnosis, real-time web search, web page to markdown extraction, or GitHub code exploration. Trigger with phrases like "analyze this image", "search the web for", "read this page", "explore this repo", or "use zai". Requires Z_AI_API_KEY.
yt-research
Research competitor YouTube channels, niches, and trending topics for your content strategy. Use this skill whenever the user says "research channels", "analyze competitors", "find trending topics", "niche analysis", "competitive research", "what are other creators doing", "scrape YouTube channels", or wants to understand the competitive landscape for a specific tool or topic area. Use when working with yt research. Trigger with 'yt', 'research'.