[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6H58MR014P9403WNMC33VJZ":3,"skill-same:01M6H58MR014P9403WNMC33VJZ":86},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":47,"commitSha":48,"skillDirectory":49,"forksCount":50,"repositoryHtmlUrl":51,"repositoryHomepageUrl":6,"ownerHtmlUrl":52,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":53,"install":54,"resources":67},"01M6H58MR014P9403WNMC33VJZ","aggregating-performance-metrics",null,"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\".","micsapp\u002Fmicstec-skills","micsapp","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F82411001?v=4","01M6GWCFQ6D3PV8EHNY62NN5VW","01M6GWCFVE1PA5HG0DKC7AMFJ3",4,"MIT","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fclaude-code\u002Fplugins-plus-skills\u002Fplugins\u002Fperformance\u002Fmetrics-aggregator\u002Fskills\u002Faggregating-performance-metrics\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"performance","metrics","performance metrics","Aggregating Performance Metrics","with","codex","sources","trigger","io","databases","use","write","read","Bash","applications","services","monitoring","collect","prometheus","code","2026-11-10 10:12:30",false,"---\nname: aggregating-performance-metrics\ndescription: 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\".\nversion: 1.0.0\nallowed-tools: \"Read, Write, Bash(prometheus:*), Bash(metrics:*), Bash(monitoring:*), Grep\"\nlicense: MIT\nauthor: Jeremy Longshore \u003Cjeremy@intentsolutions.io>\ncompatible-with: claude-code, codex, openclaw\n---\n# Metrics Aggregator\n\nAggregate and centralize performance metrics from applications, databases, caches, and infrastructure into Prometheus, StatsD, or CloudWatch with unified naming conventions.\n\n## Overview\n\nThis 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.\n\n## How It Works\n\n1. **Metrics Taxonomy Design**: Claude assists in defining a clear and consistent naming convention for metrics across all systems.\n2. **Aggregation Tool Selection**: Claude helps select the appropriate metrics aggregation tool (e.g., Prometheus, StatsD, CloudWatch) based on the user's environment and requirements.\n3. **Configuration and Integration**: Claude guides the configuration of the chosen aggregation tool and its integration with various data sources.\n4. **Dashboard and Alert Setup**: Claude helps set up dashboards for visualizing metrics and defining alerts for critical performance indicators.\n\n## When to Use This Skill\n\nThis skill activates when you need to:\n- Centralize performance metrics from multiple applications and systems.\n- Design a consistent metrics naming convention.\n- Choose the right metrics aggregation tool for your needs.\n- Set up dashboards and alerts for performance monitoring.\n\n## Examples\n\n### Example 1: Centralizing Application and System Metrics\n\nUser request: \"Aggregate application and system metrics into Prometheus.\"\n\nThe skill will:\n1. Guide the user in defining metrics for applications (e.g., request latency, error rates) and systems (e.g., CPU usage, memory utilization).\n2. Help configure Prometheus to scrape metrics from the application and system endpoints.\n\n### Example 2: Setting Up Alerts for Database Performance\n\nUser request: \"Centralize database metrics and set up alerts for slow queries.\"\n\nThe skill will:\n1. Help the user define metrics for database performance (e.g., query execution time, connection pool usage).\n2. Guide the user in configuring the aggregation tool to collect these metrics from the database.\n3. Assist in setting up alerts in the aggregation tool to notify the user when query execution time exceeds a defined threshold.\n\n## Best Practices\n\n- **Naming Conventions**: Use a consistent and well-defined naming convention for all metrics to ensure clarity and ease of analysis.\n- **Granularity**: Choose an appropriate level of granularity for metrics to balance detail and storage requirements.\n- **Retention Policies**: Define retention policies for metrics to manage storage space and ensure data is available for historical analysis.\n\n## Integration\n\nThis 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.\n\n## Prerequisites\n\n- Access to metrics collection tools (Prometheus, StatsD, CloudWatch)\n- Network connectivity to metric sources\n- Metrics storage configuration in ${CLAUDE_SKILL_DIR}\u002Fmetrics\u002F\n- Understanding of metrics taxonomy\n\n## Instructions\n\n1. Design consistent metrics naming convention\n2. Select appropriate aggregation tool for environment\n3. Configure metric collection from all sources\n4. Set up centralized storage and retention policies\n5. Create dashboards for visualization\n6. Define alerts for critical metrics\n\n## Output\n\n- Metrics aggregation configuration files\n- Unified naming convention documentation\n- Dashboard definitions for key metrics\n- Alert rules for performance thresholds\n- Integration guides for metric sources\n\n## Error Handling\n\nIf metrics aggregation fails:\n- Verify network connectivity to sources\n- Check authentication credentials\n- Validate metrics format compatibility\n- Review storage capacity and retention\n- Ensure aggregation tool configuration\n\n## Resources\n\n- Prometheus aggregation documentation\n- StatsD protocol specifications\n- CloudWatch metrics API reference\n- Metrics naming best practices","# Metrics Aggregator\n\nAggregate and centralize performance metrics from applications, databases, caches, and infrastructure into Prometheus, StatsD, or CloudWatch with unified naming conventions.\n\n## Overview\n\nThis 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.\n\n## How It Works\n\n1. **Metrics Taxonomy Design**: Claude assists in defining a clear and consistent naming convention for metrics across all systems.\n2. **Aggregation Tool Selection**: Claude helps select the appropriate metrics aggregation tool (e.g., Prometheus, StatsD, CloudWatch) based on the user's environment and requirements.\n3. **Configuration and Integration**: Claude guides the configuration of the chosen aggregation tool and its integration with various data sources.\n4. **Dashboard and Alert Setup**: Claude helps set up dashboards for visualizing metrics and defining alerts for critical performance indicators.\n\n## When to Use This Skill\n\nThis skill activates when you need to:\n- Centralize performance metrics from multiple applications and systems.\n- Design a consistent metrics naming convention.\n- Choose the right metrics aggregation tool for your needs.\n- Set up dashboards and alerts for performance monitoring.\n\n## Examples\n\n### Example 1: Centralizing Application and System Metrics\n\nUser request: \"Aggregate application and system metrics into Prometheus.\"\n\nThe skill will:\n1. Guide the user in defining metrics for applications (e.g., request latency, error rates) and systems (e.g., CPU usage, memory utilization).\n2. Help configure Prometheus to scrape metrics from the application and system endpoints.\n\n### Example 2: Setting Up Alerts for Database Performance\n\nUser request: \"Centralize database metrics and set up alerts for slow queries.\"\n\nThe skill will:\n1. Help the user define metrics for database performance (e.g., query execution time, connection pool usage).\n2. Guide the user in configuring the aggregation tool to collect these metrics from the database.\n3. Assist in setting up alerts in the aggregation tool to notify the user when query execution time exceeds a defined threshold.\n\n## Best Practices\n\n- **Naming Conventions**: Use a consistent and well-defined naming convention for all metrics to ensure clarity and ease of analysis.\n- **Granularity**: Choose an appropriate level of granularity for metrics to balance detail and storage requirements.\n- **Retention Policies**: Define retention policies for metrics to manage storage space and ensure data is available for historical analysis.\n\n## Integration\n\nThis 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.\n\n## Prerequisites\n\n- Access to metrics collection tools (Prometheus, StatsD, CloudWatch)\n- Network connectivity to metric sources\n- Metrics storage configuration in ${CLAUDE_SKILL_DIR}\u002Fmetrics\u002F\n- Understanding of metrics taxonomy\n\n## Instructions\n\n1. Design consistent metrics naming convention\n2. Select appropriate aggregation tool for environment\n3. Configure metric collection from all sources\n4. Set up centralized storage and retention policies\n5. Create dashboards for visualization\n6. Define alerts for critical metrics\n\n## Output\n\n- Metrics aggregation configuration files\n- Unified naming convention documentation\n- Dashboard definitions for key metrics\n- Alert rules for performance thresholds\n- Integration guides for metric sources\n\n## Error Handling\n\nIf metrics aggregation fails:\n- Verify network connectivity to sources\n- Check authentication credentials\n- Validate metrics format compatibility\n- Review storage capacity and retention\n- Ensure aggregation tool configuration\n\n## Resources\n\n- Prometheus aggregation documentation\n- StatsD protocol specifications\n- CloudWatch metrics API reference\n- Metrics naming best practices",{"name":5,"author":43,"license":14,"version":44,"description":7,"allowed-tools":45,"compatible-with":46},"Jeremy Longshore \u003Cjeremy@intentsolutions.io>","1.0.0","Read, Write, Bash(prometheus:*), Bash(metrics:*), Bash(monitoring:*), Grep","claude-code, codex, openclaw","master","3f5d983eb4ef375b749adcd6b07ec03bd82ae8a8","claude-code\u002Fplugins-plus-skills\u002Fplugins\u002Fperformance\u002Fmetrics-aggregator\u002Fskills\u002Faggregating-performance-metrics",0,"https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills","https:\u002F\u002Fgithub.com\u002Fmicsapp","2026-03-20 11:24:18",{"source":8,"skillName":5,"commands":55,"prompt":65,"zipAvailable":66},[56,59,62],{"tool":57,"command":58},"npx","npx skills add micsapp\u002Fmicstec-skills --skill aggregating-performance-metrics",{"tool":60,"command":61},"bunx","bunx skills add micsapp\u002Fmicstec-skills --skill aggregating-performance-metrics",{"tool":63,"command":64},"pnpm","pnpm dlx skills add micsapp\u002Fmicstec-skills --skill aggregating-performance-metrics","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fclaude-code\u002Fplugins-plus-skills\u002Fplugins\u002Fperformance\u002Fmetrics-aggregator\u002Fskills\u002Faggregating-performance-metrics\u002FSKILL.md",true,[68,74,80],{"path":69,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":72,"sourceHtmlUrl":73},"assets\u002FREADME.md","ASSET","资产文件",203,"https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fclaude-code\u002Fplugins-plus-skills\u002Fplugins\u002Fperformance\u002Fmetrics-aggregator\u002Fskills\u002Faggregating-performance-metrics\u002Fassets\u002FREADME.md",{"path":75,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":78,"sourceHtmlUrl":79},"references\u002FREADME.md","REFERENCE","参考文档",62,"https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fclaude-code\u002Fplugins-plus-skills\u002Fplugins\u002Fperformance\u002Fmetrics-aggregator\u002Fskills\u002Faggregating-performance-metrics\u002Freferences\u002FREADME.md",{"path":81,"resourceType":82,"resourceTypeDesc":83,"sizeBytes":84,"sourceHtmlUrl":85},"scripts\u002FREADME.md","SCRIPT","脚本",746,"https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fclaude-code\u002Fplugins-plus-skills\u002Fplugins\u002Fperformance\u002Fmetrics-aggregator\u002Fskills\u002Faggregating-performance-metrics\u002Fscripts\u002FREADME.md",[87,124,153,173,193,218],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":103,"publishedAt":38},"01M6HBTJ02FXBFG9NYEHHYAP52","azure-apim-architecture","Analyzes and explains Azure API Management architecture decisions for enterprise API marketplace implementations using VNet Internal mode, Front Door, hybrid authentication, and multi-environment strategies. Use when discussing APIM component selection, network topology, cost optimization, or comparing alternatives like workspaces vs instances, VNet Internal vs External mode, or Front Door vs Application Gateway.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fcopilot-agent-skills\u002F.github\u002Fskills\u002Fazure-apim-architecture\u002FSKILL.md",[93,98],{"categoryNo":94,"categoryName":95,"taxonomyType":96,"taxonomyTypeDesc":97},"01JBSEEDCAT000000000000010","后端与接口","SCENARIO","使用场景",{"categoryNo":99,"categoryName":100,"taxonomyType":101,"taxonomyTypeDesc":102},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[104,105,106,107,108,109,110,111,112,113,114,115,116,117,118,119,120,121,122,123],"architecture","azure","azure apim architecture","component","authentication","gateway","topology","Optimization","network","api","team","environment","multi-environment","workspaces","instances","selection","strategies","azure api management","mode","for",{"skillNo":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":128,"categories":129,"keywords":138,"publishedAt":38},"01M6HBT7J4H082JEEA670B3EQ9","apiops-deployment","Guides deployment of Azure API Management infrastructure using Infrastructure as Code (Bicep\u002FTerraform), CI\u002FCD pipelines (GitHub Actions\u002FAzure DevOps), and APIOps workflows. Use when deploying APIM, creating pipelines, or implementing dev→test→prod promotion strategies.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fcopilot-agent-skills\u002F.github\u002Fskills\u002Fapiops-deployment\u002FSKILL.md",[130,131,134,137],{"categoryNo":94,"categoryName":95,"taxonomyType":96,"taxonomyTypeDesc":97},{"categoryNo":132,"categoryName":133,"taxonomyType":96,"taxonomyTypeDesc":97},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":135,"categoryName":136,"taxonomyType":96,"taxonomyTypeDesc":97},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":99,"categoryName":100,"taxonomyType":101,"taxonomyTypeDesc":102},[139,140,141,142,105,143,37,144,145,146,147,148,113,114,120,149,150,121,151,152],"deployment","apiops deployment","workflows","azure devops","infrastructure","infrastructure as code","actions","ci","github actions","github-actions","as","guides","CI\u002FCD","implementing",{"skillNo":154,"name":155,"nameZh":6,"description":156,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":157,"categories":158,"keywords":160,"publishedAt":38},"01M6HBT2HEA23THNE9E00GYQBE","apim-policy-authoring","Creates production-ready Azure API Management policy XML for authentication (OAuth 2.0, JWT validation, subscription keys), rate limiting, CORS configuration, error handling, and API transformations. Use when implementing API security, access control, or request\u002Fresponse processing logic.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fcopilot-agent-skills\u002F.github\u002Fskills\u002Fapim-policy-authoring\u002FSKILL.md",[159],{"categoryNo":94,"categoryName":95,"taxonomyType":96,"taxonomyTypeDesc":97},[161,162,163,164,105,108,113,114,165,28,166,167,168,169,170,121,171,172,152,123],"policy","authoring","apim policy authoring","security","access","ready","api security","Access Control","error","processing","cors configuration","production-ready",{"skillNo":174,"name":175,"nameZh":6,"description":176,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":177,"categories":178,"keywords":181,"publishedAt":38},"01M6HBSY65SB29J9WE9KYD0K6T","api-security-review","Reviews Azure API Management configurations for security vulnerabilities, OWASP API Security Top 10 compliance, VNet Internal mode validation, Private Link verification, and Azure Security Benchmark alignment. Use when performing security audits, pre-deployment validation, or compliance reviews.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fcopilot-agent-skills\u002F.github\u002Fskills\u002Fapi-security-review\u002FSKILL.md",[179,180],{"categoryNo":94,"categoryName":95,"taxonomyType":96,"taxonomyTypeDesc":97},{"categoryNo":99,"categoryName":100,"taxonomyType":101,"taxonomyTypeDesc":102},[182,164,183,113,167,184,105,139,185,186,187,188,114,189,121,190,191,192,122,123],"review","security review","api security review","benchmark","verification","owasp","owasp-api","alignment","azure security","reviews","top",{"skillNo":194,"name":195,"nameZh":6,"description":196,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":197,"categories":198,"keywords":199,"publishedAt":38},"01M6HBSRW4PDFE6K4F8JYPZQ05","jira-cli","Interact with Jira from the command line to create, list, view, edit, and transition issues, manage sprints and epics, and perform common Jira workflows. Use when the user asks about Jira tasks, tickets, issues, sprints, or needs to manage project work items.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fawesome-copilot-agents\u002Fskills\u002Fjira-cli\u002FSKILL.md",[],[200,201,202,141,203,204,205,206,113,207,208,209,210,211,212,213,214,215,216,217],"cli","jira","jira cli","init","tasks","create","issues","common","work","command","edit","list","view","project","project work","token","line","sprints",{"skillNo":219,"name":220,"nameZh":6,"description":221,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":222,"categories":223,"keywords":224,"publishedAt":38},"01M6HBSNS3JHMW603G47TWE31H","calculator","Performs arbitrary-precision arithmetic calculations including addition, subtraction, multiplication, division, and exponents. Use when the user asks to calculate, compute, or evaluate math expressions, or when precise decimal arithmetic is needed to avoid floating-point errors.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fawesome-copilot-agents\u002Fskills\u002Fcalculator\u002FSKILL.md",[],[220,225,226,227,228,229,230,28,231,232],"npm","js","calculate","node","math","user","compute","errors"]