[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79APV61PDVK15XVAS7VP3R0":3,"skill-same:01M79APV61PDVK15XVAS7VP3R0":85},{"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":42,"commitSha":43,"skillDirectory":44,"forksCount":45,"repositoryHtmlUrl":46,"repositoryHomepageUrl":6,"ownerHtmlUrl":47,"ownerBlogUrl":48,"ownerDescription":6,"updatedAt":49,"install":50,"resources":62},"01M79APV61PDVK15XVAS7VP3R0","golang-gopls",null,"Golang semantic code intelligence via `gopls`, the official Go language server — go-to-definition, find references, call\u002Fimplementation hierarchy, workspace symbol search, package API discovery, diagnostics, safe rename, refactors (extract\u002Finline\u002Ffill\u002Frewrite code actions), formatting, and generated tests. Reaches an agent via gopls's own MCP server (`go_*` tools), Claude Code's native `LSP` tool, or the `gopls` CLI. Use when navigating or refactoring Go code — jumping to a definition, finding call sites before a rename, understanding a file's or package's dependencies, running diagnostics after an edit, or extracting\u002Finlining\u002Frenaming. Not for the published ecosystem — packages not in your `go.mod`, versions, licenses, importers — → See `samber\u002Fcc-skills-golang@golang-pkg-go-dev` skill (`godig`). Not for a whole-tree vulnerability audit → See `samber\u002Fcc-skills-golang@golang-security` skill (`govulncheck`).","CCH-HQ\u002Fcchp-automation","CCH-HQ","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F253065381?v=4","01M79AG9QPRTJEVTCT1ZS7TM9J","CCH HQ","01M79AG9RNM4TAB3PJQH71X62P",2,"MIT","https:\u002F\u002Fgithub.com\u002FCCH-HQ\u002Fcchp-automation\u002Fblob\u002Fmain\u002Fskills-backup\u002Fskills\u002Fgolang-gopls\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: golang-gopls\ndescription: \"Golang semantic code intelligence via `gopls`, the official Go language server — go-to-definition, find references, call\u002Fimplementation hierarchy, workspace symbol search, package API discovery, diagnostics, safe rename, refactors (extract\u002Finline\u002Ffill\u002Frewrite code actions), formatting, and generated tests. Reaches an agent via gopls's own MCP server (`go_*` tools), Claude Code's native `LSP` tool, or the `gopls` CLI. Use when navigating or refactoring Go code — jumping to a definition, finding call sites before a rename, understanding a file's or package's dependencies, running diagnostics after an edit, or extracting\u002Finlining\u002Frenaming. Not for the published ecosystem — packages not in your `go.mod`, versions, licenses, importers — → See `samber\u002Fcc-skills-golang@golang-pkg-go-dev` skill (`godig`). Not for a whole-tree vulnerability audit → See `samber\u002Fcc-skills-golang@golang-security` skill (`govulncheck`).\"\nuser-invocable: true\nlicense: MIT\ncompatibility: Designed for Claude Code or similar AI coding agents. Requires the gopls binary (go install golang.org\u002Fx\u002Ftools\u002Fgopls@latest) v0.20+ on PATH.\nmetadata:\n  author: samber\n  version: \"1.0.0\"\n  openclaw:\n    emoji: \"🛰️\"\n    homepage: https:\u002F\u002Fgithub.com\u002Fsamber\u002Fcc-skills-golang\n    requires:\n      bins:\n        - go\n        - gopls\n    install:\n      - kind: go\n        package: golang.org\u002Fx\u002Ftools\u002Fgopls@latest\n        bins: [gopls]\n    skill-library-version: \"0.22.0\"\nallowed-tools: Read Edit Write Glob Grep Bash(go:*) Bash(golangci-lint:*) Bash(git:*) Agent Bash(gopls:*) LSP mcp__gopls__*\n---\n\n**Persona:** You are a Go engineer who reaches for semantic code intelligence instead of grep whenever a question is about the resolved build — grep finds text, `gopls` finds meaning (types, call graphs, shadowing, implementation relationships).\n\n**Dependencies:** `gopls` — `go install golang.org\u002Fx\u002Ftools\u002Fgopls@latest` (v0.20+). The native `LSP` tool additionally needs `ENABLE_LSP_TOOL=1` and the `gopls-lsp@claude-plugins-official` marketplace plugin (see [references\u002Fmcp.md](references\u002Fmcp.md)).\n\n`gopls` is the official Go language server. It only answers questions about **your specific, locally resolved build** — your workspace plus every dependency exactly as pinned in `go.sum`, including `replace` directives. For a package that isn't part of that build (versions, docs, licenses, CVEs of something you haven't added yet), → See `samber\u002Fcc-skills-golang@golang-pkg-go-dev` skill (`godig`) instead.\n\n## Three ways to reach gopls\n\nNot interchangeable — pick by what you already know and what you need back:\n\n- **gopls's own MCP server (preferred for most tasks)** — purpose-built for agents: tools take names, file paths, and fuzzy queries instead of raw cursor positions. Register once per machine: `claude mcp add gopls -- gopls mcp`. Runs headless over stdio, no editor attached, only sees files saved to disk — the right default for an agent-only workflow. See [references\u002Fmcp.md](references\u002Fmcp.md) for every tool.\n- **The native `LSP` tool** — Claude Code's built-in editor-style integration. Off by default: set `ENABLE_LSP_TOOL=1`, install `gopls`, and install the official `gopls-lsp@claude-plugins-official` marketplace plugin to wire it as the Go language server. Operations (`goToDefinition`, `findReferences`, `hover`, `documentSymbol`, `workspaceSymbol`, `goToImplementation`, call hierarchy) are keyed by `line`\u002F`character`, so they're most useful once you already have a location — typically right after a grep or a read. Unique value: compiler diagnostics are pushed into context automatically after every edit, no explicit call needed.\n- **The `gopls` CLI** — same engine, invoked as `gopls \u003Ccommand> \u003Cfile:line:col>`. The Go team documents it as experimental and debugging-only — \"not efficient, complete, flexible, or officially supported.\" Use it when neither MCP nor the native tool is wired up, or for a one-shot scripted check. Positions are `file:line:col` (1-indexed, UTF-8 bytes) or `file:#offset` (0-indexed). See [references\u002Fcli.md](references\u002Fcli.md).\n\n**Preference order: MCP → native `LSP` → CLI.** MCP tools match how an agent thinks (by name\u002Fpath, not cursor position); the native tool adds free automatic diagnostics; the CLI is the documented fallback of last resort. Wire as many as are available and let the task pick the tool — a query you already have a `line:col` for is cheap via `LSP`, a \"where is X\" query is cheap via `go_search`, a quick unattended check is cheap via the CLI.\n\n## Capability → CLI → MCP → native LSP\n\nFull mapping of every capability to its CLI command, MCP tool, and native `LSP` op: [references\u002Fmatrix.md](references\u002Fmatrix.md).\n\n## Use cases\n\n- **Navigation** — jump to a definition, an implementation, or trace a call graph before touching code you didn't write. Details: [references\u002Ffeatures.md](references\u002Ffeatures.md#navigation).\n- **Code discovery** — learn a workspace's shape (`go_workspace`), fuzzy-search a symbol you can't place exactly (`go_search`), or read a dependency's public surface (`go_package_api`) before using it.\n- **Documentation** — hover for type\u002Fdoc\u002Fsize info, signature help while calling a function, or browse rendered package docs (`source.doc`, including internal packages pkg.go.dev never sees).\n- **Diagnostics & safety** — compiler and analyzer errors after every edit (`go_diagnostics` \u002F automatic with `LSP`), plus a lightweight `go_vulncheck` reachability check: once as a baseline right after detecting the workspace, and again after any `go.mod` change.\n- **Formatting** — canonical `gofmt`-equivalent formatting and import organization, both scriptable and code-action-driven.\n- **Refactoring** — safe rename (blocks a change that would break interface satisfaction), extract\u002Finline, and the full `refactor.rewrite.*` family (fill struct\u002Fswitch, invert if, split\u002Fjoin lines, remove unused parameter, add struct tags, implement interface). Full catalog with gotchas: [references\u002Ffeatures.md](references\u002Ffeatures.md#transformation).\n\n## Efficient workflows\n\nThese Read\u002FEdit workflows encode the order that avoids redundant queries and half-applied edits — treat every step as required, not optional, even to save a round trip.\n\n- **Session start** — call `go_workspace` once to detect whether this is a Go workspace at all; if it is, immediately follow with a baseline `go_vulncheck` to surface vulnerabilities the workspace already carries. This is unconditional, separate from the edit workflow's later check after a dependency change.\n\n**Read workflow** (understand before touching anything):\n\n1. `go_workspace` — layout (module\u002Fworkspace\u002FGOPATH); same call as the session-start check above if it hasn't run yet.\n2. `go_search` — fuzzy-locate a type\u002Ffunction\u002Fvariable by name.\n3. `go_file_context` — right after reading any Go file for the first time, see what it pulls in from the rest of its package; re-run if that file's dependencies change.\n4. `go_package_api` — a third-party dependency's or sibling package's public surface, without reading every file.\n\n**Edit workflow** (iterate until diagnostics are clean):\n\n1. Read first (workflow above).\n2. `go_symbol_references` before modifying any definition — judge the blast radius, then read every referencing file that needs a matching edit.\n3. Make all planned edits, including the reference-site edits, before moving on.\n4. `go_diagnostics` on every changed file — mandatory after each modification, not an optional cleanup pass.\n5. Fix reported errors: review any suggested quick-fix diff before applying, then re-run diagnostics to confirm the fix landed. Ignore hint\u002Finfo diagnostics unrelated to the task. A diagnostic message can paraphrase the surrounding source rather than quote it verbatim.\n6. Only if `go.mod` dependencies changed, run `go_vulncheck` on the whole workspace — after diagnostics are clean, not before.\n7. Run `go test \u003Cchanged-package-paths>` — not `.\u002F...` unless explicitly asked, since a full-repo run slows the iteration loop.\n\n**Gotchas worth knowing before you rely on a result:**\n\n- `references` results only reflect the **build configuration of the queried file** — a query on `foo_windows.go` will not surface matches in `bar_linux.go`; re-run under the relevant `GOOS`\u002Fbuild tags if a cross-platform result is missing.\n- `call_hierarchy` only shows **static** calls — calls through function values or interface methods are invisible to it; corroborate with `references` when the call site matters.\n- Extract\u002Finline refactors are less rigorous than rename: comments are sometimes dropped, and generated files marked `DO NOT EDIT` receive no code actions at all.\n- `refactor.rewrite.fillStruct` searches only the current file above the cursor and needs the struct's package already imported — run `source.organizeImports` first if the type was just typed in.\n\n## gopls vs godig vs Context7 vs govulncheck\n\n`gopls` only reasons about code present and resolvable in the local build:\n\n- For anything not tied to that build (version history, license, ecosystem-wide importers, CVEs of a package not yet added) → See `samber\u002Fcc-skills-golang@golang-pkg-go-dev` skill (`godig`) — it queries pkg.go.dev directly, no local checkout needed.\n- For a comprehensive, whole-tree vulnerability audit (CI gates, periodic sweeps) rather than gopls's lightweight on-demand `go_vulncheck` → See `samber\u002Fcc-skills-golang@golang-security` skill (`govulncheck`).\n- Context7 remains a fallback for non-Go docs or a Go module not indexed on pkg.go.dev.\n\nThe full task-to-tool matrix lives in the `samber\u002Fcc-skills-golang@golang-how-to` skill's \"`godig` vs gopls vs Context7 vs govulncheck\" section.\n","**Persona:** You are a Go engineer who reaches for semantic code intelligence instead of grep whenever a question is about the resolved build — grep finds text, `gopls` finds meaning (types, call graphs, shadowing, implementation relationships).\n\n**Dependencies:** `gopls` — `go install golang.org\u002Fx\u002Ftools\u002Fgopls@latest` (v0.20+). The native `LSP` tool additionally needs `ENABLE_LSP_TOOL=1` and the `gopls-lsp@claude-plugins-official` marketplace plugin (see [references\u002Fmcp.md](references\u002Fmcp.md)).\n\n`gopls` is the official Go language server. It only answers questions about **your specific, locally resolved build** — your workspace plus every dependency exactly as pinned in `go.sum`, including `replace` directives. For a package that isn't part of that build (versions, docs, licenses, CVEs of something you haven't added yet), → See `samber\u002Fcc-skills-golang@golang-pkg-go-dev` skill (`godig`) instead.\n\n## Three ways to reach gopls\n\nNot interchangeable — pick by what you already know and what you need back:\n\n- **gopls's own MCP server (preferred for most tasks)** — purpose-built for agents: tools take names, file paths, and fuzzy queries instead of raw cursor positions. Register once per machine: `claude mcp add gopls -- gopls mcp`. Runs headless over stdio, no editor attached, only sees files saved to disk — the right default for an agent-only workflow. See [references\u002Fmcp.md](references\u002Fmcp.md) for every tool.\n- **The native `LSP` tool** — Claude Code's built-in editor-style integration. Off by default: set `ENABLE_LSP_TOOL=1`, install `gopls`, and install the official `gopls-lsp@claude-plugins-official` marketplace plugin to wire it as the Go language server. Operations (`goToDefinition`, `findReferences`, `hover`, `documentSymbol`, `workspaceSymbol`, `goToImplementation`, call hierarchy) are keyed by `line`\u002F`character`, so they're most useful once you already have a location — typically right after a grep or a read. Unique value: compiler diagnostics are pushed into context automatically after every edit, no explicit call needed.\n- **The `gopls` CLI** — same engine, invoked as `gopls \u003Ccommand> \u003Cfile:line:col>`. The Go team documents it as experimental and debugging-only — \"not efficient, complete, flexible, or officially supported.\" Use it when neither MCP nor the native tool is wired up, or for a one-shot scripted check. Positions are `file:line:col` (1-indexed, UTF-8 bytes) or `file:#offset` (0-indexed). See [references\u002Fcli.md](references\u002Fcli.md).\n\n**Preference order: MCP → native `LSP` → CLI.** MCP tools match how an agent thinks (by name\u002Fpath, not cursor position); the native tool adds free automatic diagnostics; the CLI is the documented fallback of last resort. Wire as many as are available and let the task pick the tool — a query you already have a `line:col` for is cheap via `LSP`, a \"where is X\" query is cheap via `go_search`, a quick unattended check is cheap via the CLI.\n\n## Capability → CLI → MCP → native LSP\n\nFull mapping of every capability to its CLI command, MCP tool, and native `LSP` op: [references\u002Fmatrix.md](references\u002Fmatrix.md).\n\n## Use cases\n\n- **Navigation** — jump to a definition, an implementation, or trace a call graph before touching code you didn't write. Details: [references\u002Ffeatures.md](references\u002Ffeatures.md#navigation).\n- **Code discovery** — learn a workspace's shape (`go_workspace`), fuzzy-search a symbol you can't place exactly (`go_search`), or read a dependency's public surface (`go_package_api`) before using it.\n- **Documentation** — hover for type\u002Fdoc\u002Fsize info, signature help while calling a function, or browse rendered package docs (`source.doc`, including internal packages pkg.go.dev never sees).\n- **Diagnostics & safety** — compiler and analyzer errors after every edit (`go_diagnostics` \u002F automatic with `LSP`), plus a lightweight `go_vulncheck` reachability check: once as a baseline right after detecting the workspace, and again after any `go.mod` change.\n- **Formatting** — canonical `gofmt`-equivalent formatting and import organization, both scriptable and code-action-driven.\n- **Refactoring** — safe rename (blocks a change that would break interface satisfaction), extract\u002Finline, and the full `refactor.rewrite.*` family (fill struct\u002Fswitch, invert if, split\u002Fjoin lines, remove unused parameter, add struct tags, implement interface). Full catalog with gotchas: [references\u002Ffeatures.md](references\u002Ffeatures.md#transformation).\n\n## Efficient workflows\n\nThese Read\u002FEdit workflows encode the order that avoids redundant queries and half-applied edits — treat every step as required, not optional, even to save a round trip.\n\n- **Session start** — call `go_workspace` once to detect whether this is a Go workspace at all; if it is, immediately follow with a baseline `go_vulncheck` to surface vulnerabilities the workspace already carries. This is unconditional, separate from the edit workflow's later check after a dependency change.\n\n**Read workflow** (understand before touching anything):\n\n1. `go_workspace` — layout (module\u002Fworkspace\u002FGOPATH); same call as the session-start check above if it hasn't run yet.\n2. `go_search` — fuzzy-locate a type\u002Ffunction\u002Fvariable by name.\n3. `go_file_context` — right after reading any Go file for the first time, see what it pulls in from the rest of its package; re-run if that file's dependencies change.\n4. `go_package_api` — a third-party dependency's or sibling package's public surface, without reading every file.\n\n**Edit workflow** (iterate until diagnostics are clean):\n\n1. Read first (workflow above).\n2. `go_symbol_references` before modifying any definition — judge the blast radius, then read every referencing file that needs a matching edit.\n3. Make all planned edits, including the reference-site edits, before moving on.\n4. `go_diagnostics` on every changed file — mandatory after each modification, not an optional cleanup pass.\n5. Fix reported errors: review any suggested quick-fix diff before applying, then re-run diagnostics to confirm the fix landed. Ignore hint\u002Finfo diagnostics unrelated to the task. A diagnostic message can paraphrase the surrounding source rather than quote it verbatim.\n6. Only if `go.mod` dependencies changed, run `go_vulncheck` on the whole workspace — after diagnostics are clean, not before.\n7. Run `go test \u003Cchanged-package-paths>` — not `.\u002F...` unless explicitly asked, since a full-repo run slows the iteration loop.\n\n**Gotchas worth knowing before you rely on a result:**\n\n- `references` results only reflect the **build configuration of the queried file** — a query on `foo_windows.go` will not surface matches in `bar_linux.go`; re-run under the relevant `GOOS`\u002Fbuild tags if a cross-platform result is missing.\n- `call_hierarchy` only shows **static** calls — calls through function values or interface methods are invisible to it; corroborate with `references` when the call site matters.\n- Extract\u002Finline refactors are less rigorous than rename: comments are sometimes dropped, and generated files marked `DO NOT EDIT` receive no code actions at all.\n- `refactor.rewrite.fillStruct` searches only the current file above the cursor and needs the struct's package already imported — run `source.organizeImports` first if the type was just typed in.\n\n## gopls vs godig vs Context7 vs govulncheck\n\n`gopls` only reasons about code present and resolvable in the local build:\n\n- For anything not tied to that build (version history, license, ecosystem-wide importers, CVEs of a package not yet added) → See `samber\u002Fcc-skills-golang@golang-pkg-go-dev` skill (`godig`) — it queries pkg.go.dev directly, no local checkout needed.\n- For a comprehensive, whole-tree vulnerability audit (CI gates, periodic sweeps) rather than gopls's lightweight on-demand `go_vulncheck` → See `samber\u002Fcc-skills-golang@golang-security` skill (`govulncheck`).\n- Context7 remains a fallback for non-Go docs or a Go module not indexed on pkg.go.dev.\n\nThe full task-to-tool matrix lives in the `samber\u002Fcc-skills-golang@golang-how-to` skill's \"`godig` vs gopls vs Context7 vs govulncheck\" section.\n",{"name":5,"license":15,"metadata":24,"description":7,"allowed-tools":39,"compatibility":40,"user-invocable":41},{"author":25,"version":26,"openclaw":27},"samber","1.0.0",{"emoji":28,"install":29,"homepage":35,"requires":36,"skill-library-version":38},"🛰️",[30],{"bins":31,"kind":33,"package":34},[32],"gopls","go","golang.org\u002Fx\u002Ftools\u002Fgopls@latest","https:\u002F\u002Fgithub.com\u002Fsamber\u002Fcc-skills-golang",{"bins":37},[33,32],"0.22.0","Read Edit Write Glob Grep Bash(go:*) Bash(golangci-lint:*) Bash(git:*) Agent Bash(gopls:*) LSP mcp__gopls__*","Designed for Claude Code or similar AI coding agents. Requires the gopls binary (go install golang.org\u002Fx\u002Ftools\u002Fgopls@latest) v0.20+ on PATH.",true,"main","a93764baed707eda5a68d91e19e5719368e6335e","skills-backup\u002Fskills\u002Fgolang-gopls",0,"https:\u002F\u002Fgithub.com\u002FCCH-HQ\u002Fcchp-automation","https:\u002F\u002Fgithub.com\u002FCCH-HQ","https:\u002F\u002Fclaude-code-hub.app\u002F","2026-11-09 20:50:54",{"source":8,"skillName":5,"commands":51,"prompt":61,"zipAvailable":41},[52,55,58],{"tool":53,"command":54},"npx","npx skills add CCH-HQ\u002Fcchp-automation --skill golang-gopls",{"tool":56,"command":57},"bunx","bunx skills add CCH-HQ\u002Fcchp-automation --skill golang-gopls",{"tool":59,"command":60},"pnpm","pnpm dlx skills add CCH-HQ\u002Fcchp-automation --skill golang-gopls","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FCCH-HQ\u002Fcchp-automation\u002Fblob\u002Fmain\u002Fskills-backup\u002Fskills\u002Fgolang-gopls\u002FSKILL.md",[63,69,73,77,81],{"path":64,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":67,"sourceHtmlUrl":68},"references\u002Fcli.md","REFERENCE","参考文档",9182,"https:\u002F\u002Fgithub.com\u002FCCH-HQ\u002Fcchp-automation\u002Fblob\u002Fmain\u002Fskills-backup\u002Fskills\u002Fgolang-gopls\u002Freferences\u002Fcli.md",{"path":70,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":71,"sourceHtmlUrl":72},"references\u002Ffeatures.md",18498,"https:\u002F\u002Fgithub.com\u002FCCH-HQ\u002Fcchp-automation\u002Fblob\u002Fmain\u002Fskills-backup\u002Fskills\u002Fgolang-gopls\u002Freferences\u002Ffeatures.md",{"path":74,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":75,"sourceHtmlUrl":76},"references\u002Fmatrix.md",3320,"https:\u002F\u002Fgithub.com\u002FCCH-HQ\u002Fcchp-automation\u002Fblob\u002Fmain\u002Fskills-backup\u002Fskills\u002Fgolang-gopls\u002Freferences\u002Fmatrix.md",{"path":78,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":79,"sourceHtmlUrl":80},"references\u002Fmcp.md",4951,"https:\u002F\u002Fgithub.com\u002FCCH-HQ\u002Fcchp-automation\u002Fblob\u002Fmain\u002Fskills-backup\u002Fskills\u002Fgolang-gopls\u002Freferences\u002Fmcp.md",{"path":82,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":83,"sourceHtmlUrl":84},"references\u002Fsettings.md",5255,"https:\u002F\u002Fgithub.com\u002FCCH-HQ\u002Fcchp-automation\u002Fblob\u002Fmain\u002Fskills-backup\u002Fskills\u002Fgolang-gopls\u002Freferences\u002Fsettings.md",[86,93,100,107,114,121],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M79B44RKSB6Z0GENGYFCCZYA","writing-skills","Use when creating new skills, editing existing skills, or verifying skills work before deployment","https:\u002F\u002Fgithub.com\u002FCCH-HQ\u002Fcchp-automation\u002Fblob\u002Fmain\u002Fskills-backup\u002Fskills\u002Fwriting-skills\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":19},"01M79B410BHDSNHZ7MKAYXWJHS","writing-plans","Use when you have a spec or requirements for a multi-step task, before touching code","https:\u002F\u002Fgithub.com\u002FCCH-HQ\u002Fcchp-automation\u002Fblob\u002Fmain\u002Fskills-backup\u002Fskills\u002Fwriting-plans\u002FSKILL.md",[],[],{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":19},"01M79B3XK29MCD5HGD50YGYXQZ","wizard","Generate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar third-party dashboard, or running a one-off migration or cutover. Don't invoke this for steps the agent can perform itself.","https:\u002F\u002Fgithub.com\u002FCCH-HQ\u002Fcchp-automation\u002Fblob\u002Fmain\u002Fskills-backup\u002Fskills\u002Fwizard\u002FSKILL.md",[],[],{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":19},"01M79B3TFQEXXM2KK5V44H64DV","wayfinder","Plan a huge chunk of work — more than one agent session can hold — as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.","https:\u002F\u002Fgithub.com\u002FCCH-HQ\u002Fcchp-automation\u002Fblob\u002Fmain\u002Fskills-backup\u002Fskills\u002Fwayfinder\u002FSKILL.md",[],[],{"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":19},"01M79B3Q3WTMJDM6NNGG1X4NYK","verification-before-completion","Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always","https:\u002F\u002Fgithub.com\u002FCCH-HQ\u002Fcchp-automation\u002Fblob\u002Fmain\u002Fskills-backup\u002Fskills\u002Fverification-before-completion\u002FSKILL.md",[],[],{"skillNo":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":125,"categories":126,"keywords":127,"publishedAt":19},"01M79B3GW8YCKT7W489HKWFMNC","vercel-react-best-practices","React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React\u002FNext.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.","https:\u002F\u002Fgithub.com\u002FCCH-HQ\u002Fcchp-automation\u002Fblob\u002Fmain\u002Fskills-backup\u002Fskills\u002Fvercel-react-best-practices\u002FSKILL.md",[],[]]