setup
/setup
Get this machine ready to deploy on Gagarin Cloud — install the gg CLI if it is missing, sign in, and check the rest of the toolchain (docker, git, gh or glab). Use when the user asks to set up, install or configure Gagarin, or when gg is not found.
- Author
- gagarin-cloud ↗
- Repository
- plugin ↗
- Licence
- MIT
- Last repository change
- 13.11.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 4
No signals detected. Repository changed on 13.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Get this machine ready to deploy on Gagarin Cloud — install the gg CLI if it is missing, sign in, and check the rest of the toolchain (docker, git, gh or glab). Use when the user asks to set up, install or configure Gagarin, or when gg is not found.
Original author description
Get this machine ready to deploy on Gagarin Cloud — install the gg CLI if it is missing, sign in, and check the rest of the toolchain (docker, git, gh or glab). Use when the user asks to set up, install or configure Gagarin, or when gg is not found.
How it works
- 1. Is gg already here?
- 2. Install it
- 3. Sign in
- 4. Check the skill is not ahead of the binary
- 5. Check the rest of the toolchain
- 6. Tell them what they have
SKILL.md preview
--- name: setup description: Get this machine ready to deploy on Gagarin Cloud — install the gg CLI if it is missing, sign in, and check the rest of the toolchain (docker, git, gh or glab). Use when the user asks to set up, install or configure Gagarin, or when gg is not found. --- Get the user ready to use Gagarin Cloud. Work through this in order and stop at the first step that needs them. If you cannot run commands where you are (ChatGPT on the web, for instance), none of this is yours to do: tell the user that `gg` is installed on the machine that holds their source, with the one-liner on https://gagarin.cloud or a package manager, and that from here the Gagarin MCP tools cover everything except building and pushing an image. Stop there. ## 1. Is `gg` already here? Run `command -v gg`. If it finds nothing, look where the installer puts it: `~/.local/bin/gg` (Windows: `%LOCALAPPDATA%\Programs\gg\gg.exe`). If either is there, run `gg version` (by its full path if it is not on `PATH`) and skip to step 3. If it is installed but not on `PATH`, give the user the same `PATH` advice as step 2 does. ## 2. Install it Use a package manager the machine already has. `command -v brew winget scoop go` says which. You may run these yourself: - macOS: `brew install --cask gagarin-cloud/tap/gg` (macOS only — casks do not work on Linux) - Windows: `winget install Gagarin.gg`, or `scoop bucket add gagarin https://github.com/gagarin-cloud/scoop-bucket` then `scoop install gagarin/gg` - any platform with a Go toolchain: `go install github.com/gagarin-cloud/gg@latest` Homebrew installs it as a **cask**, not a formula. If they already have a formula `gg` (`brew list gg` finds it and `brew list --cask gg` does not), tell them to `brew uninstall gg` once and then install the cask. If `go install` succeeds but the shell still cannot find `gg`, its bin directory (`go env GOPATH`/bin) is not on `PATH`. Say so and let them fix their profile. With none of those, the install is the user's to run, not yours. **Do not download a script or a binary and run it**, from gagarin.cloud or anywhere else. Point them at the one-line installer on https://gagarin.cloud — a shell one-liner on macOS and Linux, a PowerShell one on Windows — and tell them what it does: it checks the download against the release's `checksums.txt`, installs to `~/.local/bin` (Windows: `%LOCALAPPDATA%\Programs\gg`, added to their `PATH`) without `sudo`, and never edits a shell profile. On Linux a `.deb`, `.rpm` or `.apk` from https://github.com/gagarin-cloud/gg/releases also works; it needs `sudo`, so that too is theirs to run. Wait until they say it is done, then go back to step 1. If `~/.local/bin` is not on `PATH`, the installer prints the `export` line to add. Call `gg` by its full path (`~/.local/bin/gg`) for the rest of this session and tell the user the line; do not edit their shell configuration yourself. ## 3. Sign in Run `gg whoami` first. If it names an account, they are already signed in — say so and go on to step 4. Otherwise run `gg login`. It prints a link and a code and exits. **Relay both to the user exactly as printed** — you never handle a secret here. They open the link, sign in with GitHub or Google, check the page shows the same code, and approve. A new account starts with $5 on it. Once they say they have approved, run `gg login` again to collect it. ## 4. Check the skill is not ahead of the binary The skill ships in this plugin, not in `gg`, so the two update separately and it can describe a `gg` newer than theirs. Run `gg version`. If it prints "gg vX is available (you have vY)" on stderr, theirs is behind (`GAGARIN_NO_UPDATE_CHECK=1` silences that check). Say so and run `gg upgrade`: it upgrades the way `gg` was installed — brew, scoop, winget and `go install` are handed to that tool, a script or archive install replaces itself after checking the checksum, and a `.deb`/`.rpm`/`.apk` install prints a `sudo` command for the human to run. `gg upgrade --dry-run` previews it first. `gg upgrade` exists from v0.54.0. If theirs is older it will say the command is unknown: use the per-manager command (`brew upgrade --cask gagarin-cloud/tap/gg`, `scoop update gg`, `winget upgrade Gagarin.gg`, or `go install ...@latest`), or, for an installer or archive install, have them run the installer again as step 2 says. Do this rather than letting an agent meet a refusal later and conclude the command does not exist. ## 5. Check the rest of the toolchain `gg` is the only thing setup installs, but a good session needs more. Check each, and report them together as one short list rather than one by one. Of docker, git, gh, glab and jq, whichever `command -v docker git gh glab jq` prints no path for is missing. Then, for what was found: - `docker info` — is the daemon actually up? `docker buildx version` — only `gg registry copy` needs it. - `git rev-parse --is-inside-work-tree` and `git remote get-url origin` — is this a repository, and does it live on GitHub, GitLab or somewhere else? - `gh auth status` (GitHub) or `glab auth status` (GitLab) — only the one that matches the remote. Present but not signed in is the same as missing. What each one is for, and what to tell them when it is missing: | tool | why | if missing | |---|---|---| | docker, running | **required** to build and push — `gg ship` is impossible without it | ask them to install or start Docker Desktop, OrbStack or colima (Docker Engine on Linux) | | git | commit `.gagarin.json`, tie each image to a commit, find the forge | recommended; deploys still work | | gh / glab, signed in | set the CI secret without it passing through the transcript, and watch the pipeline run | recommended once they want CI; they run `gh auth login` / `glab auth login` themselves | | jq | pull one value out of JSON output | optional | Do not install or start any of these yourself, and do not sign in to `gh` or `glab` for them. Give the install command for their platform (`brew install gh`, `winget install GitHub.cli`, `sudo apt install gh`; `glab` the same way) and let them decide. A missing optional tool is a sentence, not a blocker. ## 6. Tell them what they have Briefly: `gg` drives everything, and the `gagarin` skill in this plugin documents it; the `ship` skill takes a repository to a working address and the `ci` skill wires a pipeline to deploy on push. If this session also has the Gagarin MCP tools connected, mention that those cover the same API without a local install — but that **only `gg` can build and push an image**, because that needs docker where the source is. Do not deploy anything as part of setup. Stop here.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · gagarin-cloud/plugin | 90 | MIT |
| HwangSlater/harness-fit | 100 | MIT |
| nesquikm/dev-process-toolkit | 100 | MIT |
| userKael/rastro | 100 | MIT |
| als-apg/osprey | 100 | BSD-3-Clause |
| dedujeong/gemba | 100 | Apache-2.0 |
| eigenwise/eigenwise-toolshed | 100 | MIT |
| awrshift/agent-memory-kit | 100 | MIT |
| lifecycle-innovations-limited/claude-ops | 100 | MIT |
Database snapshot: 13.11.2026 · package version 2280cd649db3 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100ci
Wire a repository's CI pipeline to deploy to Gagarin Cloud on push — mint a scoped deploy credential, store it as a secret, and write the workflow. Use when the user asks to set up continuous deployment, automate deploys, or deploy from GitHub Actions or another CI system to Gagarin. - 91gagarin
Deploy and operate applications on Gagarin with the gg CLI — ship a service from a Dockerfile, provision postgres, qdrant, valkey, iggy, rabbitmq, s3 or external-credential resources, wire what may reach what, put a service on the internet, give CI its own credential, start jobs… - 95wicked-garden-platform-glab-cli
Use when you need glab CLI patterns for GitLab — pipeline debugging, MR management, or release automation. Provides composable glab invocations for power users. NOT for GitHub (use the gh-cli skill) or simple git commands (use Bash). - 100refresh-forge-auth
Use when glab or gh authentication is broken/expired/missing, when a glab/gh command fails with "unauthorized" or "authentication required", or when someone asks to refresh, re-auth, or login to GitLab/GitHub CLI. - 100install-deps
Detect missing SCV system dependencies (git, gh, glab, curl, jq, ffmpeg, python3) and either show OS-specific install commands or run them. graphify (Claude Code skill) is detected separately and links to its install guide. Use whenever a command reports a missing external tool,… - 95agentpaas-setup
Install, configure, and verify AgentPaaS on macOS. Covers the full bootstrap: Docker/Colima, CLI via Homebrew tap, harness binary (bundled since v0.2.1), Hermes plugin installation, daemon start, and doctor verification. Use when the user says "set up agentpaas" or "install…