| schemaVersion | 2026-04-11T00:00:00.000Z |
| skillId | infra/observability-backend |
| name | observability-backend |
| displayName | Backend Observability |
| description | Use when working on logs, metrics, traces, dashboards, alerts, and production debugging for backend systems. Focus on diagnosability, signal quality, SLOs, and incident response. |
| aliases | ["observability-backend","Backend Observability","observability backend","observabilitybackend","可观测性","日志","指标","链路追踪","告警","服务端","server side","observability","调试","排查","定位问题"] |
| version | 0.1.0 |
| sourceHash | sha256:94e597c2ff29238e6d58d5cfc7e503a1c8ac55c97d59f244fded67bb7f1b31dd |
| domain | infra |
| departmentTags | ["infra-platform"] |
| sceneTags | ["debug","incident"] |
Backend Observability
Use this skill when the task involves logs, metrics, traces, dashboards, alerts, and production debugging for backend systems.
Goal: produce reliable engineering guidance and implementation steps focused on diagnosability, signal quality, SLOs, and incident response.
Working model
- Identify the affected system, data, users, and failure modes.
- Define invariants, inputs, outputs, ownership, and rollback needs.
- Prefer small, auditable changes with explicit validation.
- Call out security, performance, concurrency, and data-loss risks when relevant.
- Finish with concrete verification steps and residual risks.
Rules
- Ground recommendations in the current codebase or runtime evidence.
- Prefer explicit contracts, typed boundaries, and defensive validation.
- Do not hide operational concerns behind generic best practices.
- Include negative cases, edge cases, and failure behavior.
- For review tasks, list findings first with file and line references when possible.
- For test or performance tasks, define the workload, success criteria, and measurement method.
Checklist
- Are assumptions and ownership boundaries explicit?
- Are risky changes reversible or safely deployable?
- Are observability and diagnostics sufficient for production issues?
- Are tests or validation steps targeted to the actual risk?
- Are security and data-integrity concerns addressed?
