Token导航 LogoToken导航TokenDH.com
中转站排行榜
开发external-servicegithub未标认证来源可访问clear审计通过

monitoring-apis（监控 API）

Agent Skill

monitoring-apis 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息，适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态，以及是否会触发联网、命令执行或文件读写。

总安装

759

周安装

31

GitHub Stars

2,101

下载量

246
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息，不托管安装包，也不代用户安装。

GitHub

来源数

3

许可证

MIT

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手，先确认命令和权限，再让它执行。

请帮我安装这个 Agent Skill：monitoring-apis（监控 API）
来源仓库：https://github.com/jeremylongshore/claude-code-plugins-plus-skills
仓库路径：skills/monitoring-apis
安装命令：
npx skills add https://github.com/jeremylongshore/claude-code-plugins-plus-skills --skill monitoring-apis
安装前请先检查当前环境是否支持对应 CLI，并向我确认将要执行的命令、安装目录、联网范围和文件读写权限；确认后再执行。

命令行安装

复制命令到本机终端执行。不同来源提供的安装方式可能略有差异；本站展示可直接复制的安装命令，安装前请核对来源页面。

skills.shnpx skills
npx skills add https://github.com/jeremylongshore/claude-code-plugins-plus-skills --skill monitoring-apis

简介

monitoring-apis 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息。

  • 适合在 Codex、Claude、Cursor、Gemini CLI 中围绕仓库状态、代码变更或协作事项进行整理。
  • 通过 npx skills add 命令从指定 GitHub 仓库安装并使用。
  • 安装前建议确认权限范围、维护状态，以及是否会触发联网、命令执行或文件读写。
  • 适用宿主包括 Codex、Claude、Cursor、Gemini CLI，接入前应确认版本、权限和运行环境要求。

SKILL.md

Monitoring APIs

Overview

Build real-time API monitoring with metrics collection (request rate, latency percentiles, error rates), health check endpoints, and alerting rules. Instrument API middleware to emit Prometheus metrics or StatsD counters, configure Grafana dashboards with SLO tracking, and implement synthetic monitoring probes for uptime verification.

Prerequisites

  • Prometheus + Grafana stack, or Datadog/New Relic/CloudWatch for metrics and dashboards
  • Metrics client library: prom-client (Node.js), prometheus_client (Python), or Micrometer (Java)
  • Alerting channel configured: PagerDuty, Slack webhook, or email for alert routing
  • Structured logging library: Winston, Pino (Node.js), structlog (Python), or Logback (Java)
  • Synthetic monitoring tool: Checkly, Uptime Robot, or custom cron-based health probes

Instructions

  1. Examine existing middleware and logging setup using Grep and Read to identify current observability coverage and gaps.
  2. Implement metrics middleware that records per-request data: http_request_duration_seconds histogram (with method, path, status labels), http_requests_total counter, and http_requests_in_flight gauge.
  3. Create a /health endpoint returning structured health status including dependency checks (database connectivity, cache availability, external service reachability) with response time for each.
  4. Add a /ready endpoint separate from health that returns 503 during startup initialization and graceful shutdown, for load balancer integration.
  5. Configure histogram buckets aligned with SLO targets: [0.01, 0.05, 0.1, 0.25, 0.5, 1, 2.5, 5, 10] seconds for comprehensive latency distribution.
  6. Build Grafana dashboard panels: request rate (QPS), p50/p95/p99 latency, error rate percentage, active connections, and per-endpoint breakdown.
  7. Define alerting rules: error rate > 5% for 5 minutes (critical), p99 latency > 2s for 10 minutes (warning), health check failure for 3 consecutive probes (critical).
  8. Implement synthetic monitoring that sends periodic requests to critical endpoints from external locations, measuring availability and latency from the consumer perspective.
  9. Add SLO tracking with error budget calculation: define SLO (99.9% availability, p95 < 500ms), compute burn rate, and alert when error budget consumption exceeds projected pace.

See ${CLAUDE_SKILL_DIR}/references/implementation.md for the full implementation guide.

