본문으로 건너뛰기
cccskills
무료GitHub에 공개

observability-and-instrumentation

Designs or reviews logs, metrics, traces, alerts, correlation, dashboards, and diagnostic instrumentation so failures and performance changes can be detected and explained at component boundaries. Use for observability work, incident readiness, instrumentation, or production diagnostics. Not for fixing a specific incident before reproducing it or for adding noisy logging without an operational question.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

thiientv/godmode
설치 방법 보기

포함된 파일(2)

  • SKILL.md2.4 KB
  • references/signal-design.md501 B

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

Observability and Instrumentation

Start from the question an operator must answer, then emit the smallest safe signal that answers it.

Design sequence

  1. Name the user or business signal, SLO/error budget, failure mode, and responder.
  2. Map the request or job across boundaries and choose correlation/trace IDs, cardinality, sampling, and clock conventions.
  3. Define structured logs for state transitions and failures, metrics for rates/latency/saturation, and traces for cross-service causality.
  4. Include useful dimensions without high-cardinality or secret data. Redact tokens, PII, payloads, and credentials by default.
  5. Add alerts with actionable thresholds, runbook links, ownership, deduping, and a recovery path. Avoid alerts that merely report expected retries.
  6. Verify the signal in a safe environment and test the failure path that should emit it.

Prepare operational baselines

For release and incident use, record the pre-change baseline, freshness, expected variance, promotion or paging threshold, and recovery signal. Include one user or business outcome alongside technical health where possible. A dashboard without a decision owner and action threshold is reference material, not a guardrail.

Preserve a correlation path from release identifier to request, job, dependency, and user-visible outcome. Ensure incident responders can distinguish absent traffic, stale telemetry, collector failure, and healthy zero values.

Read signal-design.md. Instrumentation must not change correctness or become the only source of truth for business data.

Completion condition

An operator can detect the important failure, correlate it across boundaries, understand the likely cause, and follow a bounded response without exposing sensitive data. release-engineering can consume the baseline as a promotion gate; incident-response can consume it as live evidence.

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

agent-evaluation

무료

Designs and runs reproducible evaluations for AI agents, prompts, tools, skills, and model-backed workflows using realistic datasets, isolated baselines, objective assertions, rubric grading, trajectory analysis, cost/latency tracking, and regression comparison. Use when measuring agent quality, optimizing skill triggering, comparing prompts or models, or gating an AI feature release. Not for ordinary deterministic unit tests.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

thiientv/godmode992026년 8월 26일 업데이트

api-and-interface-design

무료

Designs or reviews HTTP, REST, GraphQL, RPC, CLI, webhook, event, and service interfaces with explicit inputs, outputs, errors, compatibility, idempotency, pagination, authentication, versioning, and observability. Use when introducing or changing an API or cross-component contract. Not for internal implementation details with no boundary or for debugging one API failure; use root-cause-debugging there.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

thiientv/godmode992026년 8월 26일 업데이트

architecture-review

무료

Reviews an existing codebase for structural friction, unclear ownership, leaky or shallow interfaces, excessive coupling, misplaced state, poor testability, and risky dependency direction, then prioritizes evidence-backed improvement candidates. Use for architecture audits, modularization, modernization, or recurring cross-cutting change pain. Not for designing one new interface, simplifying a local function, or fixing a reproduced bug.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

thiientv/godmode992026년 8월 26일 업데이트

behavior-validation

무료

Validates a running application, CLI, API, service, or generated artifact as a user or operator against a prewritten observable behavior contract while remaining source-blind. Use for acceptance checks, runtime proof, anti-fake probes, release smoke tests, or an independent companion to code review. Not for source-quality findings, root-cause diagnosis, or visual design judgment outside the contract.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

thiientv/godmode992026년 8월 26일 업데이트

branch-integration

무료

Closes a completed development branch by checking the final diff and proof, presenting merge, pull-request, keep, or discard options, and cleaning up only after the user or repository workflow chooses a path. Use when feature work is complete and the branch must be integrated or retired. Not for claiming a feature is complete before verification.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

thiientv/godmode992026년 8월 26일 업데이트

browser-testing

무료

Tests a real web user flow with a browser by asserting semantic behavior, network and loading states, keyboard access, responsive layouts, and stable visual evidence. Use for browser bugs, end-to-end UI behavior, responsive or accessibility checks, and screenshot baselines. Not for static source review without a browser or for backend-only tests.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

thiientv/godmode992026년 8월 26일 업데이트

thiientv의 스킬 모두 보기

이 스킬의 문제 신고