菜单
Adds structured metric collection stubs to a service, exporting counters and histograms under a consistent naming scheme. Use when you want to instrument a service with metrics that follow a standard naming convention so they can be consumed by a shared dashboard.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Extracts a reusable code pattern from the current repo and authors a portable, validated Agent Skill. Use when you want to capture a logging setup, CI/CD pipeline, observability stack, async messaging pattern, frontend component library, feature-flag middleware, or any other repeatable engineering pattern so it can be replayed across other repos. Produces: a standard-conformant SKILL.md, parameterized code templates in assets/templates/, a PARAMETERS.md documenting every placeholder, then runs validate-skill.sh, scan-leaks.sh, and dry-run-replay.sh as a tiered quality gate. Output is ready to publish via references/publishing.md.
Regression fixture for dry-run-replay header-skip drift.
A clean skill containing a git commit SHA, a UUID, and an embedded base64 image asset — none of which are secrets and none must trip the scanner.
Sets up structured logging for a service using a configurable log level and service name. Produces a logger.config file ready for ingestion by your logging pipeline. Works with any service that reads configuration from a flat config file.
A skill that accidentally contains an AWS access key — should be caught by the scanner.
A skill containing bare base64 secrets ending in equals-sign padding, which must not evade the entropy detector.
| name | instrumentation |
| description | Adds structured metric collection stubs to a service, exporting counters and histograms under a consistent naming scheme. Use when you want to instrument a service with metrics that follow a standard naming convention so they can be consumed by a shared dashboard. |
| x-spec-version | 1 |
Wires metric collection into a service by adding an exporter configuration
and a stub metrics registry. Substitute {{SERVICE_NAME}} and
{{METRICS_PORT}} before deploying.
Use when you are adding observability to a service and want a repeatable, consistent metrics setup.
PARAMETERS.md and fill in all required placeholders for your target service.assets/templates/metrics.config to your service's config directory.{{METRICS_PORT}}.http://localhost:{{METRICS_PORT}}/metrics.Before:
# No metrics exporter configured.
After:
[metrics]
service = {{SERVICE_NAME}}
port = {{METRICS_PORT}}
format = prometheus
{{METRICS_PORT}} is already bound, choose an alternative and update the placeholder.{{SERVICE_NAME}} is globally unique within your metrics namespace.All configurable placeholders are documented in PARAMETERS.md.