[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6F1YM5B979ST4RFBJP0TSSH":3,"skill-same:01M6F1YM5B979ST4RFBJP0TSSH":113},{"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":31,"publishedAt":52,"linkOnly":53,"markdownContent":54,"markdownBody":55,"frontMatter":56,"refName":70,"commitSha":71,"skillDirectory":72,"forksCount":73,"repositoryHtmlUrl":74,"repositoryHomepageUrl":6,"ownerHtmlUrl":75,"ownerBlogUrl":6,"ownerDescription":76,"updatedAt":77,"install":78,"resources":90},"01M6F1YM5B979ST4RFBJP0TSSH","golang-modernize",null,"Continuously modernize Golang code to use the latest language features, standard library improvements, and idiomatic patterns. Use this skill whenever writing, reviewing, or refactoring Go code to ensure it leverages modern Go idioms. Also use when the user asks about Go upgrades, migration, modernization, deprecation, or when modernize linter reports issues. Also covers tooling modernization: linters, SAST, AI-powered code review in CI, and modern development practices. Trigger this skill proactively when you notice old-style Go patterns that have modern replacements.","luokai0\u002Fai-agent-skills-by-luo-kai","luokai0","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F266954973?v=4","01M6E16VNT42JB8B3X3254QWJ7","luo kai","01M6E16VTFVP6S5XJF1V1MPV90",14,"MIT","https:\u002F\u002Fgithub.com\u002Fluokai0\u002Fai-agent-skills-by-luo-kai\u002Fblob\u002Fmain\u002Fai-agent-skills\u002F22-clawhub-skills\u002Fgolang-modernize\u002FSKILL.md",[18,23,26],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000007","代码审查","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":27,"categoryName":28,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51],"modernize","golang modernize","golang","refactoring","cc","reports","edit","write","read","linter","projects","code review","Bash","ci","issues","code","modernization","ai coding agents","review","writing","2026-11-10 10:12:30",false,"---\nname: golang-modernize\ndescription: \"Continuously modernize Golang code to use the latest language features, standard library improvements, and idiomatic patterns. Use this skill whenever writing, reviewing, or refactoring Go code to ensure it leverages modern Go idioms. Also use when the user asks about Go upgrades, migration, modernization, deprecation, or when modernize linter reports issues. Also covers tooling modernization: linters, SAST, AI-powered code review in CI, and modern development practices. Trigger this skill proactively when you notice old-style Go patterns that have modern replacements.\"\nuser-invocable: true\nlicense: MIT\ncompatibility: Designed for Claude Code or similar AI coding agents, and for projects using Golang.\nmetadata:\n  author: samber\n  version: \"1.1.4\"\n  openclaw:\n    emoji: \"?\"\n    homepage: https:\u002F\u002Fgithub.com\u002Fsamber\u002Fcc-skills-golang\n    requires:\n      bins:\n        - go\n    install: []\nallowed-tools: Read Edit Write Glob Grep Bash(go:*) Bash(golangci-lint:*) Bash(git:*) Agent WebFetch WebSearch AskUserQuestion\n---\n\n\u003C!-- markdownlint-disable ol-prefix -->\n\n**Persona:** You are a Go modernization engineer. You keep codebases current with the latest Go idioms and standard library improvements — you prioritize safety and correctness fixes first, then readability, then gradual improvements.\n\n**Modes:**\n\n- **Inline mode** (developer is actively coding): suggest only modernizations relevant to the current file or feature; mention other opportunities you noticed but do not touch unrelated files.\n- **Full-scan mode** (explicit `\u002Fgolang-modernize` invocation or CI): use up to 5 parallel sub-agents — Agent 1 scans deprecated packages and API replacements, Agent 2 scans language feature opportunities (range-over-int, min\u002Fmax, any, iterators), Agent 3 scans standard library upgrades (slices, maps, cmp, slog), Agent 4 scans testing patterns (t.Context, b.Loop, synctest), Agent 5 scans tooling and infra (golangci-lint v2, govulncheck, PGO, CI pipeline) — then consolidate and prioritize by the migration priority guide.\n\n# Go Code Modernization Guide\n\nThis skill helps you continuously modernize Go codebases by replacing outdated patterns with their modern equivalents.\n\n**Scope**: This skill covers the last 3 years of Go modernization (Go 1.21 through Go 1.26, released 2023-2026). While this skill can be used for projects targeting Go 1.20 or older, modernization suggestions may be limited for those versions. For best results, consider upgrading the Go version first. Some older modernizations (e.g., `any` instead of `interface{}`, `errors.Is`\u002F`errors.As`, `strings.Cut`) are included because they are still commonly missed, but many pre-1.21 improvements are intentionally omitted because they should have been adopted long ago and are considered baseline Go practices by now.\n\nYou MUST NEVER conduct large refactoring if the developer is working on a different task. But TRY TO CONVINCE your human it would improve the code quality.\n\n## Workflow\n\nWhen invoked:\n\n1. **Check the project's `go.mod` or `go.work`** to determine the current Go version (`go` directive)\n2. **Check the latest Go version** using the Go Version Changelogs table below and suggest upgrading if the project's `go.mod` is behind\n3. **Read `.modernize`** in the project root — this file contains previously ignored suggestions; do NOT re-suggest anything listed there\n4. **Scan the codebase** for modernization opportunities based on the target Go version\n5. **Run `golangci-lint`** with the `modernize` linter if available\n6. **Suggest improvements contextually**:\n   - If the developer is actively coding, **only suggest improvements related to the code they are currently working on**. Do not refactor unrelated files. Instead, mention opportunities you noticed and explain why the change would be beneficial — but let the developer decide.\n   - If invoked explicitly via `\u002Fgolang-modernize` or in CI, scan and suggest across the entire codebase.\n7. **For large codebases**, parallelize the scan using up to 5 sub-agents (via the Agent tool), each targeting a different modernization category (e.g. deprecated packages, language features, standard library upgrades, testing patterns, tooling and infra)\n8. **Before suggesting a dependency update**, run `go mod tidy` and the test suite to verify compatibility. Ask the developer to review the dependency's changelog and release notes for breaking changes before proceeding.\n9. **If the developer explicitly ignores a suggestion**, write a short memo to `.modernize` in the project root so it is not suggested again. Format: one line per ignored suggestion, with a short description.\n\n### `.modernize` file format\n\n```\n# Ignored modernization suggestions\n# Format: \u003Cdate> \u003Ccategory> \u003Cdescription>\n2026-01-15 slog-migration Team decided to keep zap for now\n2026-02-01 math-rand-v2 Legacy module requires math\u002Frand compatibility\n```\n\n## Go Version Changelogs\n\nReference the relevant changelog when suggesting a modernization:\n\n| Version | Release       | Changelog                   |\n| ------- | ------------- | --------------------------- |\n| Go 1.21 | August 2023   | \u003Chttps:\u002F\u002Fgo.dev\u002Fdoc\u002Fgo1.21> |\n| Go 1.22 | February 2024 | \u003Chttps:\u002F\u002Fgo.dev\u002Fdoc\u002Fgo1.22> |\n| Go 1.23 | August 2024   | \u003Chttps:\u002F\u002Fgo.dev\u002Fdoc\u002Fgo1.23> |\n| Go 1.24 | February 2025 | \u003Chttps:\u002F\u002Fgo.dev\u002Fdoc\u002Fgo1.24> |\n| Go 1.25 | August 2025   | \u003Chttps:\u002F\u002Fgo.dev\u002Fdoc\u002Fgo1.25> |\n| Go 1.26 | February 2026 | \u003Chttps:\u002F\u002Fgo.dev\u002Fdoc\u002Fgo1.26> |\n\nFor versions newer than Go 1.26, consult the official Go release notes.\n\nWhen the project's `go.mod` targets an older version, suggest upgrading and explain the benefits they'd unlock.\n\n## Using the modernize linter\n\nThe `modernize` linter (available since **golangci-lint v2.6.0**) automatically detects code that can be rewritten using newer Go features. It originates from `golang.org\u002Fx\u002Ftools\u002Fgo\u002Fanalysis\u002Fpasses\u002Fmodernize` and is also used by `gopls` and Go 1.26's rewritten `go fix` command. See the `samber\u002Fcc-skills-golang@golang-lint` skill for configuration.\n\n## Version-specific modernizations\n\nFor detailed before\u002Fafter examples for each Go version (1.21–1.26) and general modernizations, see [Go version modernizations](.\u002Freferences\u002Fversions.md).\n\n## Tooling modernization\n\nFor CI tooling, govulncheck, PGO, golangci-lint v2, and AI-powered modernization pipelines, see [Tooling modernization](.\u002Freferences\u002Ftooling.md).\n\n## Deprecated Packages Migration\n\n| Deprecated | Replacement | Since |\n| --- | --- | --- |\n| `math\u002Frand` | `math\u002Frand\u002Fv2` | Go 1.22 |\n| `crypto\u002Felliptic` (most functions) | `crypto\u002Fecdh` | Go 1.21 |\n| `reflect.SliceHeader`, `StringHeader` | `unsafe.Slice`, `unsafe.String` | Go 1.21 |\n| `reflect.PtrTo` | `reflect.PointerTo` | Go 1.22 |\n| `runtime.GOROOT()` | `go env GOROOT` | Go 1.24 |\n| `runtime.SetFinalizer` | `runtime.AddCleanup` | Go 1.24 |\n| `crypto\u002Fcipher.NewOFB`, `NewCFB*` | AEAD modes or `NewCTR` | Go 1.24 |\n| `golang.org\u002Fx\u002Fcrypto\u002Fsha3` | `crypto\u002Fsha3` | Go 1.24 |\n| `golang.org\u002Fx\u002Fcrypto\u002Fhkdf` | `crypto\u002Fhkdf` | Go 1.24 |\n| `golang.org\u002Fx\u002Fcrypto\u002Fpbkdf2` | `crypto\u002Fpbkdf2` | Go 1.24 |\n| `testing\u002Fsynctest.Run` | `testing\u002Fsynctest.Test` | Go 1.25 |\n| `crypto.EncryptPKCS1v15` | OAEP encryption | Go 1.26 |\n| `net\u002Fhttp\u002Fhttputil.ReverseProxy.Director` | `ReverseProxy.Rewrite` | Go 1.26 |\n\n## Migration Priority Guide\n\nWhen modernizing a codebase, prioritize changes by impact:\n\n### High priority (safety and correctness)\n\n1. Remove loop variable shadow copies _(Go 1.22+)_ — prevents subtle bugs\n2. Replace `math\u002Frand` with `math\u002Frand\u002Fv2` _(Go 1.22+)_ — remove `rand.Seed` calls\n3. Use `os.Root` for user-supplied file paths _(Go 1.24+)_ — prevents path traversal\n4. Run `govulncheck` _(Go 1.22+)_ — catch known vulnerabilities\n5. Use `errors.Is`\u002F`errors.As` instead of direct comparison _(Go 1.13+)_\n6. Migrate deprecated crypto packages _(Go 1.24+)_ — security critical\n\n### Medium priority (readability and maintainability)\n\n7. Replace `interface{}` with `any` _(Go 1.18+)_\n8. Use `min`\u002F`max` builtins _(Go 1.21+)_\n9. Use `range` over int _(Go 1.22+)_\n10. Use `slices` and `maps` packages _(Go 1.21+)_\n11. Use `cmp.Or` for default values _(Go 1.22+)_\n12. Use `sync.OnceValue`\u002F`sync.OnceFunc` _(Go 1.21+)_\n13. Use `sync.WaitGroup.Go` _(Go 1.25+)_\n14. Use `t.Context()` in tests _(Go 1.24+)_\n15. Use `b.Loop()` in benchmarks _(Go 1.24+)_\n\n### Lower priority (gradual improvement)\n\n16. Migrate to `slog` from third-party loggers _(Go 1.21+)_\n17. Adopt iterators where they simplify code _(Go 1.23+)_\n18. Replace `sort.Slice` with `slices.SortFunc` _(Go 1.21+)_\n19. Use `strings.SplitSeq` and iterator variants _(Go 1.24+)_\n20. Move tool deps to `go.mod` tool directives _(Go 1.24+)_\n21. Enable PGO for production builds _(Go 1.21+)_\n22. Upgrade to golangci-lint v2 with modernize linter _(golangci-lint v2.6.0+)_\n23. Add `govulncheck` to CI pipeline\n24. Set up monthly modernization CI pipeline\n25. Evaluate `encoding\u002Fjson\u002Fv2` for new code _(Go 1.25+, experimental)_\n26. Set up AI-driven code review in CI — loads these skills to guide review per area; see `samber\u002Fcc-skills-golang@golang-continuous-integration`\n\n## Related Skills\n\nSee `samber\u002Fcc-skills-golang@golang-concurrency`, `samber\u002Fcc-skills-golang@golang-testing`, `samber\u002Fcc-skills-golang@golang-observability`, `samber\u002Fcc-skills-golang@golang-error-handling`, `samber\u002Fcc-skills-golang@golang-lint`, `samber\u002Fcc-skills-golang@golang-continuous-integration` skills.\n","\u003C!-- markdownlint-disable ol-prefix -->\n\n**Persona:** You are a Go modernization engineer. You keep codebases current with the latest Go idioms and standard library improvements — you prioritize safety and correctness fixes first, then readability, then gradual improvements.\n\n**Modes:**\n\n- **Inline mode** (developer is actively coding): suggest only modernizations relevant to the current file or feature; mention other opportunities you noticed but do not touch unrelated files.\n- **Full-scan mode** (explicit `\u002Fgolang-modernize` invocation or CI): use up to 5 parallel sub-agents — Agent 1 scans deprecated packages and API replacements, Agent 2 scans language feature opportunities (range-over-int, min\u002Fmax, any, iterators), Agent 3 scans standard library upgrades (slices, maps, cmp, slog), Agent 4 scans testing patterns (t.Context, b.Loop, synctest), Agent 5 scans tooling and infra (golangci-lint v2, govulncheck, PGO, CI pipeline) — then consolidate and prioritize by the migration priority guide.\n\n# Go Code Modernization Guide\n\nThis skill helps you continuously modernize Go codebases by replacing outdated patterns with their modern equivalents.\n\n**Scope**: This skill covers the last 3 years of Go modernization (Go 1.21 through Go 1.26, released 2023-2026). While this skill can be used for projects targeting Go 1.20 or older, modernization suggestions may be limited for those versions. For best results, consider upgrading the Go version first. Some older modernizations (e.g., `any` instead of `interface{}`, `errors.Is`\u002F`errors.As`, `strings.Cut`) are included because they are still commonly missed, but many pre-1.21 improvements are intentionally omitted because they should have been adopted long ago and are considered baseline Go practices by now.\n\nYou MUST NEVER conduct large refactoring if the developer is working on a different task. But TRY TO CONVINCE your human it would improve the code quality.\n\n## Workflow\n\nWhen invoked:\n\n1. **Check the project's `go.mod` or `go.work`** to determine the current Go version (`go` directive)\n2. **Check the latest Go version** using the Go Version Changelogs table below and suggest upgrading if the project's `go.mod` is behind\n3. **Read `.modernize`** in the project root — this file contains previously ignored suggestions; do NOT re-suggest anything listed there\n4. **Scan the codebase** for modernization opportunities based on the target Go version\n5. **Run `golangci-lint`** with the `modernize` linter if available\n6. **Suggest improvements contextually**:\n   - If the developer is actively coding, **only suggest improvements related to the code they are currently working on**. Do not refactor unrelated files. Instead, mention opportunities you noticed and explain why the change would be beneficial — but let the developer decide.\n   - If invoked explicitly via `\u002Fgolang-modernize` or in CI, scan and suggest across the entire codebase.\n7. **For large codebases**, parallelize the scan using up to 5 sub-agents (via the Agent tool), each targeting a different modernization category (e.g. deprecated packages, language features, standard library upgrades, testing patterns, tooling and infra)\n8. **Before suggesting a dependency update**, run `go mod tidy` and the test suite to verify compatibility. Ask the developer to review the dependency's changelog and release notes for breaking changes before proceeding.\n9. **If the developer explicitly ignores a suggestion**, write a short memo to `.modernize` in the project root so it is not suggested again. Format: one line per ignored suggestion, with a short description.\n\n### `.modernize` file format\n\n```\n# Ignored modernization suggestions\n# Format: \u003Cdate> \u003Ccategory> \u003Cdescription>\n2026-01-15 slog-migration Team decided to keep zap for now\n2026-02-01 math-rand-v2 Legacy module requires math\u002Frand compatibility\n```\n\n## Go Version Changelogs\n\nReference the relevant changelog when suggesting a modernization:\n\n| Version | Release       | Changelog                   |\n| ------- | ------------- | --------------------------- |\n| Go 1.21 | August 2023   | \u003Chttps:\u002F\u002Fgo.dev\u002Fdoc\u002Fgo1.21> |\n| Go 1.22 | February 2024 | \u003Chttps:\u002F\u002Fgo.dev\u002Fdoc\u002Fgo1.22> |\n| Go 1.23 | August 2024   | \u003Chttps:\u002F\u002Fgo.dev\u002Fdoc\u002Fgo1.23> |\n| Go 1.24 | February 2025 | \u003Chttps:\u002F\u002Fgo.dev\u002Fdoc\u002Fgo1.24> |\n| Go 1.25 | August 2025   | \u003Chttps:\u002F\u002Fgo.dev\u002Fdoc\u002Fgo1.25> |\n| Go 1.26 | February 2026 | \u003Chttps:\u002F\u002Fgo.dev\u002Fdoc\u002Fgo1.26> |\n\nFor versions newer than Go 1.26, consult the official Go release notes.\n\nWhen the project's `go.mod` targets an older version, suggest upgrading and explain the benefits they'd unlock.\n\n## Using the modernize linter\n\nThe `modernize` linter (available since **golangci-lint v2.6.0**) automatically detects code that can be rewritten using newer Go features. It originates from `golang.org\u002Fx\u002Ftools\u002Fgo\u002Fanalysis\u002Fpasses\u002Fmodernize` and is also used by `gopls` and Go 1.26's rewritten `go fix` command. See the `samber\u002Fcc-skills-golang@golang-lint` skill for configuration.\n\n## Version-specific modernizations\n\nFor detailed before\u002Fafter examples for each Go version (1.21–1.26) and general modernizations, see [Go version modernizations](.\u002Freferences\u002Fversions.md).\n\n## Tooling modernization\n\nFor CI tooling, govulncheck, PGO, golangci-lint v2, and AI-powered modernization pipelines, see [Tooling modernization](.\u002Freferences\u002Ftooling.md).\n\n## Deprecated Packages Migration\n\n| Deprecated | Replacement | Since |\n| --- | --- | --- |\n| `math\u002Frand` | `math\u002Frand\u002Fv2` | Go 1.22 |\n| `crypto\u002Felliptic` (most functions) | `crypto\u002Fecdh` | Go 1.21 |\n| `reflect.SliceHeader`, `StringHeader` | `unsafe.Slice`, `unsafe.String` | Go 1.21 |\n| `reflect.PtrTo` | `reflect.PointerTo` | Go 1.22 |\n| `runtime.GOROOT()` | `go env GOROOT` | Go 1.24 |\n| `runtime.SetFinalizer` | `runtime.AddCleanup` | Go 1.24 |\n| `crypto\u002Fcipher.NewOFB`, `NewCFB*` | AEAD modes or `NewCTR` | Go 1.24 |\n| `golang.org\u002Fx\u002Fcrypto\u002Fsha3` | `crypto\u002Fsha3` | Go 1.24 |\n| `golang.org\u002Fx\u002Fcrypto\u002Fhkdf` | `crypto\u002Fhkdf` | Go 1.24 |\n| `golang.org\u002Fx\u002Fcrypto\u002Fpbkdf2` | `crypto\u002Fpbkdf2` | Go 1.24 |\n| `testing\u002Fsynctest.Run` | `testing\u002Fsynctest.Test` | Go 1.25 |\n| `crypto.EncryptPKCS1v15` | OAEP encryption | Go 1.26 |\n| `net\u002Fhttp\u002Fhttputil.ReverseProxy.Director` | `ReverseProxy.Rewrite` | Go 1.26 |\n\n## Migration Priority Guide\n\nWhen modernizing a codebase, prioritize changes by impact:\n\n### High priority (safety and correctness)\n\n1. Remove loop variable shadow copies _(Go 1.22+)_ — prevents subtle bugs\n2. Replace `math\u002Frand` with `math\u002Frand\u002Fv2` _(Go 1.22+)_ — remove `rand.Seed` calls\n3. Use `os.Root` for user-supplied file paths _(Go 1.24+)_ — prevents path traversal\n4. Run `govulncheck` _(Go 1.22+)_ — catch known vulnerabilities\n5. Use `errors.Is`\u002F`errors.As` instead of direct comparison _(Go 1.13+)_\n6. Migrate deprecated crypto packages _(Go 1.24+)_ — security critical\n\n### Medium priority (readability and maintainability)\n\n7. Replace `interface{}` with `any` _(Go 1.18+)_\n8. Use `min`\u002F`max` builtins _(Go 1.21+)_\n9. Use `range` over int _(Go 1.22+)_\n10. Use `slices` and `maps` packages _(Go 1.21+)_\n11. Use `cmp.Or` for default values _(Go 1.22+)_\n12. Use `sync.OnceValue`\u002F`sync.OnceFunc` _(Go 1.21+)_\n13. Use `sync.WaitGroup.Go` _(Go 1.25+)_\n14. Use `t.Context()` in tests _(Go 1.24+)_\n15. Use `b.Loop()` in benchmarks _(Go 1.24+)_\n\n### Lower priority (gradual improvement)\n\n16. Migrate to `slog` from third-party loggers _(Go 1.21+)_\n17. Adopt iterators where they simplify code _(Go 1.23+)_\n18. Replace `sort.Slice` with `slices.SortFunc` _(Go 1.21+)_\n19. Use `strings.SplitSeq` and iterator variants _(Go 1.24+)_\n20. Move tool deps to `go.mod` tool directives _(Go 1.24+)_\n21. Enable PGO for production builds _(Go 1.21+)_\n22. Upgrade to golangci-lint v2 with modernize linter _(golangci-lint v2.6.0+)_\n23. Add `govulncheck` to CI pipeline\n24. Set up monthly modernization CI pipeline\n25. Evaluate `encoding\u002Fjson\u002Fv2` for new code _(Go 1.25+, experimental)_\n26. Set up AI-driven code review in CI — loads these skills to guide review per area; see `samber\u002Fcc-skills-golang@golang-continuous-integration`\n\n## Related Skills\n\nSee `samber\u002Fcc-skills-golang@golang-concurrency`, `samber\u002Fcc-skills-golang@golang-testing`, `samber\u002Fcc-skills-golang@golang-observability`, `samber\u002Fcc-skills-golang@golang-error-handling`, `samber\u002Fcc-skills-golang@golang-lint`, `samber\u002Fcc-skills-golang@golang-continuous-integration` skills.\n",{"name":5,"license":15,"metadata":57,"description":7,"allowed-tools":67,"compatibility":68,"user-invocable":69},{"author":58,"version":59,"openclaw":60},"samber","1.1.4",{"emoji":61,"install":62,"homepage":63,"requires":64},"?",[],"https:\u002F\u002Fgithub.com\u002Fsamber\u002Fcc-skills-golang",{"bins":65},[66],"go","Read Edit Write Glob Grep Bash(go:*) Bash(golangci-lint:*) Bash(git:*) Agent WebFetch WebSearch AskUserQuestion","Designed for Claude Code or similar AI coding agents, and for projects using Golang.",true,"main","4d2fb89cdfb75f3f6fd3c6c5ec9ad90ea129eb3c","ai-agent-skills\u002F22-clawhub-skills\u002Fgolang-modernize",2,"https:\u002F\u002Fgithub.com\u002Fluokai0\u002Fai-agent-skills-by-luo-kai","https:\u002F\u002Fgithub.com\u002Fluokai0","a solo builder.","2026-05-06 04:29:04",{"source":8,"skillName":5,"commands":79,"prompt":89,"zipAvailable":69},[80,83,86],{"tool":81,"command":82},"npx","npx skills add luokai0\u002Fai-agent-skills-by-luo-kai --skill golang-modernize",{"tool":84,"command":85},"bunx","bunx skills add luokai0\u002Fai-agent-skills-by-luo-kai --skill golang-modernize",{"tool":87,"command":88},"pnpm","pnpm dlx skills add luokai0\u002Fai-agent-skills-by-luo-kai --skill golang-modernize","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fluokai0\u002Fai-agent-skills-by-luo-kai\u002Fblob\u002Fmain\u002Fai-agent-skills\u002F22-clawhub-skills\u002Fgolang-modernize\u002FSKILL.md",[91,97,101,105,109],{"path":92,"resourceType":93,"resourceTypeDesc":94,"sizeBytes":95,"sourceHtmlUrl":96},"_meta.json","REFERENCE","参考文档",135,"https:\u002F\u002Fgithub.com\u002Fluokai0\u002Fai-agent-skills-by-luo-kai\u002Fblob\u002Fmain\u002Fai-agent-skills\u002F22-clawhub-skills\u002Fgolang-modernize\u002F_meta.json",{"path":98,"resourceType":93,"resourceTypeDesc":94,"sizeBytes":99,"sourceHtmlUrl":100},".clawhub\u002Forigin.json",148,"https:\u002F\u002Fgithub.com\u002Fluokai0\u002Fai-agent-skills-by-luo-kai\u002Fblob\u002Fmain\u002Fai-agent-skills\u002F22-clawhub-skills\u002Fgolang-modernize\u002F.clawhub\u002Forigin.json",{"path":102,"resourceType":93,"resourceTypeDesc":94,"sizeBytes":103,"sourceHtmlUrl":104},"evals\u002Fevals.json",27827,"https:\u002F\u002Fgithub.com\u002Fluokai0\u002Fai-agent-skills-by-luo-kai\u002Fblob\u002Fmain\u002Fai-agent-skills\u002F22-clawhub-skills\u002Fgolang-modernize\u002Fevals\u002Fevals.json",{"path":106,"resourceType":93,"resourceTypeDesc":94,"sizeBytes":107,"sourceHtmlUrl":108},"references\u002Ftooling.md",2880,"https:\u002F\u002Fgithub.com\u002Fluokai0\u002Fai-agent-skills-by-luo-kai\u002Fblob\u002Fmain\u002Fai-agent-skills\u002F22-clawhub-skills\u002Fgolang-modernize\u002Freferences\u002Ftooling.md",{"path":110,"resourceType":93,"resourceTypeDesc":94,"sizeBytes":111,"sourceHtmlUrl":112},"references\u002Fversions.md",15391,"https:\u002F\u002Fgithub.com\u002Fluokai0\u002Fai-agent-skills-by-luo-kai\u002Fblob\u002Fmain\u002Fai-agent-skills\u002F22-clawhub-skills\u002Fgolang-modernize\u002Freferences\u002Fversions.md",[114,140,157,180,213,246],{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":120,"publishedAt":52},"01M6F2SKTE208174C7S7JJCZC7","write-contracts","Generates secure Aptos Move V2 smart contracts with Object model, Digital Asset integration, security patterns, and storage type guidance. Includes comprehensive storage decision framework for optimal data structure selection. Triggers on: 'write contract', 'create NFT collection', 'build marketplace', 'implement minting', 'generate Move module', 'create token contract', 'build DAO', 'implement staking'. Ask storage questions when: 'store', 'track', 'registry', 'mapping', 'list', 'collection'.","https:\u002F\u002Fgithub.com\u002Fluokai0\u002Fai-agent-skills-by-luo-kai\u002Fblob\u002Fmain\u002Fai-agent-skills\u002F22-clawhub-skills\u002Fwrite-contracts\u002FSKILL.md",[],[39,121,122,123,124,125,126,127,128,129,130,131,132,133,134,135,136,137,138,139],"contracts","write contracts","storage","secure","create","generate","collection","model","decision","ask","smart-contracts","selection","objects","structure","nft","token","aptos","critical","move",{"skillNo":141,"name":142,"nameZh":6,"description":143,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":144,"categories":145,"keywords":146,"publishedAt":52},"01M6F2RFXJ6T9MKW0A7N7GM45B","web-search","通用网络搜索技能，支持多引擎搜索（百度、必应、DuckDuckGo），无需API密钥即可获取实时信息","https:\u002F\u002Fgithub.com\u002Fluokai0\u002Fai-agent-skills-by-luo-kai\u002Fblob\u002Fmain\u002Fai-agent-skills\u002F22-clawhub-skills\u002Fweb-search-ex-skill\u002FSKILL.md",[],[147,148,149,150,151,152,153,154,155,156],"web","search","web search","搜索","baidu","bing","duckduckgo","百度","多引擎","internet",{"skillNo":158,"name":159,"nameZh":6,"description":160,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":161,"categories":162,"keywords":164,"publishedAt":52},"01M6F2K968G1FZEZFPW2E6B222","solo-build","Execute implementation plan tasks with TDD workflow, auto-commit, and phase gates. Use when user says \"build it\", \"start building\", \"execute plan\", \"implement tasks\", \"ship it\", or references a track ID. Do NOT use for planning (use \u002Fplan) or scaffolding (use \u002Fscaffold).","https:\u002F\u002Fgithub.com\u002Fluokai0\u002Fai-agent-skills-by-luo-kai\u002Fblob\u002Fmain\u002Fai-agent-skills\u002F22-clawhub-skills\u002Fsolo-build\u002FSKILL.md",[163],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[165,166,167,168,169,170,171,47,148,44,172,40,39,173,174,175,176,177,178,179],"build","solo","solo build","MCP","workflow","commit","tasks","plan","auto","references","context7","query","scaffolding","ship it","project",{"skillNo":181,"name":182,"nameZh":6,"description":183,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":184,"categories":185,"keywords":192,"publishedAt":52},"01M6F2GKN39SGHSPWYB3662YC8","react-email","Use when building HTML email templates with React components, adding a visual email editor to an application using the React Email visual editor, rendering emails to HTML, or sending emails with Resend. Covers welcome emails, password resets, notifications, order confirmations, newsletters, transactional emails, and the embeddable email editor component.","https:\u002F\u002Fgithub.com\u002Fluokai0\u002Fai-agent-skills-by-luo-kai\u002Fblob\u002Fmain\u002Fai-agent-skills\u002F22-clawhub-skills\u002Freact-email-skills\u002FSKILL.md",[186,189],{"categoryNo":187,"categoryName":188,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000005","邮件与沟通",{"categoryNo":190,"categoryName":191,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[193,194,195,196,197,198,199,200,201,202,203,204,205,206,207,208,209,210,211,212],"react","email","react email","github","editor","components","react components","component","welcome","https","notifications","password","node","use","html","resend","visual","emails","rendering","with",{"skillNo":214,"name":215,"nameZh":6,"description":216,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":217,"categories":218,"keywords":227,"publishedAt":52},"01M6F2FBVGVDFSG8SSFJGXA40C","APITester Agent-Driven API Testing","Test API endpoints and document responses. Define tests in plain English, run them, get formatted results. Agent-driven Postman alternative.","https:\u002F\u002Fgithub.com\u002Fluokai0\u002Fai-agent-skills-by-luo-kai\u002Fblob\u002Fmain\u002Fai-agent-skills\u002F22-clawhub-skills\u002Fopenclaw-api-tester\u002FSKILL.md",[219,222,225,226],{"categoryNo":220,"categoryName":221,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":223,"categoryName":224,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":27,"categoryName":28,"taxonomyType":29,"taxonomyTypeDesc":30},[228,229,230,231,232,233,234,235,236,237,238,239,240,241,242,243,244,245],"testing","api","api testing","driven","APITester Agent Driven API Testing","test","run","postman","results","plain english","tester","endpoints","document","get","define","tests","english","api-tester",{"skillNo":247,"name":248,"nameZh":6,"description":249,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":250,"categories":251,"keywords":252,"publishedAt":52},"01M6F273Y3NGAPVJZ608BC0G9G","hubspot-implementation-plan","Generate a phased implementation plan from a HubSpot audit report. Creates prioritized, sequenced cleanup processes with effort estimates, dependencies, and automation feasibility. Use after running \u002Fhubspot-audit.","https:\u002F\u002Fgithub.com\u002Fluokai0\u002Fai-agent-skills-by-luo-kai\u002Fblob\u002Fmain\u002Fai-agent-skills\u002F22-clawhub-skills\u002Fhubspot-implementation-plan\u002FSKILL.md",[],[172,253,254,255,256,257,258,126,259,260,261,262,263,206,264,265,212,266],"implementation","hubspot","hubspot implementation plan","automation","feasibility","cleanup","planning","report","audit","audit report","phased implementation","dependencies","processes","hubspot audit"]