[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6F1WWCQ2JGJWJC2YFHC9ZR2":3,"skill-same:01M6F1WWCQ2JGJWJC2YFHC9ZR2":146},{"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":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":61,"commitSha":62,"skillDirectory":63,"forksCount":64,"repositoryHtmlUrl":65,"repositoryHomepageUrl":6,"ownerHtmlUrl":66,"ownerBlogUrl":6,"ownerDescription":67,"updatedAt":68,"install":69,"resources":81},"01M6F1WWCQ2JGJWJC2YFHC9ZR2","golang-cli",null,"Golang CLI application development. Use when building, modifying, or reviewing a Go CLI tool — especially for command structure, flag handling, configuration layering, version embedding, exit codes, I\u002FO patterns, signal handling, shell completion, argument validation, and CLI unit testing. Also triggers when code uses cobra, viper, or urfave\u002Fcli.","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-cli\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"cli","golang","golang cli","cobra","testing","embedding","unit","structure","unit testing","cc","edit","write","read","command","projects","Bash","git","code","ai coding agents","go","2026-11-10 10:12:30",false,"---\nname: golang-cli\ndescription: \"Golang CLI application development. Use when building, modifying, or reviewing a Go CLI tool — especially for command structure, flag handling, configuration layering, version embedding, exit codes, I\u002FO patterns, signal handling, shell completion, argument validation, and CLI unit testing. Also triggers when code uses cobra, viper, or urfave\u002Fcli.\"\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.3\"\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 AskUserQuestion\n---\n\n**Persona:** You are a Go CLI engineer. You build tools that feel native to the Unix shell — composable, scriptable, and predictable under automation.\n\n**Modes:**\n\n- **Build** — creating a new CLI from scratch: follow the project structure, root command setup, flag binding, and version embedding sections sequentially.\n- **Extend** — adding subcommands, flags, or completions to an existing CLI: read the current command tree first, then apply changes consistent with the existing structure.\n- **Review** — auditing an existing CLI for correctness: check the Common Mistakes table, verify `SilenceUsage`\u002F`SilenceErrors`, flag-to-Viper binding, exit codes, and stdout\u002Fstderr discipline.\n\n# Go CLI Best Practices\n\nUse Cobra + Viper as the default stack for Go CLI applications. Cobra provides the command\u002Fsubcommand\u002Fflag structure and Viper handles configuration from files, environment variables, and flags with automatic layering. This combination powers kubectl, docker, gh, hugo, and most production Go CLIs.\n\nWhen using Cobra or Viper, refer to the library's official documentation and code examples for current API signatures.\n\nFor trivial single-purpose tools with no subcommands and few flags, stdlib `flag` is sufficient.\n\n## Quick Reference\n\n| Concern             | Package \u002F Tool                       |\n| ------------------- | ------------------------------------ |\n| Commands & flags    | `github.com\u002Fspf13\u002Fcobra`             |\n| Configuration       | `github.com\u002Fspf13\u002Fviper`             |\n| Flag parsing        | `github.com\u002Fspf13\u002Fpflag` (via Cobra) |\n| Colored output      | `github.com\u002Ffatih\u002Fcolor`             |\n| Table output        | `github.com\u002Folekukonko\u002Ftablewriter`  |\n| Interactive prompts | `github.com\u002Fcharmbracelet\u002Fbubbletea` |\n| Version injection   | `go build -ldflags`                  |\n| Distribution        | `goreleaser`                         |\n\n## Project Structure\n\nOrganize CLI commands in `cmd\u002Fmyapp\u002F` with one file per command. Keep `main.go` minimal — it only calls `Execute()`.\n\n```\nmyapp\u002F\n├── cmd\u002F\n│   └── myapp\u002F\n│       ├── main.go              # package main, only calls Execute()\n│       ├── root.go              # Root command + Viper init\n│       ├── serve.go             # \"serve\" subcommand\n│       ├── migrate.go           # \"migrate\" subcommand\n│       └── version.go           # \"version\" subcommand\n├── go.mod\n└── go.sum\n```\n\n`main.go` should be minimal — see [assets\u002Fexamples\u002Fmain.go](assets\u002Fexamples\u002Fmain.go).\n\n## Root Command Setup\n\nThe root command initializes Viper configuration and sets up global behavior via `PersistentPreRunE`. See [assets\u002Fexamples\u002Froot.go](assets\u002Fexamples\u002Froot.go).\n\nKey points:\n\n- `SilenceUsage: true` MUST be set — prevents printing the full usage text on every error\n- `SilenceErrors: true` MUST be set — lets you control error output format yourself\n- `PersistentPreRunE` runs before every subcommand, so config is always initialized\n- Logs go to stderr, output goes to stdout\n\n## Subcommands\n\nAdd subcommands by creating separate files in `cmd\u002Fmyapp\u002F` and registering them in `init()`. See [assets\u002Fexamples\u002Fserve.go](assets\u002Fexamples\u002Fserve.go) for a complete subcommand example including command groups.\n\n## Flags\n\nSee [assets\u002Fexamples\u002Fflags.go](assets\u002Fexamples\u002Fflags.go) for all flag patterns:\n\n### Persistent vs Local\n\n- **Persistent** flags are inherited by all subcommands (e.g., `--config`)\n- **Local** flags only apply to the command they're defined on (e.g., `--port`)\n\n### Required Flags\n\nUse `MarkFlagRequired`, `MarkFlagsMutuallyExclusive`, and `MarkFlagsOneRequired` for flag constraints.\n\n### Flag Validation with RegisterFlagCompletionFunc\n\nProvide completion suggestions for flag values.\n\n### Always Bind Flags to Viper\n\nThis ensures `viper.GetInt(\"port\")` returns the flag value, env var `MYAPP_PORT`, or config file value — whichever has highest precedence.\n\n## Argument Validation\n\nCobra provides built-in validators for positional arguments. See [assets\u002Fexamples\u002Fargs.go](assets\u002Fexamples\u002Fargs.go) for both built-in and custom validation examples.\n\n| Validator                   | Description                          |\n| --------------------------- | ------------------------------------ |\n| `cobra.NoArgs`              | Fails if any args provided           |\n| `cobra.ExactArgs(n)`        | Requires exactly n args              |\n| `cobra.MinimumNArgs(n)`     | Requires at least n args             |\n| `cobra.MaximumNArgs(n)`     | Allows at most n args                |\n| `cobra.RangeArgs(min, max)` | Requires between min and max         |\n| `cobra.ExactValidArgs(n)`   | Exactly n args, must be in ValidArgs |\n\n## Configuration with Viper\n\nViper resolves configuration values in this order (highest to lowest precedence):\n\n1. **CLI flags** (explicit user input)\n2. **Environment variables** (deployment config)\n3. **Config file** (persistent settings)\n4. **Defaults** (set in code)\n\nSee [assets\u002Fexamples\u002Fconfig.go](assets\u002Fexamples\u002Fconfig.go) for complete Viper integration including struct unmarshaling and config file watching.\n\n### Example Config File (.myapp.yaml)\n\n```yaml\nport: 8080\nhost: localhost\nlog-level: info\ndatabase:\n  dsn: postgres:\u002F\u002Flocalhost:5432\u002Fmyapp\n  max-conn: 25\n```\n\nWith the setup above, these are all equivalent:\n\n- Flag: `--port 9090`\n- Env var: `MYAPP_PORT=9090`\n- Config file: `port: 9090`\n\n## Version and Build Info\n\nVersion SHOULD be embedded at compile time using `ldflags`. See [assets\u002Fexamples\u002Fversion.go](assets\u002Fexamples\u002Fversion.go) for the version command and build instructions.\n\n## Exit Codes\n\nExit codes MUST follow Unix conventions:\n\n| Code  | Meaning           | When to Use                               |\n| ----- | ----------------- | ----------------------------------------- |\n| 0     | Success           | Operation completed normally              |\n| 1     | General error     | Runtime failure                           |\n| 2     | Usage error       | Invalid flags or arguments                |\n| 64-78 | BSD sysexits      | Specific error categories                 |\n| 126   | Cannot execute    | Permission denied                         |\n| 127   | Command not found | Missing dependency                        |\n| 128+N | Signal N          | Terminated by signal (e.g., 130 = SIGINT) |\n\nSee [assets\u002Fexamples\u002Fexit_codes.go](assets\u002Fexamples\u002Fexit_codes.go) for a pattern mapping errors to exit codes.\n\n## I\u002FO Patterns\n\nSee [assets\u002Fexamples\u002Foutput.go](assets\u002Fexamples\u002Foutput.go) for all I\u002FO patterns:\n\n- **stdout vs stderr**: NEVER write diagnostic output to stdout — stdout is for program output (pipeable), stderr for logs\u002Ferrors\u002Fdiagnostics\n- **Detecting pipe vs terminal**: check `os.ModeCharDevice` on stdout\n- **Machine-readable output**: support `--output` flag for table\u002Fjson\u002Fplain formats\n- **Colors**: use `fatih\u002Fcolor` which auto-disables when output is not a terminal\n\n## Signal Handling\n\nSignal handling MUST use `signal.NotifyContext` to propagate cancellation through context. See [assets\u002Fexamples\u002Fsignal.go](assets\u002Fexamples\u002Fsignal.go) for graceful HTTP server shutdown.\n\n## Shell Completions\n\nCobra generates completions for bash, zsh, fish, and PowerShell automatically. See [assets\u002Fexamples\u002Fcompletion.go](assets\u002Fexamples\u002Fcompletion.go) for both the completion command and custom flag\u002Fargument completions.\n\n## Testing CLI Commands\n\nTest commands by executing them programmatically and capturing output. See [assets\u002Fexamples\u002Fcli_test.go](assets\u002Fexamples\u002Fcli_test.go).\n\nUse `cmd.OutOrStdout()` and `cmd.ErrOrStderr()` in commands (instead of `os.Stdout` \u002F `os.Stderr`) so output can be captured in tests.\n\n## Common Mistakes\n\n| Mistake | Fix |\n| --- | --- |\n| Writing to `os.Stdout` directly | Tests can't capture output. Use `cmd.OutOrStdout()` which tests can redirect to a buffer |\n| Calling `os.Exit()` inside `RunE` | Cobra's error handling, deferred functions, and cleanup code never run. Return an error, let `main()` decide |\n| Not binding flags to Viper | Flags won't be configurable via env\u002Fconfig. Call `viper.BindPFlag` for every configurable flag |\n| Missing `viper.SetEnvPrefix` | `PORT` collides with other tools. Use a prefix (`MYAPP_PORT`) to namespace env vars |\n| Logging to stdout | Unix pipes chain stdout — logs corrupt the data stream for the next program. Logs go to stderr |\n| Printing usage on every error | Full help text on every error is noise. Set `SilenceUsage: true`, save full usage for `--help` |\n| Config file required | Users without a config file get a crash. Ignore `viper.ConfigFileNotFoundError` — config should be optional |\n| Not using `PersistentPreRunE` | Config initialization must happen before any subcommand. Use root's `PersistentPreRunE` |\n| Hardcoded version string | Version gets out of sync with tags. Inject via `ldflags` at build time from git tags |\n| Not supporting `--output` format | Scripts can't parse human-readable output. Add JSON\u002Ftable\u002Fplain for machine consumption |\n\n## Related Skills\n\nSee `samber\u002Fcc-skills-golang@golang-project-layout`, `samber\u002Fcc-skills-golang@golang-dependency-injection`, `samber\u002Fcc-skills-golang@golang-testing`, `samber\u002Fcc-skills-golang@golang-design-patterns` skills.\n","**Persona:** You are a Go CLI engineer. You build tools that feel native to the Unix shell — composable, scriptable, and predictable under automation.\n\n**Modes:**\n\n- **Build** — creating a new CLI from scratch: follow the project structure, root command setup, flag binding, and version embedding sections sequentially.\n- **Extend** — adding subcommands, flags, or completions to an existing CLI: read the current command tree first, then apply changes consistent with the existing structure.\n- **Review** — auditing an existing CLI for correctness: check the Common Mistakes table, verify `SilenceUsage`\u002F`SilenceErrors`, flag-to-Viper binding, exit codes, and stdout\u002Fstderr discipline.\n\n# Go CLI Best Practices\n\nUse Cobra + Viper as the default stack for Go CLI applications. Cobra provides the command\u002Fsubcommand\u002Fflag structure and Viper handles configuration from files, environment variables, and flags with automatic layering. This combination powers kubectl, docker, gh, hugo, and most production Go CLIs.\n\nWhen using Cobra or Viper, refer to the library's official documentation and code examples for current API signatures.\n\nFor trivial single-purpose tools with no subcommands and few flags, stdlib `flag` is sufficient.\n\n## Quick Reference\n\n| Concern             | Package \u002F Tool                       |\n| ------------------- | ------------------------------------ |\n| Commands & flags    | `github.com\u002Fspf13\u002Fcobra`             |\n| Configuration       | `github.com\u002Fspf13\u002Fviper`             |\n| Flag parsing        | `github.com\u002Fspf13\u002Fpflag` (via Cobra) |\n| Colored output      | `github.com\u002Ffatih\u002Fcolor`             |\n| Table output        | `github.com\u002Folekukonko\u002Ftablewriter`  |\n| Interactive prompts | `github.com\u002Fcharmbracelet\u002Fbubbletea` |\n| Version injection   | `go build -ldflags`                  |\n| Distribution        | `goreleaser`                         |\n\n## Project Structure\n\nOrganize CLI commands in `cmd\u002Fmyapp\u002F` with one file per command. Keep `main.go` minimal — it only calls `Execute()`.\n\n```\nmyapp\u002F\n├── cmd\u002F\n│   └── myapp\u002F\n│       ├── main.go              # package main, only calls Execute()\n│       ├── root.go              # Root command + Viper init\n│       ├── serve.go             # \"serve\" subcommand\n│       ├── migrate.go           # \"migrate\" subcommand\n│       └── version.go           # \"version\" subcommand\n├── go.mod\n└── go.sum\n```\n\n`main.go` should be minimal — see [assets\u002Fexamples\u002Fmain.go](assets\u002Fexamples\u002Fmain.go).\n\n## Root Command Setup\n\nThe root command initializes Viper configuration and sets up global behavior via `PersistentPreRunE`. See [assets\u002Fexamples\u002Froot.go](assets\u002Fexamples\u002Froot.go).\n\nKey points:\n\n- `SilenceUsage: true` MUST be set — prevents printing the full usage text on every error\n- `SilenceErrors: true` MUST be set — lets you control error output format yourself\n- `PersistentPreRunE` runs before every subcommand, so config is always initialized\n- Logs go to stderr, output goes to stdout\n\n## Subcommands\n\nAdd subcommands by creating separate files in `cmd\u002Fmyapp\u002F` and registering them in `init()`. See [assets\u002Fexamples\u002Fserve.go](assets\u002Fexamples\u002Fserve.go) for a complete subcommand example including command groups.\n\n## Flags\n\nSee [assets\u002Fexamples\u002Fflags.go](assets\u002Fexamples\u002Fflags.go) for all flag patterns:\n\n### Persistent vs Local\n\n- **Persistent** flags are inherited by all subcommands (e.g., `--config`)\n- **Local** flags only apply to the command they're defined on (e.g., `--port`)\n\n### Required Flags\n\nUse `MarkFlagRequired`, `MarkFlagsMutuallyExclusive`, and `MarkFlagsOneRequired` for flag constraints.\n\n### Flag Validation with RegisterFlagCompletionFunc\n\nProvide completion suggestions for flag values.\n\n### Always Bind Flags to Viper\n\nThis ensures `viper.GetInt(\"port\")` returns the flag value, env var `MYAPP_PORT`, or config file value — whichever has highest precedence.\n\n## Argument Validation\n\nCobra provides built-in validators for positional arguments. See [assets\u002Fexamples\u002Fargs.go](assets\u002Fexamples\u002Fargs.go) for both built-in and custom validation examples.\n\n| Validator                   | Description                          |\n| --------------------------- | ------------------------------------ |\n| `cobra.NoArgs`              | Fails if any args provided           |\n| `cobra.ExactArgs(n)`        | Requires exactly n args              |\n| `cobra.MinimumNArgs(n)`     | Requires at least n args             |\n| `cobra.MaximumNArgs(n)`     | Allows at most n args                |\n| `cobra.RangeArgs(min, max)` | Requires between min and max         |\n| `cobra.ExactValidArgs(n)`   | Exactly n args, must be in ValidArgs |\n\n## Configuration with Viper\n\nViper resolves configuration values in this order (highest to lowest precedence):\n\n1. **CLI flags** (explicit user input)\n2. **Environment variables** (deployment config)\n3. **Config file** (persistent settings)\n4. **Defaults** (set in code)\n\nSee [assets\u002Fexamples\u002Fconfig.go](assets\u002Fexamples\u002Fconfig.go) for complete Viper integration including struct unmarshaling and config file watching.\n\n### Example Config File (.myapp.yaml)\n\n```yaml\nport: 8080\nhost: localhost\nlog-level: info\ndatabase:\n  dsn: postgres:\u002F\u002Flocalhost:5432\u002Fmyapp\n  max-conn: 25\n```\n\nWith the setup above, these are all equivalent:\n\n- Flag: `--port 9090`\n- Env var: `MYAPP_PORT=9090`\n- Config file: `port: 9090`\n\n## Version and Build Info\n\nVersion SHOULD be embedded at compile time using `ldflags`. See [assets\u002Fexamples\u002Fversion.go](assets\u002Fexamples\u002Fversion.go) for the version command and build instructions.\n\n## Exit Codes\n\nExit codes MUST follow Unix conventions:\n\n| Code  | Meaning           | When to Use                               |\n| ----- | ----------------- | ----------------------------------------- |\n| 0     | Success           | Operation completed normally              |\n| 1     | General error     | Runtime failure                           |\n| 2     | Usage error       | Invalid flags or arguments                |\n| 64-78 | BSD sysexits      | Specific error categories                 |\n| 126   | Cannot execute    | Permission denied                         |\n| 127   | Command not found | Missing dependency                        |\n| 128+N | Signal N          | Terminated by signal (e.g., 130 = SIGINT) |\n\nSee [assets\u002Fexamples\u002Fexit_codes.go](assets\u002Fexamples\u002Fexit_codes.go) for a pattern mapping errors to exit codes.\n\n## I\u002FO Patterns\n\nSee [assets\u002Fexamples\u002Foutput.go](assets\u002Fexamples\u002Foutput.go) for all I\u002FO patterns:\n\n- **stdout vs stderr**: NEVER write diagnostic output to stdout — stdout is for program output (pipeable), stderr for logs\u002Ferrors\u002Fdiagnostics\n- **Detecting pipe vs terminal**: check `os.ModeCharDevice` on stdout\n- **Machine-readable output**: support `--output` flag for table\u002Fjson\u002Fplain formats\n- **Colors**: use `fatih\u002Fcolor` which auto-disables when output is not a terminal\n\n## Signal Handling\n\nSignal handling MUST use `signal.NotifyContext` to propagate cancellation through context. See [assets\u002Fexamples\u002Fsignal.go](assets\u002Fexamples\u002Fsignal.go) for graceful HTTP server shutdown.\n\n## Shell Completions\n\nCobra generates completions for bash, zsh, fish, and PowerShell automatically. See [assets\u002Fexamples\u002Fcompletion.go](assets\u002Fexamples\u002Fcompletion.go) for both the completion command and custom flag\u002Fargument completions.\n\n## Testing CLI Commands\n\nTest commands by executing them programmatically and capturing output. See [assets\u002Fexamples\u002Fcli_test.go](assets\u002Fexamples\u002Fcli_test.go).\n\nUse `cmd.OutOrStdout()` and `cmd.ErrOrStderr()` in commands (instead of `os.Stdout` \u002F `os.Stderr`) so output can be captured in tests.\n\n## Common Mistakes\n\n| Mistake | Fix |\n| --- | --- |\n| Writing to `os.Stdout` directly | Tests can't capture output. Use `cmd.OutOrStdout()` which tests can redirect to a buffer |\n| Calling `os.Exit()` inside `RunE` | Cobra's error handling, deferred functions, and cleanup code never run. Return an error, let `main()` decide |\n| Not binding flags to Viper | Flags won't be configurable via env\u002Fconfig. Call `viper.BindPFlag` for every configurable flag |\n| Missing `viper.SetEnvPrefix` | `PORT` collides with other tools. Use a prefix (`MYAPP_PORT`) to namespace env vars |\n| Logging to stdout | Unix pipes chain stdout — logs corrupt the data stream for the next program. Logs go to stderr |\n| Printing usage on every error | Full help text on every error is noise. Set `SilenceUsage: true`, save full usage for `--help` |\n| Config file required | Users without a config file get a crash. Ignore `viper.ConfigFileNotFoundError` — config should be optional |\n| Not using `PersistentPreRunE` | Config initialization must happen before any subcommand. Use root's `PersistentPreRunE` |\n| Hardcoded version string | Version gets out of sync with tags. Inject via `ldflags` at build time from git tags |\n| Not supporting `--output` format | Scripts can't parse human-readable output. Add JSON\u002Ftable\u002Fplain for machine consumption |\n\n## Related Skills\n\nSee `samber\u002Fcc-skills-golang@golang-project-layout`, `samber\u002Fcc-skills-golang@golang-dependency-injection`, `samber\u002Fcc-skills-golang@golang-testing`, `samber\u002Fcc-skills-golang@golang-design-patterns` skills.\n",{"name":5,"license":15,"metadata":49,"description":7,"allowed-tools":58,"compatibility":59,"user-invocable":60},{"author":50,"version":51,"openclaw":52},"samber","1.1.3",{"emoji":53,"install":54,"homepage":55,"requires":56},"?",[],"https:\u002F\u002Fgithub.com\u002Fsamber\u002Fcc-skills-golang",{"bins":57},[43],"Read Edit Write Glob Grep Bash(go:*) Bash(golangci-lint:*) Bash(git:*) Agent 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-cli",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":70,"prompt":80,"zipAvailable":60},[71,74,77],{"tool":72,"command":73},"npx","npx skills add luokai0\u002Fai-agent-skills-by-luo-kai --skill golang-cli",{"tool":75,"command":76},"bunx","bunx skills add luokai0\u002Fai-agent-skills-by-luo-kai --skill golang-cli",{"tool":78,"command":79},"pnpm","pnpm dlx skills add luokai0\u002Fai-agent-skills-by-luo-kai --skill golang-cli","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fluokai0\u002Fai-agent-skills-by-luo-kai\u002Fblob\u002Fmain\u002Fai-agent-skills\u002F22-clawhub-skills\u002Fgolang-cli\u002FSKILL.md",[82,88,92,98,102,106,110,114,118,122,126,130,134,138,142],{"path":83,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":86,"sourceHtmlUrl":87},"_meta.json","REFERENCE","参考文档",129,"https:\u002F\u002Fgithub.com\u002Fluokai0\u002Fai-agent-skills-by-luo-kai\u002Fblob\u002Fmain\u002Fai-agent-skills\u002F22-clawhub-skills\u002Fgolang-cli\u002F_meta.json",{"path":89,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":90,"sourceHtmlUrl":91},".clawhub\u002Forigin.json",142,"https:\u002F\u002Fgithub.com\u002Fluokai0\u002Fai-agent-skills-by-luo-kai\u002Fblob\u002Fmain\u002Fai-agent-skills\u002F22-clawhub-skills\u002Fgolang-cli\u002F.clawhub\u002Forigin.json",{"path":93,"resourceType":94,"resourceTypeDesc":95,"sizeBytes":96,"sourceHtmlUrl":97},"assets\u002Fexamples\u002Fargs.go","SCRIPT","脚本",1020,"https:\u002F\u002Fgithub.com\u002Fluokai0\u002Fai-agent-skills-by-luo-kai\u002Fblob\u002Fmain\u002Fai-agent-skills\u002F22-clawhub-skills\u002Fgolang-cli\u002Fassets\u002Fexamples\u002Fargs.go",{"path":99,"resourceType":94,"resourceTypeDesc":95,"sizeBytes":100,"sourceHtmlUrl":101},"assets\u002Fexamples\u002Fcli_test.go",1258,"https:\u002F\u002Fgithub.com\u002Fluokai0\u002Fai-agent-skills-by-luo-kai\u002Fblob\u002Fmain\u002Fai-agent-skills\u002F22-clawhub-skills\u002Fgolang-cli\u002Fassets\u002Fexamples\u002Fcli_test.go",{"path":103,"resourceType":94,"resourceTypeDesc":95,"sizeBytes":104,"sourceHtmlUrl":105},"assets\u002Fexamples\u002Fcompletion.go",1657,"https:\u002F\u002Fgithub.com\u002Fluokai0\u002Fai-agent-skills-by-luo-kai\u002Fblob\u002Fmain\u002Fai-agent-skills\u002F22-clawhub-skills\u002Fgolang-cli\u002Fassets\u002Fexamples\u002Fcompletion.go",{"path":107,"resourceType":94,"resourceTypeDesc":95,"sizeBytes":108,"sourceHtmlUrl":109},"assets\u002Fexamples\u002Fconfig.go",1764,"https:\u002F\u002Fgithub.com\u002Fluokai0\u002Fai-agent-skills-by-luo-kai\u002Fblob\u002Fmain\u002Fai-agent-skills\u002F22-clawhub-skills\u002Fgolang-cli\u002Fassets\u002Fexamples\u002Fconfig.go",{"path":111,"resourceType":94,"resourceTypeDesc":95,"sizeBytes":112,"sourceHtmlUrl":113},"assets\u002Fexamples\u002Fexit_codes.go",494,"https:\u002F\u002Fgithub.com\u002Fluokai0\u002Fai-agent-skills-by-luo-kai\u002Fblob\u002Fmain\u002Fai-agent-skills\u002F22-clawhub-skills\u002Fgolang-cli\u002Fassets\u002Fexamples\u002Fexit_codes.go",{"path":115,"resourceType":94,"resourceTypeDesc":95,"sizeBytes":116,"sourceHtmlUrl":117},"assets\u002Fexamples\u002Fflags.go",1322,"https:\u002F\u002Fgithub.com\u002Fluokai0\u002Fai-agent-skills-by-luo-kai\u002Fblob\u002Fmain\u002Fai-agent-skills\u002F22-clawhub-skills\u002Fgolang-cli\u002Fassets\u002Fexamples\u002Fflags.go",{"path":119,"resourceType":94,"resourceTypeDesc":95,"sizeBytes":120,"sourceHtmlUrl":121},"assets\u002Fexamples\u002Fmain.go",120,"https:\u002F\u002Fgithub.com\u002Fluokai0\u002Fai-agent-skills-by-luo-kai\u002Fblob\u002Fmain\u002Fai-agent-skills\u002F22-clawhub-skills\u002Fgolang-cli\u002Fassets\u002Fexamples\u002Fmain.go",{"path":123,"resourceType":94,"resourceTypeDesc":95,"sizeBytes":124,"sourceHtmlUrl":125},"assets\u002Fexamples\u002Foutput.go",1791,"https:\u002F\u002Fgithub.com\u002Fluokai0\u002Fai-agent-skills-by-luo-kai\u002Fblob\u002Fmain\u002Fai-agent-skills\u002F22-clawhub-skills\u002Fgolang-cli\u002Fassets\u002Fexamples\u002Foutput.go",{"path":127,"resourceType":94,"resourceTypeDesc":95,"sizeBytes":128,"sourceHtmlUrl":129},"assets\u002Fexamples\u002Froot.go",1803,"https:\u002F\u002Fgithub.com\u002Fluokai0\u002Fai-agent-skills-by-luo-kai\u002Fblob\u002Fmain\u002Fai-agent-skills\u002F22-clawhub-skills\u002Fgolang-cli\u002Fassets\u002Fexamples\u002Froot.go",{"path":131,"resourceType":94,"resourceTypeDesc":95,"sizeBytes":132,"sourceHtmlUrl":133},"assets\u002Fexamples\u002Fserve.go",735,"https:\u002F\u002Fgithub.com\u002Fluokai0\u002Fai-agent-skills-by-luo-kai\u002Fblob\u002Fmain\u002Fai-agent-skills\u002F22-clawhub-skills\u002Fgolang-cli\u002Fassets\u002Fexamples\u002Fserve.go",{"path":135,"resourceType":94,"resourceTypeDesc":95,"sizeBytes":136,"sourceHtmlUrl":137},"assets\u002Fexamples\u002Fsignal.go",831,"https:\u002F\u002Fgithub.com\u002Fluokai0\u002Fai-agent-skills-by-luo-kai\u002Fblob\u002Fmain\u002Fai-agent-skills\u002F22-clawhub-skills\u002Fgolang-cli\u002Fassets\u002Fexamples\u002Fsignal.go",{"path":139,"resourceType":94,"resourceTypeDesc":95,"sizeBytes":140,"sourceHtmlUrl":141},"assets\u002Fexamples\u002Fversion.go",871,"https:\u002F\u002Fgithub.com\u002Fluokai0\u002Fai-agent-skills-by-luo-kai\u002Fblob\u002Fmain\u002Fai-agent-skills\u002F22-clawhub-skills\u002Fgolang-cli\u002Fassets\u002Fexamples\u002Fversion.go",{"path":143,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":144,"sourceHtmlUrl":145},"evals\u002Fevals.json",16416,"https:\u002F\u002Fgithub.com\u002Fluokai0\u002Fai-agent-skills-by-luo-kai\u002Fblob\u002Fmain\u002Fai-agent-skills\u002F22-clawhub-skills\u002Fgolang-cli\u002Fevals\u002Fevals.json",[147,172,189,214,247,281],{"skillNo":148,"name":149,"nameZh":6,"description":150,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":151,"categories":152,"keywords":153,"publishedAt":44},"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",[],[35,154,155,156,157,158,159,160,161,162,163,164,165,166,31,167,168,169,170,171],"contracts","write contracts","storage","secure","create","generate","collection","model","decision","ask","smart-contracts","selection","objects","nft","token","aptos","critical","move",{"skillNo":173,"name":174,"nameZh":6,"description":175,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":176,"categories":177,"keywords":178,"publishedAt":44},"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",[],[179,180,181,182,183,184,185,186,187,188],"web","search","web search","搜索","baidu","bing","duckduckgo","百度","多引擎","internet",{"skillNo":190,"name":191,"nameZh":6,"description":192,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":193,"categories":194,"keywords":198,"publishedAt":44},"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",[195],{"categoryNo":196,"categoryName":197,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[199,200,201,202,203,204,205,41,180,39,206,36,35,207,208,209,210,211,212,213],"build","solo","solo build","MCP","workflow","commit","tasks","plan","auto","references","context7","query","scaffolding","ship it","project",{"skillNo":215,"name":216,"nameZh":6,"description":217,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":218,"categories":219,"keywords":226,"publishedAt":44},"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",[220,223],{"categoryNo":221,"categoryName":222,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000005","邮件与沟通",{"categoryNo":224,"categoryName":225,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[227,228,229,230,231,232,233,234,235,236,237,238,239,240,241,242,243,244,245,246],"react","email","react email","github","editor","components","react components","component","welcome","https","notifications","password","node","use","html","resend","visual","emails","rendering","with",{"skillNo":248,"name":249,"nameZh":6,"description":250,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":251,"categories":252,"keywords":263,"publishedAt":44},"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",[253,254,257,258],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":255,"categoryName":256,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":196,"categoryName":197,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":259,"categoryName":260,"taxonomyType":261,"taxonomyTypeDesc":262},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[28,264,265,266,267,268,269,270,271,272,273,274,275,276,277,278,279,280],"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":282,"name":283,"nameZh":6,"description":284,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":285,"categories":286,"keywords":287,"publishedAt":44},"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",[],[206,288,289,290,291,292,293,159,294,295,296,297,298,240,299,300,246,301],"implementation","hubspot","hubspot implementation plan","automation","feasibility","cleanup","planning","report","audit","audit report","phased implementation","dependencies","processes","hubspot audit"]