Golang Dependency Management
Manage Go dependencies — go.mod, upgrades, conflicts, vulnerability scans, vendoring
- What
- Manage Go dependencies — go.mod, upgrades, conflicts, vulnerability scans, vendoring
- Cost
- Free
- Needs
- a Go project with the Go toolchain installed; govulncheck (installable via: go install golang.org/x/vuln/cmd/govulncheck@latest) for the vulnerability-scanning parts
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — a dependency-stewardship playbook for Go: go.mod and go.sum, install and upgrade flows, Minimal Version Selection, conflict resolution with replace/exclude/retract, govulncheck scanning of the module tree, outdated-dependency and binary-size auditing, vendoring, tool directives, and go.work workspaces. Its hard rule: the agent must ask the user before adding any new dependency — because agents suggest unmaintained or unnecessary packages and the standard library often already solves the problem. Distinct from the published samber-golang-security skill (that one is about fixing exploitable vulnerabilities in code, not choosing versions) and from samber-golang-continuous-integration (bots like Dependabot/Renovate wired into CI). By @samber, listed here with credit to its creator. Honest caveats: requires a Go project; needs govulncheck for the scanning parts. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Prerequisites: a Go project with the Go toolchain installed; govulncheck (installable via: go install golang.org/x/vuln/cmd/govulncheck@latest) for the vulnerability-scanning parts Install "Golang Dependency Management" for me. Manage Go dependencies — go.mod, upgrades, conflicts, vulnerability scans, vendoring Repository: https://github.com/samber/cc-skills-golang/blob/main/skills/golang-dependency-management/SKILL.md 1. Fetch the SKILL.md file for the samber-golang-dependency-management skill from the repository into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "samber-golang-dependency-management". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. any accounts, API keys, or CLI tools mentioned in the prerequisites above). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. Never ask me to paste secrets in chat — credentials go through the secure vault or environment variables. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.