Output

  • ${CLAUDE_SKILL_DIR}/src/middleware/metrics.js - Prometheus metrics collection middleware
  • ${CLAUDE_SKILL_DIR}/src/routes/health.js - Health check and readiness endpoints
  • ${CLAUDE_SKILL_DIR}/monitoring/dashboards/ - Grafana dashboard JSON definitions
  • ${CLAUDE_SKILL_DIR}/monitoring/alerts/ - Alerting rule definitions (Prometheus AlertManager or Grafana)
  • ${CLAUDE_SKILL_DIR}/monitoring/synthetic/ - Synthetic monitoring probe scripts
  • ${CLAUDE_SKILL_DIR}/monitoring/slo.yaml - SLO definitions and error budget configuration

Error Handling

ErrorCauseSolution
Metrics cardinality explosionHigh-cardinality labels (user ID, request ID) on metricsUse bounded label values only (method, status code, endpoint group); aggregate user-level data in logs
Health check false positiveHealth endpoint returns 200 but dependent service is degradedInclude dependency checks with individual status; use structured response with degraded state
Alert fatigueToo many low-severity alerts firing during normal operationsTune alert thresholds using historical baselines; implement alert grouping and deduplication
Dashboard data gapMetrics not collected during deployment rollout windowConfigure Prometheus scrape interval < deployment duration; use push-based metrics during deploys
SLO miscalculationError budget calculation uses wrong time window or includes planned maintenanceExclude maintenance windows from SLO calculation; align window with business reporting period

Refer to ${CLAUDE_SKILL_DIR}/references/errors.md for comprehensive error patterns.

Examples

RED method dashboard: Request rate, Error rate, and Duration panels per endpoint, with drill-down from overview to individual endpoint detail, including top-10 slowest endpoints by p99.

SLO-based alerting: Define 99.9% availability SLO with 30-day rolling window, alert when 1-hour burn rate exceeds 14.4x (consuming daily error budget in 1 hour), with PagerDuty escalation.

Dependency health matrix: Dashboard showing real-time health status of all downstream dependencies (database, cache, external APIs) with latency sparklines and circuit breaker state indicators.

See ${CLAUDE_SKILL_DIR}/references/examples.md for additional examples.

Resources

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

04

需要参考平台分布和安装热度时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明，方便继续核验

能力 4

补充不同宿主或平台的使用分布数据

能力 5

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用；具体调用方式请以来源页面和 README 为准。

平台分布

Claude Code

29.6%
按下载量换算73

mcpjam

24.61%
按下载量换算61

openhands

18.1%
按下载量换算45

windsurf

12.82%
按下载量换算32

zencoder

7.35%
按下载量换算18

crush

3.29%
按下载量换算8

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

external-service

该 Skill 可能调用第三方服务、云服务或外部模型 API，使用前需要确认账号、额度、数据发送范围和服务条款。

安装前确认

本站仅展示第三方公开信息，不托管安装包，不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。

来源信息

GitHub 仓库

github.com

/jeremylongshore/claude-code-plugins-plus-skills

SKILL.md 来源

github.com

/jeremylongshore/claude-code-plugins-plus-skills/tree/main/skills/monitoring-apis

skills-sh

skills.sh

/jeremylongshore/claude-code-plugins-plus-skills/monitoring-apis

agentskills-to

agentskills.to

/jeremylongshore/claude-code-plugins-plus-skills/monitoring-apis

继续浏览同类 Skills

更多开发 Skills（21,746）返回 Skills 目录

上一个 Skill

monitoring-alerting-commerce（监控警报商业）

monitoring-alerting-commerce 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息，适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态，以及是否会触发联网、命令执行或文件读写。

下一个 Skill

monitoring-database-transactions（监控数据库事务）

用于辅助数据库表结构、查询语句、迁移脚本和数据维护任务。它适合让 Agent 分析 schema、编写 SQL、排查查询问题、整理索引或生成迁移建议。使用时需要明确数据库类型、连接环境和目标表，区分只读分析与写入变更；涉及删除、更新、迁移和批量导入时，应优先 dry-run、备份或事务保护，避免误操作。