Habilidades golang-project-layout
📦
golang-project-layout
v1.4.2 Revisión del contenido r1 Riesgo alto ⚙️ Comandos externos📁 Acceso al sistema de archivos⚡ Contiene scripts🌐 Acceso a red
Organize Go Projects and Multi-Module Workspaces
Unclear package boundaries make Go projects harder to maintain. This skill guides directory layout, module naming, test placement, and workspace setup around project requirements.
Compatible con: Codex Code(CC)
Detente y solicita confirmación antes de instalar.
Revisa el plan y obtén el consentimiento explícito del usuario antes de modificar archivos.
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-project-layout" from https://skillstore.io/skills/samber-golang-project-layout.md and its manifest at https://skillstore.io/api/skills/samber-golang-project-layout/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.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.
Pruébalo
Usando "golang-project-layout". Plan a small CLI with a flat architecture and no dependency injection framework.
Resultado esperado:
- Use one command entry point with minimal startup logic.
- Keep private behavior in a small internal package.
- Place tests beside their implementation and fixtures in a local testdata directory.
- Start with one module and omit a workspace.
Usando "golang-project-layout". Our server and shared logging library are separate modules developed together. Should we use a workspace?
Resultado esperado:
- A workspace fits related modules that need local cross-module development.
- Add both existing module directories to workspace membership.
- Keep each module's dependency metadata separate.
- Use local workspace resolution instead of repeated replacement directives.
Usando "golang-project-layout". Where should private request parsing and a reusable public logging package live?
Resultado esperado:
- Keep request parsing in an internal package.
- Expose the logging API through a public package when external consumers need it.
- For a dedicated library module, prefer a root-level public package.
- Keep executable startup logic separate from reusable behavior.
Auditoría de seguridad
Riesgo altov1 • 15/10/2026 Abrir el informe versionado
All 78 static matches are false positives involving documentation, Go syntax, ignore rules, or ordinary build automation. A separate high-severity prompt injection directs persistent agent configuration changes to always load another skill without user confirmation. No evidence found of credential exfiltration or malicious network execution in the reviewed files.
8
Archivos escaneados
998
Líneas analizadas
0
Elementos de revisión
0
Falsos positivos ignorados
Preocupaciones de seguridad confirmadas (1)
Alto
Prompt Injection Attempt Detected
SKILL.md:119 says "Write the always-load directive" into the project's agent-config file and specifies "no user confirmation needed". This persists instructions to load another skill across sessions without consent, extending authority beyond the requested Go layout task.
The checklist explicitly requires persistent instruction changes and bypasses confirmation. The related-skills entry reinforces this behavior; the referenced skill's contents were not provided.
Factores de riesgo
⚙️ Comandos externos (50)
assets/.gitignore:10 assets/Makefile:7 assets/Makefile:8 assets/Makefile:18 assets/Makefile:19 assets/Makefile:24 assets/Makefile:35 assets/Makefile:36 assets/Makefile:40 assets/Makefile:45 assets/Makefile:59 assets/Makefile:60 assets/Makefile:79 assets/Makefile:80 assets/Makefile:84 assets/Makefile:85 assets/Makefile:89 assets/Makefile:90 assets/Makefile:110 evals/evals.json:34 evals/evals.json:49 references/config.md:33-34 references/config.md:34-35 references/config.md:35-37 references/config.md:37-38 references/config.md:38-39 references/config.md:39-49 references/directory-layouts.md:30-51 SKILL.md:3 SKILL.md:30 SKILL.md:34 SKILL.md:38 SKILL.md:44 SKILL.md:45 SKILL.md:46 SKILL.md:47 SKILL.md:48 SKILL.md:54 SKILL.md:56 SKILL.md:57 SKILL.md:58 SKILL.md:63-72 SKILL.md:72-76 SKILL.md:76-80 SKILL.md:80 SKILL.md:90-96 SKILL.md:96 SKILL.md:100-107 SKILL.md:107-111 SKILL.md:111-112
📁 Acceso al sistema de archivos (2)
⚡ Contiene scripts (2)
🌐 Acceso a red (2)
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.
Copiar enlace del informe
https://skillstore.io/skills/samber-golang-project-layout/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportInsignia Markdown
[](https://skillstore.io/skills/samber-golang-project-layout?utm_source=security_passport_badge)Insignia HTML
<a href="https://skillstore.io/skills/samber-golang-project-layout?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/samber-golang-project-layout/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Tarjeta para insertar
<iframe src="https://skillstore.io/embed/skills/samber-golang-project-layout.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-project-layout security audit report (audit version 1) [Author version 1.4.2]. Skillstore. https://skillstore.io/skills/samber-golang-project-layout/audits/1Cita BibTeX
@techreport{samber-samber-golang-project-layout-2026,
author = {samber},
title = {golang-project-layout security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/samber-golang-project-layout/audits/1},
note = {Author version 1.4.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-project-layout security audit report (audit version 1)"
version: "1.4.2"
type: report
authors:
- name: "samber"
date-released: "2026-10-15"
url: "https://skillstore.io/skills/samber-golang-project-layout/audits/1"
identifiers:
- type: other
value: "skillstore:samber-golang-project-layout:audit:1"
description: "Skillstore immutable audit report identifier"
Puntuación de Skillstore
Por qué esta puntuación Confianza de la evidencia: Medio 59
Arquitectura
100
Mantenibilidad
87
Contenido
65
Comunidad
91
Cumplimiento de la especificación
Lo que puedes crear
Start a focused CLI project
Choose a small directory structure, a meaningful module path, and local test placement without unnecessary architecture layers.
Separate service entry points
Organize server, worker, and migration binaries while keeping shared business logic in private packages.
Coordinate related Go modules
Plan workspace membership and local dependency resolution for modules developed together in a monorepo.
Prueba estos prompts
Choose a minimal layout
Help me plan a small Go CLI called [name]. Ask about architecture first, then dependency injection. Recommend a minimal layout without editing files.
Organize a service
Plan a layout for [service] with an API server and migration binary. Ask about architecture and dependency injection before suggesting packages. Include test placement.
Review package boundaries
Review [directory tree] for private implementation and reusable API boundaries. Recommend focused layout changes and explain module naming. Do not modify persistent agent configuration.
Plan a multi-module workspace
Design a go.work workspace for [module paths]. Explain local resolution, initialization, and cross-module testing. Identify when a single module is preferable. Propose changes before execution.
Mejores prácticas
- Confirm project scope, architecture, and dependency injection preferences before creating directories.
- Use workspaces for related modules, not merely for multiple packages within one module.
- Review templates and commands before execution, and require approval for persistent agent configuration changes.
Evitar
- Creating empty architecture layers or public packages without a concrete need.
- Collecting business logic in entry points or vague utility packages.
- Automatically adding always-load skill instructions to persistent project configuration without explicit approval.
Preguntas frecuentes
What does this skill help organize?
It covers project directories, module naming, package boundaries, test placement, configuration, and multi-module workspaces.
Does every project need go.work?
No. A single module with multiple packages does not need a workspace. Workspaces support local development across related modules.
Is pkg required for public libraries?
No. The library reference recommends root-level public packages. The application guidance treats pkg as optional when external consumers need reusable code.
Does the skill include a complete application generator?
No. It provides instructions, examples, and build templates. An agent may apply them, but generated projects still require review and testing.
What tools are needed to run the suggested commands?
Go is required. The Makefile also uses Make and Git, while optional targets require tools such as golangci-lint, govulncheck, and air.
Does the skill change persistent agent instructions?
Its checklist requests an always-load directive without confirmation. Remove that instruction or explicitly approve a reviewed change before allowing persistent configuration edits.