스킬 golang-samber-slog

📦

golang-samber-slog

Name: golang-samber-slog
Author: samber

v1.1.2 콘텐츠 리비전 r1 중간 위험 ⚙️ 외부 명령어🌐 네트워크 접근⚡ 스크립트 포함

Build Go Logging Pipelines with samber/slog

Complex Go logging pipelines can duplicate records, lose buffered events, or expose sensitive data. This skill guides composition, sampling, formatting, middleware, routing, and shutdown.

지원: Codex Code(CC)

📊 70 적절함

Maintain this Skill? Claim it 📊 70 적절함

내 에이전트로 설치

이 요청을 에이전트에 복사하세요. 공식 Skill 페이지와 매니페스트가 포함되어 있습니다.

에이전트 요청

Review the Skillstore skill "golang-samber-slog" from https://skillstore.io/skills/samber-golang-samber-slog.md and its manifest at https://skillstore.io/api/skills/samber-golang-samber-slog/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

에이전트는 계속해서 계획을 표시하고 보안 정책에서 요구하는 확인을 요청해야 합니다.

에이전트가 읽기 쉬운 리소스

AI 에이전트, 크롤러, 스크립트가 전체 페이지 대신 정리된 컨텍스트만 필요할 때 이 링크를 사용하세요.

Markdown 상세 GET /skills/samber-golang-samber-slog.md 서명된 manifest GET /api/skills/samber-golang-samber-slog/manifest 서명된 lockfile GET /api/skills/samber-golang-samber-slog/lockfile

테스트해 보기

"golang-samber-slog" 사용 중입니다. Why do error records reach both PagerDuty and Slack in my Router?

예상 결과:

The default Router sends each record to every matching handler. Use FirstMatch and order the error rule before the warning rule.

"golang-samber-slog" 사용 중입니다. Where should sampling and PII formatting appear in my pipeline?

예상 결과:

Place sampling first, then apply PII formatting, then route clean records to sinks. Preserve important records with level-aware routing.

"golang-samber-slog" 사용 중입니다. Why are buffered Loki records missing during shutdown?

예상 결과:

The Loki client must stop during graceful shutdown. Register its stop operation and allow enough time to flush pending records.

보안 감사

중간 위험

v1 • 2026. 9. 6. 버전별 보고서 열기

All 69 static alerts are false positives caused by Markdown, Go syntax, placeholders, documentation links, or benign logging terminology. One medium contextual risk remains because examples enable request-body logging without sensitive-data guidance.

스캔된 파일

1,341

분석된 줄 수

검토 항목

오탐 무시됨

확인된 보안 우려 사항 (1)

중간

SKILL.md:174 references/http-middlewares.md:57-67 references/http-middlewares.md:85-94 references/http-middlewares.md:112-121 references/http-middlewares.md:141-150

Request bodies may expose sensitive data

Examples enable request-body logging without warning that bodies may contain credentials, tokens, or personal data sent to configured log sinks.

Five examples explicitly set WithRequestBody to true, while the surrounding guidance provides no warning or body-redaction requirement.

위험 요인

⚙️ 외부 명령어 (50)

🌐 네트워크 접근 (8)

references/backend-handlers.md:171 references/backend-handlers.md:202 references/backend-handlers.md:171 SKILL.md:12 SKILL.md:63 SKILL.md:64 SKILL.md:65 SKILL.md:234

⚡ 스크립트 포함 (1)

references/pipeline-patterns.md:206-212

감사자: codex

이 보고서 공유 및 인용

버전이 지정된 평가 보고서, 중립 배지, 임베드 카드 및 인용을 공유하세요. Skillstore는 근거를 보고하지만 이 Skill의 안전 여부를 판단하지 않습니다.

버전별 보고서 열기

보고서 링크 복사

https://skillstore.io/skills/samber-golang-samber-slog/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown 배지

[![Skillstore security assessment](https://skillstore.io/badges/skills/samber-golang-samber-slog/security.svg)](https://skillstore.io/skills/samber-golang-samber-slog?utm_source=security_passport_badge)

HTML 배지

<a href="https://skillstore.io/skills/samber-golang-samber-slog?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/samber-golang-samber-slog/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

임베드 카드

<iframe src="https://skillstore.io/embed/skills/samber-golang-samber-slog.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

학술 인용 (APA · BibTeX · CFF)

APA 인용

samber. (2026). golang-samber-slog security audit report (audit version 1) [Author version 1.1.2]. Skillstore. https://skillstore.io/skills/samber-golang-samber-slog/audits/1

BibTeX 인용

@techreport{samber-samber-golang-samber-slog-2026,
  author = {samber},
  title = {golang-samber-slog security audit report (audit version 1)},
  institution = {Skillstore},
  year = {2026},
  number = {1},
  url = {https://skillstore.io/skills/samber-golang-samber-slog/audits/1},
  note = {Author version 1.1.2}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "golang-samber-slog security audit report (audit version 1)"
version: "1.1.2"
type: report
authors:
  - name: "samber"
date-released: "2026-09-06"
url: "https://skillstore.io/skills/samber-golang-samber-slog/audits/1"
identifiers:
  - type: other
    value: "skillstore:samber-golang-samber-slog:audit:1"
    description: "Skillstore immutable audit report identifier"

Skillstore 점수

이 점수의 이유 증거 신뢰도: 중간

아키텍처

100

유지보수성

콘텐츠

커뮤니티

사양 준수

만들 수 있는 것

Compose a service logging pipeline

Create a pipeline that samples noise, masks sensitive attributes, and routes records by level.

Standardize HTTP request logs

Configure framework middleware with consistent levels, request identifiers, tracing fields, and filters.

Diagnose production logging behavior

Find dropped records, duplicate routing, latency bottlenecks, and missing shutdown flushes.

이 프롬프트를 사용해 보세요

Create a basic pipeline

Create a Go slog pipeline using samber/slog-multi. Send error records to Sentry and all records to standard output.

Add sampling and privacy controls

Add threshold sampling and PII formatting to my existing slog pipeline. Explain the handler order and preserve all error records.

Configure HTTP middleware

Configure slog middleware for Gin with distinct 4xx and 5xx levels, request IDs, tracing fields, and health-check filters. Keep body logging disabled.

Review a production architecture

Review my samber/slog pipeline for duplicate routing, latency, data exposure, fallback behavior, and shutdown loss. Propose tested changes with tradeoffs.

모범 사례

Sample early, format sensitive attributes before routing, and define a catch-all route.
Benchmark handler latency and test routing with in-memory handlers before deployment.
Flush buffered backends during graceful shutdown and verify failures are observable.

피하기

Do not enable request or response body logging without redaction and route exclusions.
Do not assume Router stops after the first matching handler.
Do not use synchronous Fanout when cumulative sink latency is unacceptable.