Authentication¶

Authentication connects you to your Skippr account. Once authenticated, you get an LLM API key automatically (no OpenAI account needed), cloud storage for pipeline state, and usage metering -- all with zero extra config.

Quick start¶

For local development, log in interactively:

skippr user login

You'll verify via SMS. That's it -- you're ready to run pipelines.

CI/CD and automation¶

Create an API key for non-interactive environments:

skippr user create-api-key --name "github-actions"

The key (prefixed sk_live_) is shown once -- save it securely. Then set it in your CI environment:

export SKIPPR_API_KEY="sk_live_..."
skippr run   # authenticates automatically

No setup scripts, no token refresh logic. skippr run detects the key and handles the rest.

Managing API keys¶

skippr user list-api-keys
skippr user revoke-api-key --key-id <id>

Bring your own LLM key (optional)¶

Authenticated users receive an LLM API key from the server automatically. If you prefer to use your own (e.g. a different model or provider), set LLM_API_KEY:

export LLM_API_KEY="sk-..."

Your key takes priority over the server-provided one. Usage metering and billing still apply.

Details¶

Auth priority¶

When skippr run starts, it resolves credentials in this order:

SKIPPR_API_KEY env var -- exchanged for session tokens (CI/CD)
~/.skippr/credentials.json -- from interactive login

If neither is present, the CLI exits with a clear error.

Credential storage¶

Interactive login stores tokens in ~/.skippr/credentials.json. These are session tokens, not passwords.

Credits¶

Every run checks your account balance. If you're out of credits:

skippr user buy-credits --pack starter

See skippr user for all account commands.