[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M76HAX3MTRXVG6MTHDW7SMNZ":3,"skill-same:01M76HAX3MTRXVG6MTHDW7SMNZ":73},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":44,"commitSha":45,"skillDirectory":46,"forksCount":47,"repositoryHtmlUrl":48,"repositoryHomepageUrl":49,"ownerHtmlUrl":50,"ownerBlogUrl":51,"ownerDescription":52,"updatedAt":53,"install":54,"resources":66},"01M76HAX3MTRXVG6MTHDW7SMNZ","golang-swagger",null,"Golang OpenAPI\u002FSwagger documentation with swaggo\u002Fswag — annotation comments (@Summary, @Param, @Success, @Router, @Security), swag init code generation, framework integrations (gin, echo, fiber, chi, net\u002Fhttp), security definitions (Bearer\u002FJWT, OAuth2, API key), and struct tags (swaggertype, enums, example, swaggerignore). Apply when adding or maintaining Swagger\u002FOpenAPI docs in a Go project, or when the codebase imports github.com\u002Fswaggo\u002Fswag, github.com\u002Fswaggo\u002Fgin-swagger, github.com\u002Fswaggo\u002Fecho-swagger, github.com\u002Fswaggo\u002Fhttp-swagger, or github.com\u002Fswaggo\u002Ffiles.","bg-szy\u002FTOP-SKILLS","bg-szy","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F106576190?v=4","01M73A4E8KPV67SFXRY8XZGNBX","ShuZhiyong","01M73A4E96MQ294MHM74TZBVQD",6,"MIT","https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketplace\u002Fgolang-swagger\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: golang-swagger\ndescription: \"Golang OpenAPI\u002FSwagger documentation with swaggo\u002Fswag — annotation comments (@Summary, @Param, @Success, @Router, @Security), swag init code generation, framework integrations (gin, echo, fiber, chi, net\u002Fhttp), security definitions (Bearer\u002FJWT, OAuth2, API key), and struct tags (swaggertype, enums, example, swaggerignore). Apply when adding or maintaining Swagger\u002FOpenAPI docs in a Go project, or when the codebase imports github.com\u002Fswaggo\u002Fswag, github.com\u002Fswaggo\u002Fgin-swagger, github.com\u002Fswaggo\u002Fecho-swagger, github.com\u002Fswaggo\u002Fhttp-swagger, or github.com\u002Fswaggo\u002Ffiles.\"\nuser-invocable: true\nlicense: MIT\ncompatibility: Designed for Claude Code, Codex or similar harness. Requires go and swag CLI.\nmetadata:\n  author: samber\n  version: \"1.1.2\"\n  openclaw:\n    emoji: \"📋\"\n    homepage: https:\u002F\u002Fgithub.com\u002Fsamber\u002Fcc-skills-golang\n    requires:\n      bins:\n        - go\n        - swag\n    install:\n      - kind: go\n        package: github.com\u002Fswaggo\u002Fswag\u002Fcmd\u002Fswag@latest\n        bins: [swag]\n    skill-library-version: \"2.0.0-rc5\"\nallowed-tools: Read Edit Write Glob Grep Bash(go:*) Bash(golangci-lint:*) Bash(git:*) Agent WebFetch mcp__context7__resolve-library-id mcp__context7__query-docs Bash(swag:*) AskUserQuestion Bash(godig:*) Bash(gopls:*) LSP mcp__gopls__*\npaths:\n  - \"**\u002F*.go\"\n---\n\n**Persona:** You are a Go API documentation engineer. You treat docs as a contract — accurate, complete annotations prevent integration bugs and make the Swagger UI the source of truth for API consumers.\n\n**Modes:**\n\n- **Build** — adding Swagger to a new or existing Go project: set up the toolchain, annotate handlers, generate docs, wire the UI endpoint.\n- **Audit** — reviewing existing swagger annotations for completeness, correctness, and security coverage.\n\n**Dependencies:**\n\n- swag: `go install github.com\u002Fswaggo\u002Fswag\u002Fcmd\u002Fswag@latest`\n\n## Setup\n\nThree steps to get Swagger UI running:\n\n```bash\nswag init                        # generates docs\u002F with docs.go, swagger.json, swagger.yaml\nswag init -g cmd\u002Fapi\u002Fmain.go     # if general info is not in main.go\nswag fmt                         # format annotation comments (like go fmt)\n```\n\nImport the `docs` package to register the spec. Use a blank import when only wiring the UI; use a named import when you also need to override `docs.SwaggerInfo` at runtime:\n\n```go\nimport _ \"yourmodule\u002Fdocs\"          \u002F\u002F blank: registers spec, no identifier\nimport docs \"yourmodule\u002Fdocs\"       \u002F\u002F named: use when overriding SwaggerInfo\n```\n\nWire the UI endpoint — pick your framework:\n\n```go\n\u002F\u002F Gin\nr.GET(\"\u002Fswagger\u002F*any\", ginSwagger.WrapHandler(swaggerFiles.Handler))\n\n\u002F\u002F Echo\ne.GET(\"\u002Fswagger\u002F*\", echoSwagger.WrapHandler)\n\n\u002F\u002F Fiber\napp.Get(\"\u002Fswagger\u002F*\", fiberSwagger.WrapHandler(swaggerFiles.Handler))\n\n\u002F\u002F net\u002Fhttp\nmux.Handle(\"\u002Fswagger\u002F\", httpSwagger.Handler(swaggerFiles.Handler))\n\n\u002F\u002F Chi\nr.Get(\"\u002Fswagger\u002F*\", httpSwagger.Handler(swaggerFiles.Handler))\n```\n\nAccess the UI at `\u002Fswagger\u002Findex.html`.\n\nFor dynamic host\u002Fbasepath (multi-environment), use a named import and override before serving:\n\n```go\nimport docs \"yourmodule\u002Fdocs\"\n\ndocs.SwaggerInfo.Host     = os.Getenv(\"API_HOST\")\ndocs.SwaggerInfo.BasePath = \"\u002Fapi\u002Fv1\"\n```\n\n[Full CLI reference](references\u002Fswag-cli.md)\n\n## General API Info\n\nPlace in `main.go` (or the file passed via `-g`). These annotations define the top-level spec:\n\n```go\n\u002F\u002F @title           My API\n\u002F\u002F @version         1.0\n\u002F\u002F @description     Short description of the API.\n\u002F\u002F @host            localhost:8080\n\u002F\u002F @BasePath        \u002Fapi\u002Fv1\n\u002F\u002F @schemes         http https\n\n\u002F\u002F @contact.name    API Support\n\u002F\u002F @contact.email   support@example.com\n\u002F\u002F @license.name    Apache 2.0\n\n\u002F\u002F @securityDefinitions.apikey Bearer\n\u002F\u002F @in header\n\u002F\u002F @name Authorization\n\u002F\u002F @description Type \"Bearer\" followed by a space and the JWT token.\n```\n\n## Operation Annotations\n\nAnnotate each handler function. The standard doc comment (`\u002F\u002F FuncName godoc`) must precede swag annotations — it anchors indentation for `swag fmt`.\n\n```go\n\u002F\u002F ShowAccount godoc\n\u002F\u002F @Summary      Get account by ID\n\u002F\u002F @Description  Returns account details for the given ID.\n\u002F\u002F @Tags         accounts\n\u002F\u002F @Accept       json\n\u002F\u002F @Produce      json\n\u002F\u002F @Param        id      path  int  true  \"Account ID\"\n\u002F\u002F @Param        filter  query string false \"Optional search filter\"\n\u002F\u002F @Success      200  {object}  model.Account\n\u002F\u002F @Success      204  \"No content\"\n\u002F\u002F @Failure      400  {object}  api.ErrorResponse\n\u002F\u002F @Failure      404  {object}  api.ErrorResponse\n\u002F\u002F @Router       \u002Faccounts\u002F{id} [get]\n\u002F\u002F @Security     Bearer\nfunc ShowAccount(c *gin.Context) {}\n```\n\n**@Param** format: `@Param \u003Cname> \u003Cin> \u003Ctype> \u003Crequired> \"\u003Cdescription>\" [attributes]`\n\n| `\u003Cin>`     | Usage                                |\n| ---------- | ------------------------------------ |\n| `path`     | URL path segment (`\u002Fusers\u002F{id}`)     |\n| `query`    | URL query string (`?filter=x`)       |\n| `body`     | Request body — type must be a struct |\n| `header`   | HTTP header                          |\n| `formData` | Multipart\u002Fform field                 |\n\nOptional attributes on `@Param`: `default(v)`, `minimum(n)`, `maximum(n)`, `minLength(n)`, `maxLength(n)`, `Enums(a,b,c)`, `example(v)`, `collectionFormat(multi)`.\n\n**@Success\u002F@Failure** format: `@Success \u003Ccode> {\u003Ckind>} \u003Ctype> \"\u003Cdescription>\"`\n\n| `\u003Ckind>`             | When             |\n| -------------------- | ---------------- |\n| `{object}`           | Single struct    |\n| `{array}`            | Slice of structs |\n| `string` \u002F `integer` | Primitive        |\n\n**Generics** (swag v2): `@Success 200 {object} api.Response[model.User]`\n\n**Nested composition**: `@Success 200 {object} api.Response{data=model.User}`\n\n## Security Definitions\n\nDefine once at the API level (in main.go), apply per endpoint with `@Security`.\n\n```go\n\u002F\u002F Bearer \u002F JWT\n\u002F\u002F @securityDefinitions.apikey Bearer\n\u002F\u002F @in header\n\u002F\u002F @name Authorization\n\n\u002F\u002F API key in header\n\u002F\u002F @securityDefinitions.apikey ApiKeyAuth\n\u002F\u002F @in header\n\u002F\u002F @name X-API-Key\n\n\u002F\u002F Basic auth\n\u002F\u002F @securityDefinitions.basic BasicAuth\n\n\u002F\u002F OAuth2 authorization code\n\u002F\u002F @securityDefinitions.oauth2.authorizationCode OAuth2\n\u002F\u002F @authorizationUrl https:\u002F\u002Fexample.com\u002Foauth\u002Fauthorize\n\u002F\u002F @tokenUrl https:\u002F\u002Fexample.com\u002Foauth\u002Ftoken\n\u002F\u002F @scope.read Read access\n\u002F\u002F @scope.write Write access\n```\n\nApply to an endpoint:\n\n```go\n\u002F\u002F @Security Bearer\n\u002F\u002F @Security OAuth2[read, write]\n\u002F\u002F @Security BasicAuth && ApiKeyAuth   \u002F\u002F AND — both required\n```\n\n## Struct Tags\n\nEnrich models without changing their Go type:\n\n```go\ntype CreateUserRequest struct {\n    Name   string `json:\"name\" example:\"Jane Doe\" minLength:\"2\" maxLength:\"100\"`\n    Role   string `json:\"role\" enums:\"admin,user,guest\" example:\"user\"`\n    Age    int    `json:\"age\" minimum:\"18\" maximum:\"120\"`\n    Avatar []byte `json:\"avatar\" swaggertype:\"string\" format:\"base64\"`\n    Secret string `json:\"-\" swaggerignore:\"true\"`  \u002F\u002F excluded from docs\n}\n```\n\n| Tag | Purpose |\n| --- | --- |\n| `example` | Example value shown in Swagger UI |\n| `enums` | Comma-separated allowed values |\n| `swaggertype` | Override detected type (e.g., `\"primitive,integer\"` for `time.Time`) |\n| `swaggerignore:\"true\"` | Exclude field from the generated schema |\n| `extensions` | Add OpenAPI extensions: `extensions:\"x-nullable,x-deprecated=true\"` |\n\n## Common Mistakes\n\n| Mistake | Why it breaks | Fix |\n| --- | --- | --- |\n| Missing `_ \"yourmodule\u002Fdocs\"` import | Schema not registered; UI loads empty | Add blank import in main.go or server init |\n| Stale `docs\u002F` after code changes | Docs diverge from implementation; consumers get wrong schema | Re-run `swag init` after every annotation change |\n| `@Param body` with primitive type | swag cannot derive schema from `string`; generation fails | Always use a named struct for body params |\n| No `@Security` on protected routes | Swagger UI shows no lock icon; testers send unauthenticated requests | Apply `@Security` to every authenticated endpoint |\n| General info annotations in the wrong file | swag silently skips them; spec has no title\u002Fhost | Use `-g \u003Cfile>` flag or move annotations to `main.go` |\n| Using `{object}` with a map type | swag cannot generate a schema for `map[string]any` without help | Use a named struct or annotate with `swaggertype` |\n| Multi-word `@Tags` without quotes | Tags split on spaces, producing malformed grouping | Quote tags with spaces: `@Tags \"user accounts\"` |\n\n## Cross-References\n\n- → See `samber\u002Fcc-skills-golang@golang-security` for securing the Swagger UI endpoint in production (disable or gate with auth middleware).\n- → See `samber\u002Fcc-skills-golang@golang-grpc` for gRPC — use grpc-gateway with its own OpenAPI generator instead of swag.\n\nThis skill is not exhaustive — refer to the swaggo\u002Fswag documentation and code examples for up-to-date API signatures and usage patterns:\n\n- For Go package docs, symbols, versions, importers, and known vulnerabilities, → See `samber\u002Fcc-skills-golang@golang-pkg-go-dev` skill (`godig`), preferred over Context7 for Go package facts.\n- To navigate this library's usage in your own code (definitions, call sites, diagnostics), → See `samber\u002Fcc-skills-golang@golang-gopls` skill (`gopls`).\n- Context7 remains a fallback for docs not indexed on pkg.go.dev.\n\nIf you encounter a bug or unexpected behavior in swag, open an issue at \u003Chttps:\u002F\u002Fgithub.com\u002Fswaggo\u002Fswag\u002Fissues>.\n","**Persona:** You are a Go API documentation engineer. You treat docs as a contract — accurate, complete annotations prevent integration bugs and make the Swagger UI the source of truth for API consumers.\n\n**Modes:**\n\n- **Build** — adding Swagger to a new or existing Go project: set up the toolchain, annotate handlers, generate docs, wire the UI endpoint.\n- **Audit** — reviewing existing swagger annotations for completeness, correctness, and security coverage.\n\n**Dependencies:**\n\n- swag: `go install github.com\u002Fswaggo\u002Fswag\u002Fcmd\u002Fswag@latest`\n\n## Setup\n\nThree steps to get Swagger UI running:\n\n```bash\nswag init                        # generates docs\u002F with docs.go, swagger.json, swagger.yaml\nswag init -g cmd\u002Fapi\u002Fmain.go     # if general info is not in main.go\nswag fmt                         # format annotation comments (like go fmt)\n```\n\nImport the `docs` package to register the spec. Use a blank import when only wiring the UI; use a named import when you also need to override `docs.SwaggerInfo` at runtime:\n\n```go\nimport _ \"yourmodule\u002Fdocs\"          \u002F\u002F blank: registers spec, no identifier\nimport docs \"yourmodule\u002Fdocs\"       \u002F\u002F named: use when overriding SwaggerInfo\n```\n\nWire the UI endpoint — pick your framework:\n\n```go\n\u002F\u002F Gin\nr.GET(\"\u002Fswagger\u002F*any\", ginSwagger.WrapHandler(swaggerFiles.Handler))\n\n\u002F\u002F Echo\ne.GET(\"\u002Fswagger\u002F*\", echoSwagger.WrapHandler)\n\n\u002F\u002F Fiber\napp.Get(\"\u002Fswagger\u002F*\", fiberSwagger.WrapHandler(swaggerFiles.Handler))\n\n\u002F\u002F net\u002Fhttp\nmux.Handle(\"\u002Fswagger\u002F\", httpSwagger.Handler(swaggerFiles.Handler))\n\n\u002F\u002F Chi\nr.Get(\"\u002Fswagger\u002F*\", httpSwagger.Handler(swaggerFiles.Handler))\n```\n\nAccess the UI at `\u002Fswagger\u002Findex.html`.\n\nFor dynamic host\u002Fbasepath (multi-environment), use a named import and override before serving:\n\n```go\nimport docs \"yourmodule\u002Fdocs\"\n\ndocs.SwaggerInfo.Host     = os.Getenv(\"API_HOST\")\ndocs.SwaggerInfo.BasePath = \"\u002Fapi\u002Fv1\"\n```\n\n[Full CLI reference](references\u002Fswag-cli.md)\n\n## General API Info\n\nPlace in `main.go` (or the file passed via `-g`). These annotations define the top-level spec:\n\n```go\n\u002F\u002F @title           My API\n\u002F\u002F @version         1.0\n\u002F\u002F @description     Short description of the API.\n\u002F\u002F @host            localhost:8080\n\u002F\u002F @BasePath        \u002Fapi\u002Fv1\n\u002F\u002F @schemes         http https\n\n\u002F\u002F @contact.name    API Support\n\u002F\u002F @contact.email   support@example.com\n\u002F\u002F @license.name    Apache 2.0\n\n\u002F\u002F @securityDefinitions.apikey Bearer\n\u002F\u002F @in header\n\u002F\u002F @name Authorization\n\u002F\u002F @description Type \"Bearer\" followed by a space and the JWT token.\n```\n\n## Operation Annotations\n\nAnnotate each handler function. The standard doc comment (`\u002F\u002F FuncName godoc`) must precede swag annotations — it anchors indentation for `swag fmt`.\n\n```go\n\u002F\u002F ShowAccount godoc\n\u002F\u002F @Summary      Get account by ID\n\u002F\u002F @Description  Returns account details for the given ID.\n\u002F\u002F @Tags         accounts\n\u002F\u002F @Accept       json\n\u002F\u002F @Produce      json\n\u002F\u002F @Param        id      path  int  true  \"Account ID\"\n\u002F\u002F @Param        filter  query string false \"Optional search filter\"\n\u002F\u002F @Success      200  {object}  model.Account\n\u002F\u002F @Success      204  \"No content\"\n\u002F\u002F @Failure      400  {object}  api.ErrorResponse\n\u002F\u002F @Failure      404  {object}  api.ErrorResponse\n\u002F\u002F @Router       \u002Faccounts\u002F{id} [get]\n\u002F\u002F @Security     Bearer\nfunc ShowAccount(c *gin.Context) {}\n```\n\n**@Param** format: `@Param \u003Cname> \u003Cin> \u003Ctype> \u003Crequired> \"\u003Cdescription>\" [attributes]`\n\n| `\u003Cin>`     | Usage                                |\n| ---------- | ------------------------------------ |\n| `path`     | URL path segment (`\u002Fusers\u002F{id}`)     |\n| `query`    | URL query string (`?filter=x`)       |\n| `body`     | Request body — type must be a struct |\n| `header`   | HTTP header                          |\n| `formData` | Multipart\u002Fform field                 |\n\nOptional attributes on `@Param`: `default(v)`, `minimum(n)`, `maximum(n)`, `minLength(n)`, `maxLength(n)`, `Enums(a,b,c)`, `example(v)`, `collectionFormat(multi)`.\n\n**@Success\u002F@Failure** format: `@Success \u003Ccode> {\u003Ckind>} \u003Ctype> \"\u003Cdescription>\"`\n\n| `\u003Ckind>`             | When             |\n| -------------------- | ---------------- |\n| `{object}`           | Single struct    |\n| `{array}`            | Slice of structs |\n| `string` \u002F `integer` | Primitive        |\n\n**Generics** (swag v2): `@Success 200 {object} api.Response[model.User]`\n\n**Nested composition**: `@Success 200 {object} api.Response{data=model.User}`\n\n## Security Definitions\n\nDefine once at the API level (in main.go), apply per endpoint with `@Security`.\n\n```go\n\u002F\u002F Bearer \u002F JWT\n\u002F\u002F @securityDefinitions.apikey Bearer\n\u002F\u002F @in header\n\u002F\u002F @name Authorization\n\n\u002F\u002F API key in header\n\u002F\u002F @securityDefinitions.apikey ApiKeyAuth\n\u002F\u002F @in header\n\u002F\u002F @name X-API-Key\n\n\u002F\u002F Basic auth\n\u002F\u002F @securityDefinitions.basic BasicAuth\n\n\u002F\u002F OAuth2 authorization code\n\u002F\u002F @securityDefinitions.oauth2.authorizationCode OAuth2\n\u002F\u002F @authorizationUrl https:\u002F\u002Fexample.com\u002Foauth\u002Fauthorize\n\u002F\u002F @tokenUrl https:\u002F\u002Fexample.com\u002Foauth\u002Ftoken\n\u002F\u002F @scope.read Read access\n\u002F\u002F @scope.write Write access\n```\n\nApply to an endpoint:\n\n```go\n\u002F\u002F @Security Bearer\n\u002F\u002F @Security OAuth2[read, write]\n\u002F\u002F @Security BasicAuth && ApiKeyAuth   \u002F\u002F AND — both required\n```\n\n## Struct Tags\n\nEnrich models without changing their Go type:\n\n```go\ntype CreateUserRequest struct {\n    Name   string `json:\"name\" example:\"Jane Doe\" minLength:\"2\" maxLength:\"100\"`\n    Role   string `json:\"role\" enums:\"admin,user,guest\" example:\"user\"`\n    Age    int    `json:\"age\" minimum:\"18\" maximum:\"120\"`\n    Avatar []byte `json:\"avatar\" swaggertype:\"string\" format:\"base64\"`\n    Secret string `json:\"-\" swaggerignore:\"true\"`  \u002F\u002F excluded from docs\n}\n```\n\n| Tag | Purpose |\n| --- | --- |\n| `example` | Example value shown in Swagger UI |\n| `enums` | Comma-separated allowed values |\n| `swaggertype` | Override detected type (e.g., `\"primitive,integer\"` for `time.Time`) |\n| `swaggerignore:\"true\"` | Exclude field from the generated schema |\n| `extensions` | Add OpenAPI extensions: `extensions:\"x-nullable,x-deprecated=true\"` |\n\n## Common Mistakes\n\n| Mistake | Why it breaks | Fix |\n| --- | --- | --- |\n| Missing `_ \"yourmodule\u002Fdocs\"` import | Schema not registered; UI loads empty | Add blank import in main.go or server init |\n| Stale `docs\u002F` after code changes | Docs diverge from implementation; consumers get wrong schema | Re-run `swag init` after every annotation change |\n| `@Param body` with primitive type | swag cannot derive schema from `string`; generation fails | Always use a named struct for body params |\n| No `@Security` on protected routes | Swagger UI shows no lock icon; testers send unauthenticated requests | Apply `@Security` to every authenticated endpoint |\n| General info annotations in the wrong file | swag silently skips them; spec has no title\u002Fhost | Use `-g \u003Cfile>` flag or move annotations to `main.go` |\n| Using `{object}` with a map type | swag cannot generate a schema for `map[string]any` without help | Use a named struct or annotate with `swaggertype` |\n| Multi-word `@Tags` without quotes | Tags split on spaces, producing malformed grouping | Quote tags with spaces: `@Tags \"user accounts\"` |\n\n## Cross-References\n\n- → See `samber\u002Fcc-skills-golang@golang-security` for securing the Swagger UI endpoint in production (disable or gate with auth middleware).\n- → See `samber\u002Fcc-skills-golang@golang-grpc` for gRPC — use grpc-gateway with its own OpenAPI generator instead of swag.\n\nThis skill is not exhaustive — refer to the swaggo\u002Fswag documentation and code examples for up-to-date API signatures and usage patterns:\n\n- For Go package docs, symbols, versions, importers, and known vulnerabilities, → See `samber\u002Fcc-skills-golang@golang-pkg-go-dev` skill (`godig`), preferred over Context7 for Go package facts.\n- To navigate this library's usage in your own code (definitions, call sites, diagnostics), → See `samber\u002Fcc-skills-golang@golang-gopls` skill (`gopls`).\n- Context7 remains a fallback for docs not indexed on pkg.go.dev.\n\nIf you encounter a bug or unexpected behavior in swag, open an issue at \u003Chttps:\u002F\u002Fgithub.com\u002Fswaggo\u002Fswag\u002Fissues>.\n",{"name":5,"paths":24,"license":15,"metadata":26,"description":7,"allowed-tools":41,"compatibility":42,"user-invocable":43},[25],"**\u002F*.go",{"author":27,"version":28,"openclaw":29},"samber","1.1.2",{"emoji":30,"install":31,"homepage":37,"requires":38,"skill-library-version":40},"📋",[32],{"bins":33,"kind":35,"package":36},[34],"swag","go","github.com\u002Fswaggo\u002Fswag\u002Fcmd\u002Fswag@latest","https:\u002F\u002Fgithub.com\u002Fsamber\u002Fcc-skills-golang",{"bins":39},[35,34],"2.0.0-rc5","Read Edit Write Glob Grep Bash(go:*) Bash(golangci-lint:*) Bash(git:*) Agent WebFetch mcp__context7__resolve-library-id mcp__context7__query-docs Bash(swag:*) AskUserQuestion Bash(godig:*) Bash(gopls:*) LSP mcp__gopls__*","Designed for Claude Code, Codex or similar harness. Requires go and swag CLI.",true,"master","fd76f882a04e445e899d5cfb2732f2105ea054ee","skills\u002Fmarketplace\u002Fgolang-swagger",0,"https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS","https:\u002F\u002Fbg-szy.github.io\u002FTOP-SKILLS\u002F","https:\u002F\u002Fgithub.com\u002Fbg-szy","https:\u002F\u002Fwww.ecust.edu.cn\u002F","a student of East China University of Science and Technology","2026-11-15 03:38:02",{"source":8,"skillName":5,"commands":55,"prompt":65,"zipAvailable":43},[56,59,62],{"tool":57,"command":58},"npx","npx skills add bg-szy\u002FTOP-SKILLS --skill golang-swagger",{"tool":60,"command":61},"bunx","bunx skills add bg-szy\u002FTOP-SKILLS --skill golang-swagger",{"tool":63,"command":64},"pnpm","pnpm dlx skills add bg-szy\u002FTOP-SKILLS --skill golang-swagger","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketplace\u002Fgolang-swagger\u002FSKILL.md",[67],{"path":68,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":71,"sourceHtmlUrl":72},"skill-report.json","REFERENCE","参考文档",81278,"https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketplace\u002Fgolang-swagger\u002Fskill-report.json",[74,82,89,96,103,110],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":81},"01M7DXW9N826PKXK174PVW3038","serpmaven","Scrape Google search results (SERP) to JSON with SERP Maven (serpmaven) - a real Chrome browser on a residential proxy with sticky sessions. Run it as a CLI, a Python library, a local HTTP search API (`serve`), an MCP server or a Docker image; set the proxy login, workers, pages and cost tracking. Use when the user wants Google results, rank tracking, a self-hosted SERP API, or live Google search for an AI agent.","https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketplace\u002Fserpmaven\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":81},"01M7DXVHSTWDV65475QEQ915M7","revnu-landing-page-audit","Find out why a landing page isn't turning visitors into signups, demos or sales. Audits one page against what the ad, post or search that sends people there promised, then checks the first screen, proof, call to action, friction and mobile. Returns at most 7 prioritized fixes, plus what is fine and what could not be checked; rewrites specific lines and fixes the page in the repo when asked. Never promises a conversion lift. Works without a Revnu account. Use when the user says or asks: \"audit my landing page\", \"why isn't this page converting\", \"review my homepage\", \"my ads get clicks but no signups\", \"people bounce from the pricing page\", \"CRO review\", \"improve conversion rate\", \"is my hero section clear\", \"roast my landing page\", \"rewrite my headline\", \"what's wrong with this page\", \"landing page feedback\", \"make the signup page convert better\". Not for SEO or AI-search audits, page speed engineering on its own, or building a new page from scratch.","https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketplace\u002Frevnu-landing-page-audit\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":81},"01M7DXV8X2D7B3VTD4HHYYHTGR","revnu-growth-context","Write down once who buys, what they're stuck on, what it costs, what proof you have and what you've already tried, so every growth task starts from facts instead of a questionnaire. Creates or updates .agents\u002Frevnu-growth.md from the repo, the live site and the user, and imports an existing product-marketing.md. Use when the user says \"set up our marketing context\", \"who is our ideal customer\", \"write our ICP\", \"describe the product for marketing\", \"positioning doc\", \"what's our brand voice\", \"remember this about our customers\", \"log what we tried\", \"what have we learned from marketing\", \"we changed pricing, update the context\", \"update our growth notes\", \"summarize the business for the agent\", \"import my product-marketing.md\", \"start a growth doc\", or before a first marketing, SEO, outreach or launch task when no context file exists. Works without a Revnu account.","https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketplace\u002Frevnu-growth-context\u002FSKILL.md",[],[],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":81},"01M7DXV0DGJ1G0A60PAHC6J3C5","revnu-get-listed","Get onto the third-party pages AI answers and search cite when buyers ask for the best tool in your category: \"best X\" roundups, directories, review sites, GitHub awesome lists, community threads and comparison pages. Finds which ones are cited, ranks them by fit and effort, and drafts each submission, PR or pitch by the target's own rules. Use when the user says \"get us listed\", \"which directories should we submit to\", \"how do we get into best-of lists\", \"why does ChatGPT recommend competitors and not us\", \"get mentioned in AI answers\", \"submit to awesome lists\", \"get on G2\", \"where are our competitors listed\", \"pitch listicle authors\", \"find backlink opportunities\", \"launch directories\", \"get into roundups\", \"Product Hunt alternatives\", \"where should we be listed\", \"get cited by Perplexity\". Never submits, pays or posts without a yes. Works without a Revnu account.","https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketplace\u002Frevnu-get-listed\u002FSKILL.md",[],[],{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":81},"01M7DXTSPMGT9D6DSS0HP9BSTA","revnu-ai-readiness-audit","Audit whether your website gives ChatGPT, Perplexity, Claude, Gemini and Google's AI Overviews something worth quoting, and fix the pages that don't. Use when the user says or asks \"is my site ready for AI search\", \"audit my site for AI answers\", \"AEO audit\", \"GEO audit\", \"why doesn't ChatGPT quote our pricing\", \"make our pages citable by AI\", \"do I need llms.txt\", \"does schema help with ChatGPT\", \"check our structured data\", \"is our content visible without JavaScript\", \"AI SEO audit\", \"optimize our homepage for AI answers\", \"LLM SEO check\", \"why does AI get our product wrong\", \"fix our site for AI Overviews\". Checks fetchability and indexability, answers in the raw HTML, entity facts, schema (including JS-injected markup), headings, dates and llms.txt, then gives at most 10 prioritised fixes and edits the repo when asked. Works without a Revnu account.","https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketplace\u002Frevnu-ai-readiness-audit\u002FSKILL.md",[],[],{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":116,"publishedAt":81},"01M7DXSZHCVTRS620GC3S97JZV","proxy-troubleshooting","Diagnose residential proxy failures, with NodeMaven's gateway as the reference - 407 with correct credentials, 406, 410, 500, a connection that hangs, ERR_TUNNEL_CONNECTION_FAILED in a browser, Playwright or Puppeteer ignoring proxy credentials, a sticky session that changes IP, geo-targeting that is silently ignored, passwords with special characters, and unexpected traffic from headless Chrome. Use when a proxy connection fails, returns the wrong location, or costs more traffic than expected.","https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketplace\u002Fproxy-troubleshooting\u002FSKILL.md",[],[]]