Habilidades golang-spf13-viper
📦

golang-spf13-viper

v1.1.2 Revisión del contenido r1 Seguro ⚙️ Comandos externos🔑 Variables de entorno🌐 Acceso a red📁 Acceso al sistema de archivos

Configure Go Applications with Viper

Layered Go configuration can fail through incorrect precedence, binding, or decoding. This skill provides focused Viper patterns for reliable setup, testing, and reloads.

Compatible con: Codex Code(CC)
Maintain this Skill? Claim it 🥉 78 Bronce

Instalar con mi Agente

Copia esta solicitud en tu Agente. Incluye la página canónica del Skill y el manifiesto.

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

Tu Agente debe seguir mostrando su plan y solicitar cualquier confirmación exigida por la política de seguridad.

Recursos legibles por agentes

Usa estos enlaces cuando un agente de IA, crawler o script necesite contexto limpio en vez de leer la página completa.

Detalle Markdown GET /skills/samber-golang-spf13-viper.md Manifest firmado GET /api/skills/samber-golang-spf13-viper/manifest Lockfile firmado GET /api/skills/samber-golang-spf13-viper/lockfile

Pruébalo

Usando "golang-spf13-viper". Why does an environment variable for database.host remain ignored?

Resultado esperado:

The diagnosis identifies the missing dot-to-underscore key replacer and lists the required prefix, replacer, and automatic binding sequence.

Usando "golang-spf13-viper". How should an optional configuration file be loaded?

Resultado esperado:

The response distinguishes a missing file from parsing or permission errors, allowing only the missing-file case to continue.

Usando "golang-spf13-viper". How can a service reload configuration without data races?

Resultado esperado:

The response proposes candidate decoding, validation, synchronized replacement, error logging, and retention of the previous valid configuration.

Auditoría de seguridad

Seguro
v1 • 23/9/2026 Abrir el informe versionado

All 97 static alerts are contextual false positives. The matches are documentation syntax, Go tags, evaluation prose, conventional configuration examples, loopback addresses, or transparent upstream links.

7
Archivos escaneados
1,310
Líneas analizadas
0
Elementos de revisión
0
Falsos positivos ignorados

Factores de riesgo

⚙️ Comandos externos (50)
evals/evals.json:131 references/unmarshal.md:18-19 references/unmarshal.md:19-20 references/unmarshal.md:20-22 references/unmarshal.md:22-23 references/unmarshal.md:23-24 references/unmarshal.md:24-31 references/unmarshal.md:44-45 references/unmarshal.md:45-46 references/unmarshal.md:46-55 references/unmarshal.md:61-62 references/unmarshal.md:62-69 references/unmarshal.md:117-118 references/unmarshal.md:118-122 references/unmarshal.md:122-123 references/unmarshal.md:123-125 references/unmarshal.md:133-134 references/unmarshal.md:134-136 references/watch-and-reload.md:47-48 references/watch-and-reload.md:48-67 SKILL.md:3 SKILL.md:36 SKILL.md:37 SKILL.md:40-42 SKILL.md:42-50 SKILL.md:50 SKILL.md:52-58 SKILL.md:58-65 SKILL.md:65-71 SKILL.md:71-80 SKILL.md:80-82 SKILL.md:82-84 SKILL.md:84-90 SKILL.md:90-97 SKILL.md:97-99 SKILL.md:99 SKILL.md:103 SKILL.md:105-111 SKILL.md:111-113 SKILL.md:113-117 SKILL.md:117 SKILL.md:119-121 SKILL.md:121-123 SKILL.md:123-124 SKILL.md:124-128 SKILL.md:128-130 SKILL.md:130 SKILL.md:132 SKILL.md:136 SKILL.md:140-143
🔑 Variables de entorno (5)
evals/evals.json:344 evals/evals.json:349 references/binding-and-env.md:32 references/binding-and-env.md:36 references/sources-and-formats.md:24
🌐 Acceso a red (6)
references/sources-and-formats.md:90 references/sources-and-formats.md:90 SKILL.md:12 SKILL.md:31 SKILL.md:32 SKILL.md:190
📁 Acceso al sistema de archivos (4)
references/sources-and-formats.md:67 references/sources-and-formats.md:38 references/sources-and-formats.md:67 SKILL.md:73
La auditoría estática y semántica completada más reciente no detectó hallazgos de seguridad confirmados. Esto no demuestra que el skill no tenga efectos secundarios.
Auditado por: codex
Compartir y citar este informe

