update-api-reference — community update-api-reference, sandbox, community, ide skills

v1.0.0

Acerca de este Skill

Perfecto para Agentes de Mantenimiento de API que necesitan actualizaciones automatizadas de documentación de OpenAPI con anotaciones de swaggo. Regenerate the OpenAPI reference documentation after adding, modifying, or removing API endpoints in sandbox-api. Run this whenever handler signatures, route paths, or swag annotations change.

blaxel-ai blaxel-ai
[9]
[5]
Updated: 3/10/2026

Killer-Skills Review

Decision support comes first. Repository text comes second.

Reference-Only Page Review Score: 7/11

This page remains useful for operators, but Killer-Skills treats it as reference material instead of a primary organic landing page.

Original recommendation layer Concrete use-case guidance Explicit limitations and caution
Review Score
7/11
Quality Score
39
Canonical Locale
en
Detected Body Locale
en

Perfecto para Agentes de Mantenimiento de API que necesitan actualizaciones automatizadas de documentación de OpenAPI con anotaciones de swaggo. Regenerate the OpenAPI reference documentation after adding, modifying, or removing API endpoints in sandbox-api. Run this whenever handler signatures, route paths, or swag annotations change.

¿Por qué usar esta habilidad?

Habilita a los agentes a regenerar referencias de API utilizando documentos de OpenAPI y anotaciones de swaggo, garantizando una documentación precisa y actualizada con un solo comando, aprovechando las especificaciones de Swagger 2.0 y OpenAPI.

Mejor para

Perfecto para Agentes de Mantenimiento de API que necesitan actualizaciones automatizadas de documentación de OpenAPI con anotaciones de swaggo.

Casos de uso accionables for update-api-reference

Regenerar la documentación de API después de cambios en los puntos de conexión
Actualizar referencias de nombres de tipo para garantizar la coherencia
Convertir Swagger 2.0 a OpenAPI para garantizar la compatibilidad

! Seguridad y limitaciones

  • Requiere anotaciones de swaggo en el código del controlador de Go
  • Necesita configuración de makefile para la generación automatizada de documentación
  • Limitado a las especificaciones de OpenAPI y Swagger 2.0

Why this page is reference-only

  • - Current locale does not satisfy the locale-governance contract.
  • - The underlying skill quality score is below the review floor.

Source Boundary

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

After The Review

Decide The Next Action Before You Keep Reading Repository Material

Killer-Skills should not stop at opening repository instructions. It should help you decide whether to install this skill, when to cross-check against trusted collections, and when to move into workflow rollout.

Labs Demo

Browser Sandbox Environment

⚡️ Ready to unleash?

Experience this Agent in a zero-setup browser environment powered by WebContainers. No installation required.

Boot Container Sandbox

FAQ & Installation Steps

These questions and steps mirror the structured data on this page for better search understanding.

? Frequently Asked Questions

What is update-api-reference?

Perfecto para Agentes de Mantenimiento de API que necesitan actualizaciones automatizadas de documentación de OpenAPI con anotaciones de swaggo. Regenerate the OpenAPI reference documentation after adding, modifying, or removing API endpoints in sandbox-api. Run this whenever handler signatures, route paths, or swag annotations change.

How do I install update-api-reference?

Run the command: npx killer-skills add blaxel-ai/sandbox/update-api-reference. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.

What are the use cases for update-api-reference?

Key use cases include: Regenerar la documentación de API después de cambios en los puntos de conexión, Actualizar referencias de nombres de tipo para garantizar la coherencia, Convertir Swagger 2.0 a OpenAPI para garantizar la compatibilidad.

Which IDEs are compatible with update-api-reference?

This skill is compatible with Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Use the Killer-Skills CLI for universal one-command installation.

Are there any limitations for update-api-reference?

Requiere anotaciones de swaggo en el código del controlador de Go. Necesita configuración de makefile para la generación automatizada de documentación. Limitado a las especificaciones de OpenAPI y Swagger 2.0.

