Qjzd Nav Cli Auth

Use when working with QJZD Nav CLI login, bearer token auth, profile setup, profile switching, current profile inspection, or fixing missing keyring credenti...

Security Scan

This is an instruction-only helper for the qjzd-nav CLI auth workflows and is internally consistent: it only requires the qjzd-nav binary and its instructions match the described purpose.

Purpose & Capability

Name/description describe CLI auth flows and the skill requires only the qjzd-nav binary; that is proportionate and expected for an auth helper.

Instruction Scope

SKILL.md confines itself to qjzd-nav auth commands (login, profile management, doctor, delete). It does reference that secrets live in the system keyring and shows examples using --password. Minor caution: the documentation encourages non-interactive use with --password and --force which can leak credentials via shell history or process lists; otherwise the instructions do not ask the agent to read unrelated files or credentials.

Install Mechanism

No install spec and no code files — instruction-only. Nothing is downloaded or written to disk by the skill itself.

Credentials

The skill declares no required env vars or credentials. It mentions that credentials are stored in the system keyring (expected for a CLI auth helper) but does not request unrelated secrets or external credentials.

Persistence & Privilege

always is false and model invocation is normal. The skill does not request persistent system-wide privileges or attempt to modify other skills or agent settings.

Assessment

This skill is coherent and lightweight, but take these precautions before using it: (1) Verify the qjzd-nav binary is from a trusted source and on your system PATH — the skill will run that binary. (2) Avoid passing plaintext passwords on the command line (the examples use --password); prefer interactive entry or other secure input methods to prevent exposure via shell history or process listings. (3) Be aware the CLI will store secrets in your system keyring and may contact the configured server (e.g., nav.qjzd.online) — only use with servers and binaries you trust. (4) Because the skill can run destructive ops (profile delete --force), double-check commands before running or allow the agent to confirm with you. If you want extra safety, run the CLI in an isolated environment (container/VM) or inspect the binary source before granting it use.

Use this skill for qjzd-nav auth and qjzd-nav auth profile.

If authentication is not set up yet, do this first before running link, category, tag, backup, or settings commands.

Commands

qjzd-nav auth --help
qjzd-nav auth login --help
qjzd-nav auth profile --help

Main workflows:

• qjzd-nav auth login
• qjzd-nav auth current
• qjzd-nav auth profile list
• qjzd-nav auth profile current
• qjzd-nav auth profile get <name>
• qjzd-nav auth profile use <name>
• qjzd-nav auth profile delete <name>
• qjzd-nav auth profile doctor

Common Flows

Login with password (uses RSA encryption):

qjzd-nav auth login \
  --profile default \
  --url https://nav.qjzd.online \
  --password <password>

Note: The password is encrypted with the server's public key before being sent.

Inspect and switch profiles:

qjzd-nav auth current
qjzd-nav auth profile list
qjzd-nav auth profile use production
qjzd-nav auth profile get default --json

Diagnose broken credentials:

qjzd-nav auth profile doctor
qjzd-nav auth profile delete production --force

Rules

• In non-interactive mode, qjzd-nav auth login requires --profile, --url, and --password.
• Use --json when another tool needs structured output.
• profile delete is destructive; use --force in non-interactive mode.
• Profile metadata lives in config, but secrets live in the system keyring.
• The CLI uses RSA encryption for password authentication.

Routing

• Use qjzd-nav-cli-content for links, categories, and tags.
• Use qjzd-nav-cli-operations for backups, restore, and settings.