스킬 golang-swagger

📦

golang-swagger

Name: golang-swagger
Author: samber

v1.1.2 콘텐츠 리비전 r1 안전 ⚙️ 외부 명령어🌐 네트워크 접근

Document Go APIs with Swagger

Go API annotations often become incomplete, inconsistent, or difficult to generate. This skill guides accurate OpenAPI documentation, Swagger UI wiring, and schema generation with swaggo.

지원: Codex Code(CC)

🥉 78 브론즈

Maintain this Skill? Claim it 🥉 78 브론즈

내 에이전트로 설치

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

에이전트 요청

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

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

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

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

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

테스트해 보기

"golang-swagger" 사용 중입니다. A Gin service has generated docs, but Swagger UI displays an empty specification.

예상 결과:

The fix is to register the generated docs package with a blank import, mount the Gin Swagger handler, regenerate the specification, and verify the route.

"golang-swagger" 사용 중입니다. An endpoint returns a response envelope whose data field contains a user object.

예상 결과:

The documentation should use nested response composition so the generated schema shows the concrete user model inside the envelope.

"golang-swagger" 사용 중입니다. A user model needs documented roles, score limits, examples, and a hidden secret field.

예상 결과:

Use struct tags for allowed values, numeric bounds, example values, and Swagger-only exclusion while preserving required JSON serialization.

보안 감사

안전

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

All 89 static findings are false positives caused by Markdown backticks, documentation URLs, Go annotations, evaluation text, or tool metadata rather than executable threats. Review of the three scanned files found no prompt-injection text, unauthorized network behavior, or data-exfiltration intent.

스캔된 파일

518

분석된 줄 수

검토 항목

오탐 무시됨

위험 요인

⚙️ 외부 명령어 (50)

evals/evals.json:6 evals/evals.json:7-9 evals/evals.json:9-18 evals/evals.json:18-19 evals/evals.json:19-21 evals/evals.json:21-30 evals/evals.json:30 evals/evals.json:33 evals/evals.json:42-48 evals/evals.json:48 evals/evals.json:78 evals/evals.json:81-90 evals/evals.json:90 evals/evals.json:102 evals/evals.json:114 evals/evals.json:126 evals/evals.json:129-130 evals/evals.json:130 references/swag-cli.md:114-115 references/swag-cli.md:115-118 SKILL.md:36 SKILL.md:42-46 SKILL.md:46-48 SKILL.md:48 SKILL.md:50-53 SKILL.md:53-57 SKILL.md:57-72 SKILL.md:72-74 SKILL.md:74-78 SKILL.md:78-83 SKILL.md:83-89 SKILL.md:89 SKILL.md:91-107 SKILL.md:107-111 SKILL.md:111 SKILL.md:113-129 SKILL.md:129-131 SKILL.md:131-133 SKILL.md:133-135 SKILL.md:135 SKILL.md:136 SKILL.md:137-138 SKILL.md:138-139 SKILL.md:139-141 SKILL.md:141 SKILL.md:143-145 SKILL.md:145-147 SKILL.md:147-148 SKILL.md:148-149 SKILL.md:149

🌐 네트워크 접근 (4)

SKILL.md:12 SKILL.md:175 SKILL.md:176 SKILL.md:234

가장 최근에 완료된 정적·의미론적 감사에서 확인된 보안 발견 사항이 감지되지 않았습니다. 이는 스킬에 부작용이 없음을 증명하지 않습니다.

감사자: codex

이 보고서 공유 및 인용

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

버전별 보고서 열기

보고서 링크 복사

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

Markdown 배지

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

HTML 배지

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

임베드 카드

<iframe src="https://skillstore.io/embed/skills/samber-golang-swagger.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-swagger security audit report (audit version 1) [Author version 1.1.2]. Skillstore. https://skillstore.io/skills/samber-golang-swagger/audits/1

BibTeX 인용

@techreport{samber-samber-golang-swagger-2026,
  author = {samber},
  title = {golang-swagger security audit report (audit version 1)},
  institution = {Skillstore},
  year = {2026},
  number = {1},
  url = {https://skillstore.io/skills/samber-golang-swagger/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-swagger security audit report (audit version 1)"
version: "1.1.2"
type: report
authors:
  - name: "samber"
date-released: "2026-09-23"
url: "https://skillstore.io/skills/samber-golang-swagger/audits/1"
identifiers:
  - type: other
    value: "skillstore:samber-golang-swagger:audit:1"
    description: "Skillstore immutable audit report identifier"

Skillstore 점수

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

아키텍처

100

유지보수성

콘텐츠

커뮤니티

100

사양 준수

만들 수 있는 것

Document a New Go API

Create endpoint annotations, response schemas, and a generated Swagger UI for a new Go service.

Repair an Existing Specification

Find annotation gaps, stale generated files, invalid response types, and missing security requirements.

Standardize Team Documentation

Apply consistent schemas, naming, constraints, examples, and framework wiring across multiple Go services.

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

Add Basic Endpoint Docs

Document this Go endpoint with a summary, parameters, success response, failure response, and route annotation. Explain where each comment belongs.

Wire Swagger UI

Connect generated swag documentation to my Go framework and explain the required imports, route registration, generation command, and verification steps.

Model Complex Responses

Improve this API schema for nested response data, map values, timestamps, byte fields, enums, examples, and validation constraints. Identify unsupported patterns.

Audit API Documentation

Review this Go service documentation for missing routes, inaccurate schemas, inconsistent annotations, stale generated files, and missing security requirements. Return prioritized fixes.

모범 사례

Regenerate documentation after annotation or model changes, then review the generated schema for accuracy.
Keep security definitions and endpoint requirements explicit, consistent, and aligned with deployed authentication.
Use named response types and focused annotations when generic maps or envelopes would produce ambiguous schemas.

피하기

Do not publish stale generated documentation that differs from current handlers or models.
Do not hide fields with JSON exclusion when the application still needs to serialize them.
Do not expose production Swagger UI without authentication, authorization, or an intentional deployment policy.