What problem does it solve? Managing API credentials across multiple Frontline environments (production, staging, on-prem) is error-prone when done manually. This Skill explains how to authenticate the Frontline CLI with API keys, organize credentials into named profiles, and switch between environments without re-entering keys. ## Core Features & Use Cases - API Key Login: Store personal (USER) or account (GENERAL) API keys via frontline auth login, with keys kept in sync between the frontline and max binaries. - Named Profile Management: Create, list, switch, and remove profiles per environment, each with its own key and base URL. - Per-Call Overrides: Pass --api-key, --profile, or --base-url on any leaf command for one-off calls in scripts and CI without persisting credentials. - Use Case: A developer maintains dev and prod profiles, works against dev by default, then runs frontline auth profiles use prod to query production agents and workflows with the correct key automatically applied. ## Quick Start Log in to the Frontline CLI with my API key and create separate profiles for my staging and production environments.