Comparte el informe de evaluación versionado, la insignia neutral, la tarjeta insertable y las citas. Skillstore presenta evidencias sin decidir si este Skill es seguro.

Abrir el informe versionado
Evaluación de seguridad

Copiar enlace del informe

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

Insignia Markdown

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

Insignia HTML

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

Tarjeta para insertar

<iframe src="https://skillstore.io/embed/skills/samber-golang-spf13-viper.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>
Citas académicas (APA · BibTeX · CFF)

Cita APA

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

Cita BibTeX

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

Puntuación de Skillstore

Por qué esta puntuación Confianza de la evidencia: Medio
45
Arquitectura
100
Mantenibilidad
87
Contenido
65
Comunidad
91
Cumplimiento de la especificación

Lo que puedes crear

Configure a Go Service

Create layered file and environment configuration with predictable precedence and optional config files.

Connect Cobra Flags

Bind CLI flags before execution so explicit values override environment variables and files correctly.

Harden Runtime Reloads

Validate candidate settings and synchronize updates before replacing active service configuration.

Prueba estos prompts

Create Basic Configuration 
Set up Viper for my Go service using a YAML file, MYAPP-prefixed environment variables, and sensible defaults.
Diagnose Environment Binding 
Explain why MYAPP_DATABASE_HOST does not override database.host, then provide the correct Viper prefix, replacer, and AutomaticEnv setup.
Refactor Configuration Tests 
Refactor my Viper tests to avoid shared global state. Use isolated instances and temporary environment values.
Design Safe Hot Reload 
Design a production Viper reload flow that debounces events, decodes a candidate, validates it, and atomically updates synchronized application state.

Mejores prácticas

  • Configure the environment prefix and key replacer before enabling automatic environment lookup.
  • Use explicit mapstructure tags and validate decoded configuration before application startup or reload.
  • Create a separate Viper instance for each test and protect shared runtime configuration with synchronization.

Evitar

  • Do not rely on the global Viper instance across tests because state persists between cases.
  • Do not ignore every ReadInConfig error because malformed or unreadable files require attention.
  • Do not update shared configuration directly from a watch callback without validation and synchronization.

Preguntas frecuentes

Can Viper be used without Cobra?
Yes. Services can use Viper for files and environment variables without adding a command framework.
Which configuration source has highest priority?
Explicit Set values lead, followed by flags, environment variables, files, remote stores, and defaults.
Why do nested environment keys fail?
Viper preserves dots unless a key replacer maps them to underscores before environment lookup.
How should optional config files be handled?
Continue only for ConfigFileNotFoundError. Return parsing, permission, and other real errors.
How can tests avoid Viper state leakage?
Create a new Viper instance per test and use the test framework's temporary environment support.
Does this skill access credentials or remote services?
No. It documents binding and remote-provider patterns, but it does not read credentials or initiate connections.

Detalles del desarrollador

Autor

samber

Licencia

MIT

Versión del autor

v1.1.2

Revisión de Skillstore

r1

Repositorio

https://github.com/samber/cc-skills-golang/tree/19a0626ae8565d27a7b7bdf59d8d99d94d7e284c/skills/golang-spf13-viper

Ref.

2aa351cb09c29b7287d263bd8ea81e9bee3b2a61

Actualidad del mantenimiento

30/9/2026

Uso

0 descargas · 0 vistas

Estructura de archivos

📁 evals/

📄 evals.json

📁 references/

📄 binding-and-env.md

📄 sources-and-formats.md

📄 testing-and-isolation.md

📄 unmarshal.md

📄 watch-and-reload.md

📄 SKILL.md