agentleFS
gokite-aigokite-ai/passport-skills/passport-setup/SKILL.md

Passport Setup

Skill2 starsChanged 4 months agoMITView on GitHub

Install and verify the kpass CLI on this computer before running any other Passport skill. Invoke automatically when kpass is missing or when a Passport skill fails with a command-not-found error.

The file

We split this skill into the rules it gives an agent

10 rules. About 0 are common, 6 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Before installing, check if kpass is already present:

    line 23
  2. Distinctive:

    If this returns a path, kpass is installed.

    line 29
  3. Distinctive:

    If kpass is missing, install it with the official installer.

    line 33
  4. Distinctive:

    After receiving user approval, run the installer:

    line 41
  5. Very specific:

    If scripts/setup.sh is not available (single-folder skill install), obtain approval for this fallback command, then run it:

    line 47
  6. Distinctive:

    After the installer completes, reload your shell environment:

    line 83
  7. Distinctive:

    After installation, verify kpass works:

    line 92
  8. Very specific:

    If kpass --version fails, the installation did not succeed.

    line 100
  9. Very specific:

    Check kpass --help for available commands

    line 107
  10. Very specific:

    No authentication is required to install kpass.

    line 114

≈ “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

Passport Setup

Purpose

Install the kpass CLI on this computer so other Passport skills can run. Grok Bot installs skills but not external dependencies; this skill bridges the gap by installing the CLI itself.

When to Use

Invoke this skill automatically when:

  • command -v kpass returns nothing (kpass is not installed)
  • Any other Passport skill fails with "command not found: kpass"
  • The user asks to "install kpass", "set up Passport", or "prepare my environment for Kite"

Installation

Check First

Before installing, check if kpass is already present:

command -v kpass

If this returns a path, kpass is installed. Skip to verification.

Install on This Computer

If kpass is missing, install it with the official installer.

Security Note: This installer executes a remote script. For Grok Bot and similar autonomous agents running in isolated environments, this step may run automatically per the bot's security model. For interactive agent environments (Claude Code, Cursor, Cline), you must obtain explicit user approval before running this command. Show the user this exact command and wait for their confirmation:

bash <skill-directory>/../scripts/setup.sh

After receiving user approval, run the installer:

bash <skill-directory>/../scripts/setup.sh

If scripts/setup.sh is not available (single-folder skill install), obtain approval for this fallback command, then run it:

get_installer_base() {
  local base=""
  if [[ -n "${KPASS_BASE_URL:-}" ]]; then
    base="$KPASS_BASE_URL"
  else
    local base_file="<skill-directory>/../.installer-base"
    if [[ -f "$base_file" ]]; then
      base="$(tr -d '[:space:]' < "$base_file" 2>/dev/null)"
    fi
  fi
  if [[ -z "$base" ]]; then
    base="https://cli.gokite.ai"
  fi
  [[ $base =~ ^https://cli(\.staging)?\.gokite\.ai$ ]] || { echo "bad installer base: $base" >&2; return 1; }
  printf '%s' "$base"
}
INSTALLER_BASE="$(get_installer_base)" || exit 1
INSTALL_SCRIPT="$(mktemp)"
trap 'rm -f "$INSTALL_SCRIPT"' EXIT
if curl -fsSL --proto '=https' --proto-redir '=https' --max-redirs 0 "$INSTALLER_BASE/install.sh" -o "$INSTALL_SCRIPT" && \
   [[ -s "$INSTALL_SCRIPT" ]] && \
   [[ "$(head -1 "$INSTALL_SCRIPT")" == '#!'* ]]; then
  bash "$INSTALL_SCRIPT"
else
  echo "Installer download failed or is not a shell script" >&2; exit 1
fi

This installer:

  • Downloads the latest kpass CLI binary for your platform
  • Installs it to ~/.kpass/bin (or $KPASS_INSTALL_DIR/bin), with ~/.local/bin as a fallback
  • Updates your shell's PATH if needed

After the installer completes, reload your shell environment:

export PATH="${KPASS_INSTALL_DIR:-$HOME/.kpass}/bin:$HOME/.local/bin:$PATH"
hash -r

Verification

After installation, verify kpass works:

kpass --version

Expected output: a version at or above min_kpass_version in skills.json (currently 6.8.9 or later).

If kpass --version fails, the installation did not succeed. Report the error to the user and stop. Do not proceed to other Passport skills until verification passes.

Next Steps

Once kpass is installed and verified:

  • Other Passport skills can now run
  • The user may need to authenticate with authenticate-user before using paid features
  • Check kpass --help for available commands

Notes

  • This skill runs on the bot's own computer, not the user's machine
  • The installer is idempotent — safe to run multiple times
  • For production use only; the installer URL serves the live kpass release
  • No authentication is required to install kpass; authentication happens separately via authenticate-user

Dependencies

None. This is the bootstrap skill that makes other Passport skills possible.

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.