Appearance
Login & whoami
login
Validate an API key and store it per profile.
Always set the API base URL
Pass --server explicitly (or type the correct API URL interactively). Do not accept a default like https://pm.elsai.io if it does not resolve. Use the API origin (SaaS: https://api.promptmanager-new.elsaifoundry.ai), not the browser console URL.
bash
pm-skills login --server https://api.promptmanager-new.elsaifoundry.ai --api-key "$PM_SKILLS_API_KEY"
pm-skills login --profile staging --server https://staging.example.comOn success, prints identity (email, orgs, accessible project count, key id) and writes ~/.pm-skills/config.json (mode 0600).
whoami
Re-validate the stored credential:
bash
pm-skills whoami
pm-skills whoami --jsonUse this when init fails with “No accessible projects” — confirm project count and membership.
logout
bash
pm-skills logout
pm-skills logout --profile stagingSkip login in CI
Env vars alone are enough:
bash
export PM_SKILLS_API_KEY=elsai_…
export PM_SKILLS_SERVER=https://api.promptmanager-new.elsaifoundry.ai
pm-skills pull --project "$PROJECT_ID"