agentleFS
httprunnerhttprunner/skills/go-installer/SKILL.md

go-installer

Skill2 starsChanged 9 months agoMITView on GitHub

Install and verify the Go toolchain on macOS, Linux, and Windows. Use when Go is required but not present, or when a specific Go version must be installed. Prefer system package managers (homebrew, apt, etc.) and fall back to official Go downloads when needed.

  • Deletes or force-pushes
  • Installs packages

The file

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 5 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Check whether Go is already installed.

    line 20
  2. Distinctive:

    If missing, install via OS package manager (preferred).

    line 21
  3. Distinctive:

    If package manager is unavailable or the required version is not available, install from the official Go downloads.

    line 22
  4. Very specific:

    Ensure PATH is updated and confirm go version.

    line 23
  5. Distinctive:

    If the command is missing, continue to installation.

    line 31
  6. Distinctive:

    Use this when a specific version is required or no package manager is available.

    line 80
  7. Very specific:

    Add C:\Go\bin to the system PATH.

    line 161
  8. Very specific:

    If the version still does not match, ensure the PATH order is correct and restart the shell.

    line 169

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Go Installer

Install or verify the Go toolchain with system package managers first, then fall back to official Go downloads when needed.

Path Convention

Canonical install and execution directory: ~/.agents/skills/go-installer/. Run commands from this directory:

cd ~/.agents/skills/go-installer

Quick workflow

  1. Check whether Go is already installed.
  2. If missing, install via OS package manager (preferred).
  3. If package manager is unavailable or the required version is not available, install from the official Go downloads.
  4. Ensure PATH is updated and confirm go version.

Verify

go version

If the command is missing, continue to installation.

Install via package manager (preferred)

macOS (Homebrew):

brew install go

Linux (Debian/Ubuntu apt):

sudo apt update
sudo apt install -y golang-go

Linux (Fedora/RHEL/CentOS dnf):

sudo dnf install -y golang

Linux (RHEL/CentOS yum):

sudo yum install -y golang

Linux (Arch pacman):

sudo pacman -S --noconfirm go

Windows (winget):

winget install --id GoLang.Go -e

Windows (Chocolatey):

choco install -y golang

Install from official Go downloads (fallback)

Use this when a specific version is required or no package manager is available.

Set the version explicitly (example uses Go 1.22.0):

GO_VER="go1.22.0"

macOS (tar.gz, user dir)

GO_VER="go1.22.0"
ARCH="$(uname -m)"
case "${ARCH}" in
  arm64) GO_ARCH="arm64" ;;
  x86_64) GO_ARCH="amd64" ;;
  *) echo "Unsupported arch: ${ARCH}"; exit 1 ;;
esac

TAR="${GO_VER}.darwin-${GO_ARCH}.tar.gz"
if command -v curl >/dev/null 2>&1; then
  curl -LO "https://go.dev/dl/${TAR}"
else
  wget -O "${TAR}" "https://go.dev/dl/${TAR}"
fi

rm -rf "${HOME}/.local/go"
mkdir -p "${HOME}/.local"
tar -C "${HOME}/.local" -xzf "${TAR}"

Linux (tar.gz, user dir)

GO_VER="go1.22.0"
ARCH="$(uname -m)"
case "${ARCH}" in
  aarch64) GO_ARCH="arm64" ;;
  x86_64) GO_ARCH="amd64" ;;
  *) echo "Unsupported arch: ${ARCH}"; exit 1 ;;
esac

TAR="${GO_VER}.linux-${GO_ARCH}.tar.gz"
if command -v curl >/dev/null 2>&1; then
  curl -LO "https://go.dev/dl/${TAR}"
else
  wget -O "${TAR}" "https://go.dev/dl/${TAR}"
fi

rm -rf "${HOME}/.local/go"
mkdir -p "${HOME}/.local"
tar -C "${HOME}/.local" -xzf "${TAR}"

Windows (.zip)

$GoVer = "go1.22.0"
$Arch = $env:PROCESSOR_ARCHITECTURE
switch ($Arch) {
  "ARM64" { $GoArch = "arm64" }
  "AMD64" { $GoArch = "amd64" }
  default { throw "Unsupported arch: $Arch" }
}

$Zip = "$GoVer.windows-$GoArch.zip"
Invoke-WebRequest -Uri "https://go.dev/dl/$Zip" -OutFile $Zip
if (Test-Path C:\Go) { Remove-Item -Recurse -Force C:\Go }
tar -C C:\ -xf $Zip

PATH updates

macOS/Linux (add to shell profile):

export PATH="$PATH:${HOME}/.local/go/bin"

Windows:

  • Add C:\Go\bin to the system PATH.

Post-check

go version

If the version still does not match, ensure the PATH order is correct and restart the shell.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.