How To Install

  1. 1. Open your terminal

    Open the terminal or command line in your project directory.

  2. 2. Run the install command

    Run: npx killer-skills add blaxel-ai/sandbox/update-api-reference. The CLI will automatically detect your IDE or AI agent and configure the skill.

  3. 3. Start using the skill

    The skill is now active. Your AI agent can use update-api-reference immediately in the current project.

! Reference-Only Mode

This page remains useful for installation and reference, but Killer-Skills no longer treats it as a primary indexable landing page. Read the review above before relying on the upstream repository instructions.

Upstream Repository Material

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

Upstream Source

update-api-reference

Install update-api-reference, an AI agent skill for AI agent workflows and automation. Review the use cases, limitations, and setup path before rollout.

SKILL.md
Readonly
Upstream Repository Material
The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.
Supporting Evidence

Update the API Reference (OpenAPI Docs)

The OpenAPI spec is generated from swaggo annotations in the Go handler code. After changing any endpoint, regenerate the docs.

Run the Full Reference Update

bash
1make reference

This single command:

  1. Runs swag init to parse Go annotations → generates sandbox-api/docs/swagger.yaml and docs.go
  2. Fixes type name references (replaces filesystem.Directory with Directory)
  3. Converts Swagger 2.0 → OpenAPI 3.0 via swagger2openapi
  4. Adds Bearer auth security scheme to all endpoints
  5. Runs fixopenapi.sh for additional patches

The output file is sandbox-api/docs/openapi.yml.


How Swag Annotations Work

Annotations are Go comments above handler functions. Example:

go
1// HandleGetFile retrieves a file from the sandbox filesystem. 2// 3// @Summary Get file or directory 4// @Description Returns file content or directory listing 5// @Tags filesystem 6// @Produce application/octet-stream 7// @Param path path string true "File path" 8// @Success 200 {string} string "File content" 9// @Failure 404 {object} ErrorResponse 10// @Router /filesystem/{path} [get] 11func (h *FileSystemHandler) HandleGetFile(c *gin.Context) {

Key annotation fields:

  • @Summary — short description (shown in API reference)
  • @Description — longer explanation
  • @Tags — group endpoints in the UI (filesystem, process, network, codegen)
  • @Param — parameter: name location type required "description"
    • locations: path, query, body, header
  • @Success / @Failure — response codes with type and description
  • @Router — path and HTTP method [get|post|put|delete]
  • @Accept / @Produce — request/response content types

Where the Docs Live

FilePurpose
sandbox-api/docs/openapi.ymlFinal OpenAPI 3.0 spec (commit this)
sandbox-api/docs/docs.goAuto-generated Go embed of the spec
sandbox-api/docs/fixopenapi.shPost-processing patches

After Adding a New Endpoint

  1. Add swag annotations to your handler function
  2. Register the route in sandbox-api/src/api/router.go
  3. Run make reference
  4. Review the diff in sandbox-api/docs/openapi.yml to confirm your endpoint appears correctly
  5. Commit both the handler changes and the updated openapi.yml and docs.go

Verify the Generated Docs

Open the Swagger UI at http://localhost:8080/swagger/index.html while the dev server is running. It reads docs.go which is embedded at build time.


Troubleshooting

  • swag: command not found: Run make dependencies first
  • Missing endpoint in output: Check that your handler has a @Router annotation and the function is exported
  • Type not found: Ensure the struct is in the same package or imported and annotated with @Description
  • swagger2openapi not found: Run npm install -g swagger2openapi or npx swagger2openapi (the Makefile uses npx)

Habilidades relacionadas

Looking for an alternative to update-api-reference or another community skill for your workflow? Explore these related open-source skills.

Ver todo

openclaw-release-maintainer

Logo of openclaw
openclaw

Your own personal AI assistant. Any OS. Any Platform. The lobster way. 🦞

333.8k
0
Inteligencia Artificial

widget-generator

Logo of f
f

Generar complementos de widgets personalizables para el sistema de feeds de prompts.chat

149.6k
0
Inteligencia Artificial

flags

Logo of vercel
vercel

El Marco de React

138.4k
0
Navegador

pr-review

Logo of pytorch
pytorch

Tensores y redes neuronales dinámicas en Python con fuerte aceleración de GPU

98.6k
0
Desarrollador