[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71N87XSM319PTF3R4V4RBFC":3,"skill-same:01M71N87XSM319PTF3R4V4RBFC":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":28,"publishedAt":49,"linkOnly":50,"markdownContent":51,"markdownBody":52,"frontMatter":53,"refName":71,"commitSha":72,"skillDirectory":73,"forksCount":14,"repositoryHtmlUrl":74,"repositoryHomepageUrl":75,"ownerHtmlUrl":76,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":77,"install":78,"resources":90},"01M71N87XSM319PTF3R4V4RBFC","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`).","pattanation\u002FNorvik","pattanation","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F235419268?v=4","01M71M5THHYYB15ME8R2E4FCZG","Patta","01M71M5TJM1NDM992M8PDKYR2K",0,"MIT","https:\u002F\u002Fgithub.com\u002Fpattanation\u002FNorvik\u002Fblob\u002Fclaude\u002Finstall-gsd-build-foQdV\u002F.agents\u002Fskills\u002Fgolang-gopls\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48],"golang","golang gopls","gopls","Bash","when","definition","hierarchy","ecosystem","extracting","lsp","generated","MCP","api","vulnerability","actions","search","code","official","ai coding agents","mcp server","2026-11-10 10:56:23",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":54,"description":7,"allowed-tools":68,"compatibility":69,"user-invocable":70},{"author":55,"version":56,"openclaw":57},"samber","1.0.0",{"emoji":58,"install":59,"homepage":64,"requires":65,"skill-library-version":67},"🛰️",[60],{"bins":61,"kind":62,"package":63},[31],"go","golang.org\u002Fx\u002Ftools\u002Fgopls@latest","https:\u002F\u002Fgithub.com\u002Fsamber\u002Fcc-skills-golang",{"bins":66},[62,31],"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,"claude\u002Finstall-gsd-build-foQdV","d86cd127f527124b5fd0fd0bc679a4d79b7d01d7",".agents\u002Fskills\u002Fgolang-gopls","https:\u002F\u002Fgithub.com\u002Fpattanation\u002FNorvik","https:\u002F\u002Fnorvik-orpin.vercel.app","https:\u002F\u002Fgithub.com\u002Fpattanation","2026-07-17 11:17:04",{"source":8,"skillName":5,"commands":79,"prompt":89,"zipAvailable":70},[80,83,86],{"tool":81,"command":82},"npx","npx skills add pattanation\u002FNorvik --skill golang-gopls",{"tool":84,"command":85},"bunx","bunx skills add pattanation\u002FNorvik --skill golang-gopls",{"tool":87,"command":88},"pnpm","pnpm dlx skills add pattanation\u002FNorvik --skill golang-gopls","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fpattanation\u002FNorvik\u002Fblob\u002Fclaude\u002Finstall-gsd-build-foQdV\u002F.agents\u002Fskills\u002Fgolang-gopls\u002FSKILL.md",[91,97,101,105,109],{"path":92,"resourceType":93,"resourceTypeDesc":94,"sizeBytes":95,"sourceHtmlUrl":96},"references\u002Fcli.md","REFERENCE","参考文档",9182,"https:\u002F\u002Fgithub.com\u002Fpattanation\u002FNorvik\u002Fblob\u002Fclaude\u002Finstall-gsd-build-foQdV\u002F.agents\u002Fskills\u002Fgolang-gopls\u002Freferences\u002Fcli.md",{"path":98,"resourceType":93,"resourceTypeDesc":94,"sizeBytes":99,"sourceHtmlUrl":100},"references\u002Ffeatures.md",18498,"https:\u002F\u002Fgithub.com\u002Fpattanation\u002FNorvik\u002Fblob\u002Fclaude\u002Finstall-gsd-build-foQdV\u002F.agents\u002Fskills\u002Fgolang-gopls\u002Freferences\u002Ffeatures.md",{"path":102,"resourceType":93,"resourceTypeDesc":94,"sizeBytes":103,"sourceHtmlUrl":104},"references\u002Fmatrix.md",3320,"https:\u002F\u002Fgithub.com\u002Fpattanation\u002FNorvik\u002Fblob\u002Fclaude\u002Finstall-gsd-build-foQdV\u002F.agents\u002Fskills\u002Fgolang-gopls\u002Freferences\u002Fmatrix.md",{"path":106,"resourceType":93,"resourceTypeDesc":94,"sizeBytes":107,"sourceHtmlUrl":108},"references\u002Fmcp.md",4951,"https:\u002F\u002Fgithub.com\u002Fpattanation\u002FNorvik\u002Fblob\u002Fclaude\u002Finstall-gsd-build-foQdV\u002F.agents\u002Fskills\u002Fgolang-gopls\u002Freferences\u002Fmcp.md",{"path":110,"resourceType":93,"resourceTypeDesc":94,"sizeBytes":111,"sourceHtmlUrl":112},"references\u002Fsettings.md",5255,"https:\u002F\u002Fgithub.com\u002Fpattanation\u002FNorvik\u002Fblob\u002Fclaude\u002Finstall-gsd-build-foQdV\u002F.agents\u002Fskills\u002Fgolang-gopls\u002Freferences\u002Fsettings.md",[114,147,173,196,218,233],{"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":118,"licenseFileUrl":119,"sourceHtmlUrl":120,"categories":121,"keywords":128,"publishedAt":146},"01M71QDV4DM8T19HEHWATEF1K4","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fpattanation\u002FNorvik\u002Fblob\u002Fclaude\u002Finstall-gsd-build-foQdV\u002F.agents\u002Fskills\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fpattanation\u002FNorvik\u002Fblob\u002Fclaude\u002Finstall-gsd-build-foQdV\u002F.agents\u002Fskills\u002Fwebapp-testing\u002FSKILL.md",[122,125],{"categoryNo":123,"categoryName":124,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":126,"categoryName":127,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[129,130,131,132,133,134,135,136,137,138,139,140,141,142,143,144,145],"webapp","testing","webapp testing","for","applications","local","frontend","debugging","toolkit","logs","browser","with","playwright","web","behavior","ui","screenshots","2026-11-10 13:02:02",{"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":118,"licenseFileUrl":151,"sourceHtmlUrl":152,"categories":153,"keywords":155,"publishedAt":146},"01M71QDH2GGMXGA9105C9W1N7B","web-artifacts-builder","Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn\u002Fui). Use for complex artifacts requiring state management, routing, or shadcn\u002Fui components - not for simple single-file HTML\u002FJSX artifacts.","https:\u002F\u002Fgithub.com\u002Fpattanation\u002FNorvik\u002Fblob\u002Fclaude\u002Finstall-gsd-build-foQdV\u002F.agents\u002Fskills\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fpattanation\u002FNorvik\u002Fblob\u002Fclaude\u002Finstall-gsd-build-foQdV\u002F.agents\u002Fskills\u002Fweb-artifacts-builder\u002FSKILL.md",[154],{"categoryNo":126,"categoryName":127,"taxonomyType":21,"taxonomyTypeDesc":22},[156,157,158,142,159,160,161,132,162,163,135,164,165,166,167,168,169,170,171,172],"builder","artifacts builder","artifacts","web artifacts builder","single-file","css","Tailwind","ui components","single","use","file","components","react","multi","state","routing","state management",{"skillNo":174,"name":175,"nameZh":6,"description":176,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":177,"sourceHtmlUrl":178,"categories":179,"keywords":181,"publishedAt":146},"01M71QD9T2XC3EWMQNN9ACNWQ1","vueuse-functions","Apply VueUse composables where appropriate to build concise, maintainable Vue.js \u002F Nuxt features.","https:\u002F\u002Fgithub.com\u002Fpattanation\u002FNorvik\u002Fblob\u002Fclaude\u002Finstall-gsd-build-foQdV\u002F.agents\u002Fskills\u002Fvueuse-functions\u002FLICENSE.md","https:\u002F\u002Fgithub.com\u002Fpattanation\u002FNorvik\u002Fblob\u002Fclaude\u002Finstall-gsd-build-foQdV\u002F.agents\u002Fskills\u002Fvueuse-functions\u002FSKILL.md",[180],{"categoryNo":126,"categoryName":127,"taxonomyType":21,"taxonomyTypeDesc":22},[182,183,184,185,186,187,188,189,190,191,192,193,194,195],"functions","vueuse","vueuse functions","project","nuxt","apply","github","concise","build","https","features","vue","js","composables",{"skillNo":197,"name":198,"nameZh":6,"description":199,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":200,"sourceHtmlUrl":201,"categories":202,"keywords":205,"publishedAt":146},"01M71QD51HWSGYMCMB7RW7PGK8","vue-testing-best-practices","Use for Vue.js testing. Covers Vitest, Vue Test Utils, component testing, mocking, testing patterns, and Playwright for E2E testing.","https:\u002F\u002Fgithub.com\u002Fpattanation\u002FNorvik\u002Fblob\u002Fclaude\u002Finstall-gsd-build-foQdV\u002F.agents\u002Fskills\u002Fvue-testing-best-practices\u002FLICENSE.md","https:\u002F\u002Fgithub.com\u002Fpattanation\u002FNorvik\u002Fblob\u002Fclaude\u002Finstall-gsd-build-foQdV\u002F.agents\u002Fskills\u002Fvue-testing-best-practices\u002FSKILL.md",[203,204],{"categoryNo":123,"categoryName":124,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":126,"categoryName":127,"taxonomyType":21,"taxonomyTypeDesc":22},[206,130,207,193,208,141,209,210,211,188,212,132,213,214,215,165,216,194,217],"vue testing best practices","testing best practices","best practices","test","testing patterns","component","vitest","mocking","e2e","utils","patterns","e2e testing",{"skillNo":219,"name":220,"nameZh":6,"description":221,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":222,"sourceHtmlUrl":223,"categories":224,"keywords":226,"publishedAt":146},"01M71QD358H2DJ9THJRBP77T3T","vue-router-best-practices","Vue Router 4 patterns, navigation guards, route params, and route-component lifecycle interactions.","https:\u002F\u002Fgithub.com\u002Fpattanation\u002FNorvik\u002Fblob\u002Fclaude\u002Finstall-gsd-build-foQdV\u002F.agents\u002Fskills\u002Fvue-router-best-practices\u002FLICENSE.md","https:\u002F\u002Fgithub.com\u002Fpattanation\u002FNorvik\u002Fblob\u002Fclaude\u002Finstall-gsd-build-foQdV\u002F.agents\u002Fskills\u002Fvue-router-best-practices\u002FSKILL.md",[225],{"categoryNo":126,"categoryName":127,"taxonomyType":21,"taxonomyTypeDesc":22},[227,193,228,208,229,211,230,188,216,231,232],"router","vue router best practices","route","guards","navigation","lifecycle",{"skillNo":234,"name":235,"nameZh":6,"description":236,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":237,"sourceHtmlUrl":238,"categories":239,"keywords":241,"publishedAt":146},"01M71QCYPNWDE2MQZ1TF3ED5S4","vue-best-practices","MUST be used for Vue.js tasks. Strongly recommends Composition API with `\u003Cscript setup>` and TypeScript as the standard approach. Covers Vue 3, SSR, Volar, vue-tsc. Load for any Vue, .vue files, Vue Router, Pinia, or Vite with Vue work. ALWAYS use Composition API unless the project explicitly requires Options API.","https:\u002F\u002Fgithub.com\u002Fpattanation\u002FNorvik\u002Fblob\u002Fclaude\u002Finstall-gsd-build-foQdV\u002F.agents\u002Fskills\u002Fvue-best-practices\u002FLICENSE.md","https:\u002F\u002Fgithub.com\u002Fpattanation\u002FNorvik\u002Fblob\u002Fclaude\u002Finstall-gsd-build-foQdV\u002F.agents\u002Fskills\u002Fvue-best-practices\u002FSKILL.md",[240],{"categoryNo":126,"categoryName":127,"taxonomyType":21,"taxonomyTypeDesc":22},[242,193,208,243,185,244,245,41,227,246,247,248,249,250,251,132,252,165,253,254],"vue best practices","Composition","files","tasks","pinia","work","options","ssr","typescript","as","vite","load","standard"]