Skip to content
GSKILL

Run doctor

Check that your environment is ready for GSKILL and that declared skill requirements are satisfied.

Before you start

Section titled “Before you start”
  • GSKILL installed.

Steps

Section titled “Steps”
Terminal window
gskill doctor            # check environment + declared requirements
gskill doctor --json     # machine-readable report

Expected result

Section titled “Expected result”
  • gskill doctor reports on prerequisites such as the git binary, detected agents, and any external commands/environment variables that installed skills declare in their requires block.
  • It is read-only. A clean environment exits 0; problems are reported with actionable diagnostics.

When to use it

Section titled “When to use it”
  • Right after installing GSKILL, to confirm git and your agents are detected.
  • When a skill declares requires.commands (e.g. kubectl) or requires.environment (e.g. KUBECONFIG) and you want to confirm they’re present.
  • When agent links look wrong: a checkout made without symlink support (e.g. core.symlinks=false) leaves plain files where agent links should be — gskill doctor (and gskill project check) report it; the fix is to re-clone on a symlink-capable filesystem.

See also

Section titled “See also”