Dinox Auth (Login / Logout / Status)

CRITICAL — Before doing anything else, first read ../dino-shared/SKILL.md. It contains shared auth, output, and write-safety rules.

Use this skill when the user asks about logging in, logging out, or checking auth status.

Safety & Boundaries (Must Follow)

• Never ask the user to paste auth tokens into chat. For temporary auth, ask them to set DINOX_TOKEN in their own shell. For persistent auth, ask them to run dino auth login "<token>" in their own terminal session.
• DINOX_TOKEN takes precedence over saved config, may be a raw token or Bearer ..., and must never be echoed in chat or logs.
• Only run dino ... commands needed for this workflow. Do not run unrelated shell commands unless the user explicitly asks.
• logout is a write operation (it modifies local config). logout --clear-local-db is destructive. Show the exact command and get explicit confirmation before executing.

Intent Mapping

• status / empty args: show current auth and sync connectivity info
• login: guide the user to use DINOX_TOKEN or run login locally, then verify
• logout: clear saved token (and optionally the local DB)