[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6JGPNWMCWE2ZE2KPFX49D4D":3,"skill-same:01M6JGPNWMCWE2ZE2KPFX49D4D":114},{"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":54,"commitSha":55,"skillDirectory":56,"forksCount":57,"repositoryHtmlUrl":58,"repositoryHomepageUrl":6,"ownerHtmlUrl":59,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":60,"install":61,"resources":74},"01M6JGPNWMCWE2ZE2KPFX49D4D","golang-dependency-management",null,"Provides dependency management strategies for Golang projects including go.mod management, installing\u002Fupgrading packages, semantic versioning, Minimal Version Selection, vulnerability scanning, outdated dependency tracking, dependency size analysis, automated updates with Dependabot\u002FRenovate, conflict resolution, and dependency graph visualization. Use this skill whenever adding, removing, updating, or auditing Go dependencies, resolving version conflicts, setting up automated dependency updates, analyzing binary size, or working with go.work workspaces.","muratovv\u002Fai-hats","muratovv","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F7502801?v=4","01M6JGCBN4KEJX012GPJVSH04T","Fedor Muratov","01M6JGCBSNMN7CW3RGTPPE0MN2",3,"MIT","https:\u002F\u002Fgithub.com\u002Fmuratovv\u002Fai-hats\u002Fblob\u002Fmaster\u002Fpackages\u002Fai-hats-library\u002Fsrc\u002Fai_hats_library\u002Fusage\u002Fskills\u002Fgolang-dependency-management\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"golang","golang dependency management","management","dependency management","dependency","up","updates","renovate","false","binary size","selection","workspaces","dependency graph","conflict resolution","ai coding agents","projects","Bash","analysis","dependabot","visualization","2026-11-10 10:12:30",false,"---\nname: golang-dependency-management\ndescription: >-\n  Provides dependency management strategies for Golang projects including\n  go.mod management, installing\u002Fupgrading packages, semantic versioning,\n  Minimal Version Selection, vulnerability scanning, outdated dependency\n  tracking, dependency size analysis, automated updates with\n  Dependabot\u002FRenovate, conflict resolution, and dependency graph\n  visualization. Use this skill whenever adding, removing, updating, or\n  auditing Go dependencies, resolving version conflicts, setting up\n  automated dependency updates, analyzing binary size, or working with\n  go.work workspaces.\nuser-invocable: false\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.2\"\nallowed-tools: Read Edit Write Glob Grep Bash(go:*) Bash(golangci-lint:*) Bash(git:*) Agent Bash(govulncheck:*) AskUserQuestion\n---\n\n**Persona:** You are a Go dependency steward. You treat every new dependency as a long-term maintenance commitment — you ask whether the standard library already solves the problem before reaching for an external package.\n\n# Go Dependency Management\n\n## AI Agent Rule: Ask Before Adding Dependencies\n\n**Before running `go get` to add any new dependency, AI agents MUST ask the user for confirmation.** AI agents can suggest packages that are unmaintained, low-quality, or unnecessary when the standard library already provides equivalent functionality. Using `go get -u` to upgrade an existing dependency is safe.\n\nBefore proposing a dependency, present:\n\n- Package name and import path\n- What it does and why it's needed\n- Whether the standard library covers the use case\n- GitHub stars, last commit date, and maintenance status (check via `gh repo view`)\n- License compatibility\n- Known alternatives\n\nThe `samber\u002Fcc-skills-golang@golang-popular-libraries` skill contains a curated list of vetted, production-ready libraries. Prefer recommending packages from that list. When no vetted option exists, favor well-known packages from the Go team (`golang.org\u002Fx\u002F...`) or established organizations over obscure alternatives.\n\n## Key Rules\n\n- `go.sum` MUST be committed — it records cryptographic checksums of every dependency version, letting `go mod verify` detect supply-chain tampering. Without it, a compromised proxy could silently substitute malicious code\n- `govulncheck .\u002F...` before every release — catches known CVEs in your dependency tree before they reach production\n- Check maintenance status, license, and stdlib alternatives before adding a dependency — every dependency increases attack surface, maintenance burden, and binary size\n- `go mod tidy` before every commit that changes dependencies — removes unused modules and adds missing ones, keeping go.mod honest\n\n## go.mod & go.sum\n\n### Essential Commands\n\n| Command           | Purpose                                      |\n| ----------------- | -------------------------------------------- |\n| `go mod tidy`     | Add missing deps, remove unused ones         |\n| `go mod download` | Download modules to local cache              |\n| `go mod verify`   | Verify cached modules match go.sum checksums |\n| `go mod vendor`   | Copy deps into `vendor\u002F` directory           |\n| `go mod edit`     | Edit go.mod programmatically (scripts, CI)   |\n| `go mod graph`    | Print the module requirement graph           |\n| `go mod why`      | Explain why a module or package is needed    |\n\n### Vendoring\n\nUse `go mod vendor` when you need hermetic builds (no network access), reproducibility guarantees beyond checksums, or when deploying to environments without module proxy access. CI pipelines and Docker builds sometimes benefit from vendoring. Run `go mod vendor` after any dependency change and commit the `vendor\u002F` directory.\n\n## Installing & Upgrading Dependencies\n\n### Adding a Dependency\n\n```bash\ngo get github.com\u002Fpkg\u002Ferrors           # Latest version\ngo get github.com\u002Fpkg\u002Ferrors@v0.9.1    # Specific version\ngo get github.com\u002Fpkg\u002Ferrors@latest    # Explicitly latest\ngo get github.com\u002Fpkg\u002Ferrors@master    # Specific branch (pseudo-version)\n```\n\n### Upgrading\n\n```bash\ngo get -u .\u002F...            # Upgrade ALL direct+indirect deps to latest minor\u002Fpatch\ngo get -u=patch .\u002F...      # Upgrade to latest patch only (safer)\ngo get github.com\u002Fpkg@v1.5 # Upgrade specific package\n```\n\n**Prefer `go get -u=patch`** for routine updates — patch versions change no public API (semver promise), so they're unlikely to break your build. Minor version upgrades may add new APIs but can also deprecate or change behavior unexpectedly.\n\n### Removing a Dependency\n\n```bash\ngo get github.com\u002Fpkg\u002Ferrors@none   # Mark for removal\ngo mod tidy                          # Clean up go.mod and go.sum\n```\n\n### Installing CLI Tools\n\n```bash\ngo install github.com\u002Fgolangci\u002Fgolangci-lint\u002Fcmd\u002Fgolangci-lint@latest\n```\n\n`go install` builds and installs a binary to `$GOPATH\u002Fbin`. Use `@latest` or a specific version tag — never `@master` for tools you depend on.\n\n### The tools.go Pattern\n\nPin tool versions in your module without importing them in production code:\n\n```go\n\u002F\u002Fgo:build tools\n\npackage tools\n\nimport (\n    _ \"github.com\u002Fgolangci\u002Fgolangci-lint\u002Fcmd\u002Fgolangci-lint\"\n    _ \"golang.org\u002Fx\u002Fvuln\u002Fcmd\u002Fgovulncheck\"\n)\n```\n\nThe build constraint ensures this file is never compiled. The blank imports keep the tools in `go.mod` so `go install` uses the pinned version. Run `go mod tidy` after creating this file.\n\n## Deep Dives\n\n- **[Versioning & MVS](.\u002Freferences\u002Fversioning.md)** — Semantic versioning rules (major.minor.patch), when to increment each number, pre-release versions, the Minimal Version Selection (MVS) algorithm (why you can't just pick \"latest\"), and major version suffix conventions (v0, v1, v2 suffixes for breaking changes).\n\n- **[Auditing Dependencies](.\u002Freferences\u002Fauditing.md)** — Vulnerability scanning with `govulncheck`, tracking outdated dependencies, analyzing which dependencies make the binary large (`goweight`), and distinguishing test-only vs binary dependencies to keep `go.mod` clean.\n\n- **[Dependency Conflicts & Resolution](.\u002Freferences\u002Fconflicts.md)** — Diagnosing version conflicts (what `go get` does when you request incompatible versions), resolution strategies (`replace` directives for local development, `exclude` for broken versions, `retract` for published versions that should be skipped), and workflows for conflicts across your dependency tree.\n\n- **[Go Workspaces](.\u002Freferences\u002Fworkspaces.md)** — `go.work` files for multi-module development (e.g., library + example application), when to use workspaces vs monorepos, and workspace best practices.\n\n- **[Automated Dependency Updates](.\u002Freferences\u002Fautomated-updates.md)** — Setting up Dependabot or Renovate for automatic dependency update PRs, auto-merge strategies (when to merge automatically vs require review), and handling security updates.\n\n- **[Visualizing the Dependency Graph](.\u002Freferences\u002Fvisualization.md)** — `go mod graph` to inspect the full dependency tree, `modgraphviz` to visualize it, and interactive tools to find which dependency chains cause bloat.\n\n## Cross-References\n\n- → See `samber\u002Fcc-skills-golang@golang-continuous-integration` skill for Dependabot\u002FRenovate CI setup\n- → See `samber\u002Fcc-skills-golang@golang-security` skill for vulnerability scanning with govulncheck\n- → See `samber\u002Fcc-skills-golang@golang-popular-libraries` skill for vetted library recommendations\n\n## Quick Reference\n\n```bash\n# Start a new module\ngo mod init github.com\u002Fuser\u002Fproject\n\n# Add a dependency\ngo get github.com\u002Fpkg\u002Ferrors@v0.9.1\n\n# Upgrade all deps (patch only, safer)\ngo get -u=patch .\u002F...\n\n# Remove unused deps\ngo mod tidy\n\n# Check for vulnerabilities\ngovulncheck .\u002F...\n\n# Check for outdated deps\ngo list -u -m -json all | go-mod-outdated -update -direct\n\n# Analyze binary size by dependency\ngoweight\n\n# Understand why a dep exists\ngo mod why -m github.com\u002Fsome\u002Fmodule\n\n# Visualize dependency graph\ngo mod graph | modgraphviz | dot -Tpng -o deps.png\n\n# Verify checksums\ngo mod verify\n```\n","**Persona:** You are a Go dependency steward. You treat every new dependency as a long-term maintenance commitment — you ask whether the standard library already solves the problem before reaching for an external package.\n\n# Go Dependency Management\n\n## AI Agent Rule: Ask Before Adding Dependencies\n\n**Before running `go get` to add any new dependency, AI agents MUST ask the user for confirmation.** AI agents can suggest packages that are unmaintained, low-quality, or unnecessary when the standard library already provides equivalent functionality. Using `go get -u` to upgrade an existing dependency is safe.\n\nBefore proposing a dependency, present:\n\n- Package name and import path\n- What it does and why it's needed\n- Whether the standard library covers the use case\n- GitHub stars, last commit date, and maintenance status (check via `gh repo view`)\n- License compatibility\n- Known alternatives\n\nThe `samber\u002Fcc-skills-golang@golang-popular-libraries` skill contains a curated list of vetted, production-ready libraries. Prefer recommending packages from that list. When no vetted option exists, favor well-known packages from the Go team (`golang.org\u002Fx\u002F...`) or established organizations over obscure alternatives.\n\n## Key Rules\n\n- `go.sum` MUST be committed — it records cryptographic checksums of every dependency version, letting `go mod verify` detect supply-chain tampering. Without it, a compromised proxy could silently substitute malicious code\n- `govulncheck .\u002F...` before every release — catches known CVEs in your dependency tree before they reach production\n- Check maintenance status, license, and stdlib alternatives before adding a dependency — every dependency increases attack surface, maintenance burden, and binary size\n- `go mod tidy` before every commit that changes dependencies — removes unused modules and adds missing ones, keeping go.mod honest\n\n## go.mod & go.sum\n\n### Essential Commands\n\n| Command           | Purpose                                      |\n| ----------------- | -------------------------------------------- |\n| `go mod tidy`     | Add missing deps, remove unused ones         |\n| `go mod download` | Download modules to local cache              |\n| `go mod verify`   | Verify cached modules match go.sum checksums |\n| `go mod vendor`   | Copy deps into `vendor\u002F` directory           |\n| `go mod edit`     | Edit go.mod programmatically (scripts, CI)   |\n| `go mod graph`    | Print the module requirement graph           |\n| `go mod why`      | Explain why a module or package is needed    |\n\n### Vendoring\n\nUse `go mod vendor` when you need hermetic builds (no network access), reproducibility guarantees beyond checksums, or when deploying to environments without module proxy access. CI pipelines and Docker builds sometimes benefit from vendoring. Run `go mod vendor` after any dependency change and commit the `vendor\u002F` directory.\n\n## Installing & Upgrading Dependencies\n\n### Adding a Dependency\n\n```bash\ngo get github.com\u002Fpkg\u002Ferrors           # Latest version\ngo get github.com\u002Fpkg\u002Ferrors@v0.9.1    # Specific version\ngo get github.com\u002Fpkg\u002Ferrors@latest    # Explicitly latest\ngo get github.com\u002Fpkg\u002Ferrors@master    # Specific branch (pseudo-version)\n```\n\n### Upgrading\n\n```bash\ngo get -u .\u002F...            # Upgrade ALL direct+indirect deps to latest minor\u002Fpatch\ngo get -u=patch .\u002F...      # Upgrade to latest patch only (safer)\ngo get github.com\u002Fpkg@v1.5 # Upgrade specific package\n```\n\n**Prefer `go get -u=patch`** for routine updates — patch versions change no public API (semver promise), so they're unlikely to break your build. Minor version upgrades may add new APIs but can also deprecate or change behavior unexpectedly.\n\n### Removing a Dependency\n\n```bash\ngo get github.com\u002Fpkg\u002Ferrors@none   # Mark for removal\ngo mod tidy                          # Clean up go.mod and go.sum\n```\n\n### Installing CLI Tools\n\n```bash\ngo install github.com\u002Fgolangci\u002Fgolangci-lint\u002Fcmd\u002Fgolangci-lint@latest\n```\n\n`go install` builds and installs a binary to `$GOPATH\u002Fbin`. Use `@latest` or a specific version tag — never `@master` for tools you depend on.\n\n### The tools.go Pattern\n\nPin tool versions in your module without importing them in production code:\n\n```go\n\u002F\u002Fgo:build tools\n\npackage tools\n\nimport (\n    _ \"github.com\u002Fgolangci\u002Fgolangci-lint\u002Fcmd\u002Fgolangci-lint\"\n    _ \"golang.org\u002Fx\u002Fvuln\u002Fcmd\u002Fgovulncheck\"\n)\n```\n\nThe build constraint ensures this file is never compiled. The blank imports keep the tools in `go.mod` so `go install` uses the pinned version. Run `go mod tidy` after creating this file.\n\n## Deep Dives\n\n- **[Versioning & MVS](.\u002Freferences\u002Fversioning.md)** — Semantic versioning rules (major.minor.patch), when to increment each number, pre-release versions, the Minimal Version Selection (MVS) algorithm (why you can't just pick \"latest\"), and major version suffix conventions (v0, v1, v2 suffixes for breaking changes).\n\n- **[Auditing Dependencies](.\u002Freferences\u002Fauditing.md)** — Vulnerability scanning with `govulncheck`, tracking outdated dependencies, analyzing which dependencies make the binary large (`goweight`), and distinguishing test-only vs binary dependencies to keep `go.mod` clean.\n\n- **[Dependency Conflicts & Resolution](.\u002Freferences\u002Fconflicts.md)** — Diagnosing version conflicts (what `go get` does when you request incompatible versions), resolution strategies (`replace` directives for local development, `exclude` for broken versions, `retract` for published versions that should be skipped), and workflows for conflicts across your dependency tree.\n\n- **[Go Workspaces](.\u002Freferences\u002Fworkspaces.md)** — `go.work` files for multi-module development (e.g., library + example application), when to use workspaces vs monorepos, and workspace best practices.\n\n- **[Automated Dependency Updates](.\u002Freferences\u002Fautomated-updates.md)** — Setting up Dependabot or Renovate for automatic dependency update PRs, auto-merge strategies (when to merge automatically vs require review), and handling security updates.\n\n- **[Visualizing the Dependency Graph](.\u002Freferences\u002Fvisualization.md)** — `go mod graph` to inspect the full dependency tree, `modgraphviz` to visualize it, and interactive tools to find which dependency chains cause bloat.\n\n## Cross-References\n\n- → See `samber\u002Fcc-skills-golang@golang-continuous-integration` skill for Dependabot\u002FRenovate CI setup\n- → See `samber\u002Fcc-skills-golang@golang-security` skill for vulnerability scanning with govulncheck\n- → See `samber\u002Fcc-skills-golang@golang-popular-libraries` skill for vetted library recommendations\n\n## Quick Reference\n\n```bash\n# Start a new module\ngo mod init github.com\u002Fuser\u002Fproject\n\n# Add a dependency\ngo get github.com\u002Fpkg\u002Ferrors@v0.9.1\n\n# Upgrade all deps (patch only, safer)\ngo get -u=patch .\u002F...\n\n# Remove unused deps\ngo mod tidy\n\n# Check for vulnerabilities\ngovulncheck .\u002F...\n\n# Check for outdated deps\ngo list -u -m -json all | go-mod-outdated -update -direct\n\n# Analyze binary size by dependency\ngoweight\n\n# Understand why a dep exists\ngo mod why -m github.com\u002Fsome\u002Fmodule\n\n# Visualize dependency graph\ngo mod graph | modgraphviz | dot -Tpng -o deps.png\n\n# Verify checksums\ngo mod verify\n```\n",{"name":5,"license":15,"metadata":49,"description":7,"allowed-tools":52,"compatibility":53,"user-invocable":45},{"author":50,"version":51},"samber","1.1.2","Read Edit Write Glob Grep Bash(go:*) Bash(golangci-lint:*) Bash(git:*) Agent Bash(govulncheck:*) AskUserQuestion","Designed for Claude Code or similar AI coding agents, and for projects using Golang.","master","b4819add93efbaf4d80627118ec34680406b309b","packages\u002Fai-hats-library\u002Fsrc\u002Fai_hats_library\u002Fusage\u002Fskills\u002Fgolang-dependency-management",1,"https:\u002F\u002Fgithub.com\u002Fmuratovv\u002Fai-hats","https:\u002F\u002Fgithub.com\u002Fmuratovv","2026-11-05 20:59:10",{"source":8,"skillName":5,"commands":62,"prompt":72,"zipAvailable":73},[63,66,69],{"tool":64,"command":65},"npx","npx skills add muratovv\u002Fai-hats --skill golang-dependency-management",{"tool":67,"command":68},"bunx","bunx skills add muratovv\u002Fai-hats --skill golang-dependency-management",{"tool":70,"command":71},"pnpm","pnpm dlx skills add muratovv\u002Fai-hats --skill golang-dependency-management","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmuratovv\u002Fai-hats\u002Fblob\u002Fmaster\u002Fpackages\u002Fai-hats-library\u002Fsrc\u002Fai_hats_library\u002Fusage\u002Fskills\u002Fgolang-dependency-management\u002FSKILL.md",true,[75,81,86,90,94,98,102,106,110],{"path":76,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":79,"sourceHtmlUrl":80},"evals\u002Fevals.json","REFERENCE","参考文档",11464,"https:\u002F\u002Fgithub.com\u002Fmuratovv\u002Fai-hats\u002Fblob\u002Fmaster\u002Fpackages\u002Fai-hats-library\u002Fsrc\u002Fai_hats_library\u002Fusage\u002Fskills\u002Fgolang-dependency-management\u002Fevals\u002Fevals.json",{"path":82,"resourceType":82,"resourceTypeDesc":83,"sizeBytes":84,"sourceHtmlUrl":85},"LICENSE","许可证",1070,"https:\u002F\u002Fgithub.com\u002Fmuratovv\u002Fai-hats\u002Fblob\u002Fmaster\u002Fpackages\u002Fai-hats-library\u002Fsrc\u002Fai_hats_library\u002Fusage\u002Fskills\u002Fgolang-dependency-management\u002FLICENSE",{"path":87,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":88,"sourceHtmlUrl":89},"metadata.yaml",673,"https:\u002F\u002Fgithub.com\u002Fmuratovv\u002Fai-hats\u002Fblob\u002Fmaster\u002Fpackages\u002Fai-hats-library\u002Fsrc\u002Fai_hats_library\u002Fusage\u002Fskills\u002Fgolang-dependency-management\u002Fmetadata.yaml",{"path":91,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":92,"sourceHtmlUrl":93},"references\u002Fauditing.md",3493,"https:\u002F\u002Fgithub.com\u002Fmuratovv\u002Fai-hats\u002Fblob\u002Fmaster\u002Fpackages\u002Fai-hats-library\u002Fsrc\u002Fai_hats_library\u002Fusage\u002Fskills\u002Fgolang-dependency-management\u002Freferences\u002Fauditing.md",{"path":95,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":96,"sourceHtmlUrl":97},"references\u002Fautomated-updates.md",1559,"https:\u002F\u002Fgithub.com\u002Fmuratovv\u002Fai-hats\u002Fblob\u002Fmaster\u002Fpackages\u002Fai-hats-library\u002Fsrc\u002Fai_hats_library\u002Fusage\u002Fskills\u002Fgolang-dependency-management\u002Freferences\u002Fautomated-updates.md",{"path":99,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":100,"sourceHtmlUrl":101},"references\u002Fconflicts.md",2101,"https:\u002F\u002Fgithub.com\u002Fmuratovv\u002Fai-hats\u002Fblob\u002Fmaster\u002Fpackages\u002Fai-hats-library\u002Fsrc\u002Fai_hats_library\u002Fusage\u002Fskills\u002Fgolang-dependency-management\u002Freferences\u002Fconflicts.md",{"path":103,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":104,"sourceHtmlUrl":105},"references\u002Fversioning.md",2747,"https:\u002F\u002Fgithub.com\u002Fmuratovv\u002Fai-hats\u002Fblob\u002Fmaster\u002Fpackages\u002Fai-hats-library\u002Fsrc\u002Fai_hats_library\u002Fusage\u002Fskills\u002Fgolang-dependency-management\u002Freferences\u002Fversioning.md",{"path":107,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":108,"sourceHtmlUrl":109},"references\u002Fvisualization.md",1473,"https:\u002F\u002Fgithub.com\u002Fmuratovv\u002Fai-hats\u002Fblob\u002Fmaster\u002Fpackages\u002Fai-hats-library\u002Fsrc\u002Fai_hats_library\u002Fusage\u002Fskills\u002Fgolang-dependency-management\u002Freferences\u002Fvisualization.md",{"path":111,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":112,"sourceHtmlUrl":113},"references\u002Fworkspaces.md",1227,"https:\u002F\u002Fgithub.com\u002Fmuratovv\u002Fai-hats\u002Fblob\u002Fmaster\u002Fpackages\u002Fai-hats-library\u002Fsrc\u002Fai_hats_library\u002Fusage\u002Fskills\u002Fgolang-dependency-management\u002Freferences\u002Fworkspaces.md",[115,140,165,184,208,222],{"skillNo":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":119,"categories":120,"keywords":121,"publishedAt":44},"01M6PVFB1SM738R2SRSRSF7CY6","tool-evaluation-protocol","Time-bounded protocol for evaluating new tools, libraries, or methodologies before adoption. Use when evaluating a candidate dependency for the project, researching a methodology (e.g. ML\u002FLLM frameworks, testing approaches), or following up on a hype-driven recommendation.","https:\u002F\u002Fgithub.com\u002Fmuratovv\u002Fai-hats\u002Fblob\u002Fmaster\u002Fpackages\u002Fai-hats-library\u002Fsrc\u002Fai_hats_library\u002Fexperimental\u002Fusage\u002Fskills\u002Ftool-evaluation-protocol\u002FSKILL.md",[],[122,123,124,125,126,127,128,129,130,131,132,28,29,133,134,135,136,137,138,139],"protocol","Evaluation","tool","tool evaluation protocol","testing","ml","libraries","adoption","methodology","Tools","use","frameworks","time","project","recommendation","for","bounded","candidate",{"skillNo":141,"name":142,"nameZh":6,"description":143,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":144,"categories":145,"keywords":146,"publishedAt":44},"01M6PVF7HATBEX1G7N50E2QT57","systematic-debugging","4-phase bug-fix protocol (evidence, pattern, hypothesis, verify). Use when investigating any error, failure, or unexpected behavior, handling bug reports from users or monitoring, or diagnosing test failures with non-obvious causes.","https:\u002F\u002Fgithub.com\u002Fmuratovv\u002Fai-hats\u002Fblob\u002Fmaster\u002Fpackages\u002Fai-hats-library\u002Fsrc\u002Fai_hats_library\u002Fexperimental\u002Fusage\u002Fskills\u002Fsystematic-debugging\u002FSKILL.md",[],[147,148,149,150,122,151,152,153,154,155,132,156,157,158,159,160,161,162,163,164],"systematic debugging","debugging","systematic","test","monitoring","hypothesis","verify","behavior","fix","evidence","bug","reports","pattern","users","error","with","bug-fix","phase",{"skillNo":166,"name":167,"nameZh":6,"description":168,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":169,"categories":170,"keywords":172,"publishedAt":44},"01M6PVF3MTQN3RPF73AN34856J","skill-template","Canonical template and validation guide for ai-hats skills. Use when creating a new skill, reviewing an existing one for structural compliance, or deciding which pattern fits a new behavior.","https:\u002F\u002Fgithub.com\u002Fmuratovv\u002Fai-hats\u002Fblob\u002Fmaster\u002Fpackages\u002Fai-hats-library\u002Fsrc\u002Fai_hats_library\u002Fexperimental\u002Fusage\u002Fskills\u002Fskill-template\u002FSKILL.md",[171],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[173,174,175,176,177,154,178,132,179,159,180,181,182,137,183],"template","skill template","validation","compliance","hats","guide","new skill","structural","canonical","which","Existing",{"skillNo":185,"name":186,"nameZh":6,"description":187,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":188,"categories":189,"keywords":191,"publishedAt":44},"01M6PVF06SCV28QARM5MQPANC9","skill-optimization","Audit and refactor library components to eliminate redundancy and staleness. Use during periodic library maintenance, after adding multiple new skills or rules, when a role's token budget is too high, or after retrospectives identify component issues.","https:\u002F\u002Fgithub.com\u002Fmuratovv\u002Fai-hats\u002Fblob\u002Fmaster\u002Fpackages\u002Fai-hats-library\u002Fsrc\u002Fai_hats_library\u002Fexperimental\u002Fusage\u002Fskills\u002Fskill-optimization\u002FSKILL.md",[190],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[192,193,194,195,196,197,198,199,200,201,132,202,203,204,205,206,207],"Optimization","skill optimization","components","component","issues","library","audit","refactor","Budget","Rules","periodic","maintenance","token","token budget","role","high",{"skillNo":209,"name":210,"nameZh":6,"description":211,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":212,"categories":213,"keywords":214,"publishedAt":44},"01M6PVEXM9717016T9MW82HDCT","silent-fallback-gate","PreToolUse hook — refuses an Edit or Write that adds an inert broad except. Use when a Python edit was blocked for a silent fallback.","https:\u002F\u002Fgithub.com\u002Fmuratovv\u002Fai-hats\u002Fblob\u002Fmaster\u002Fpackages\u002Fai-hats-library\u002Fsrc\u002Fai_hats_library\u002Fexperimental\u002Fusage\u002Fskills\u002Fsilent-fallback-gate\u002FSKILL.md",[],[215,216,217,218,219,220,132,221,137],"gate","fallback","silent fallback gate","python","write","edit","hook",{"skillNo":223,"name":224,"nameZh":6,"description":225,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":226,"categories":227,"keywords":229,"publishedAt":44},"01M6PVESM49C5NT7SB7N3F76VS","retro-to-framework","Convert an observation about agent behavior — from a retrospective or from a single incident — into a framework-level change (hook, rule, skill, skill update). Use after a retrospective identifies problems that are not project-specific, after an incident where an agent misapplied a component it had read, when CLAUDE.md band-aids accumulate (more than 3 per-project rules that could be generic), or when the same problem recurs across multiple projects.","https:\u002F\u002Fgithub.com\u002Fmuratovv\u002Fai-hats\u002Fblob\u002Fmaster\u002Fpackages\u002Fai-hats-library\u002Fsrc\u002Fai_hats_library\u002Fexperimental\u002Fusage\u002Fskills\u002Fretro-to-framework\u002FSKILL.md",[228],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[230,231,232,233,195,234,39,235,201,154,132,236,237,135,238,239,240,241,242,243],"framework","retro","retro to framework","change","retrospective","convert","incident","across","problem","about","more","skill update","single","generic"]