📦

golang-swagger

Name: golang-swagger
Author: samber

v1.1.2 Révision du contenu r1 Sûr ⚙️ Commandes externes🌐 Accès réseau

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.

Prend en charge: Codex Code(CC)

🥉 78 Bronze

Maintain this Skill? Claim it 🥉 78 Bronze

Installer avec mon Agent

Copiez cette demande dans votre Agent. Elle contient la page Skill de référence et le manifeste.

Demande d’agent

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.

Votre Agent doit toujours présenter son plan et demander toute confirmation exigée par la politique de sécurité.

Ressources lisibles par les agents

Utilisez ces liens lorsqu’un Agent IA, un crawler ou un script a besoin d’un contexte propre au lieu de lire toute la page.

Détail Markdown GET /skills/samber-golang-swagger.md manifest signé GET /api/skills/samber-golang-swagger/manifest lockfile signé GET /api/skills/samber-golang-swagger/lockfile

Tester

Utilisation de « golang-swagger ». A Gin service has generated docs, but Swagger UI displays an empty specification.

Résultat attendu:

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.

Utilisation de « golang-swagger ». An endpoint returns a response envelope whose data field contains a user object.

Résultat attendu:

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

Utilisation de « golang-swagger ». A user model needs documented roles, score limits, examples, and a hidden secret field.

Résultat attendu:

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

Audit de sécurité

Sûr

v1 • 23/09/2026 Ouvrir le rapport versionné

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.

Fichiers analysés

518

Lignes analysées

Éléments à examiner

Faux positifs ignorés

Facteurs de risque

⚙️ Commandes externes (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

🌐 Accès réseau (4)

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

Le dernier audit statique et sémantique terminé n’a détecté aucun constat de sécurité confirmé. Cela ne prouve pas que le skill est sans effets secondaires.

Audité par: codex

Partager et citer ce rapport

Partagez le rapport d’évaluation versionné, le badge neutre, la carte intégrable et les citations. Skillstore présente les preuves sans décider si ce Skill est sûr.

Ouvrir le rapport versionné

Copier le lien du rapport

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

Badge 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)

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>

Carte intégrable

<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>

Citations académiques (APA · BibTeX · CFF)

Citation 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

Citation 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"

Score Skillstore

Pourquoi ce score Niveau de confiance des preuves: Moyen

Architecture

100

Maintenabilité

Contenu

Communauté

100

Conformité aux spécifications

Ce que vous pouvez créer

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.

Essayez ces prompts

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.

Bonnes pratiques

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.

Éviter

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.