What problem does it solve? Managing API keys, OAuth tokens, and service credentials scattered across machines is error-prone: tokens expire silently, flat config files drift out of sync, and secrets get leaked into logs. This Skill provides a single command surface (evo cred) to read, list, refresh, migrate, and sync credentials from a per-service folder store that compiles into a flat ~/.omelet.json. ## Core Features & Use Cases - Credential lookup and health checks: Read any value by dotted key path with evo cred get, and audit every credential's expiry and status with evo cred doctor. - Google OAuth lifecycle: Run first-time consent flows with evo cred auth and refresh short-lived access tokens for rclone, gmail, google-drive, and google-calendar with evo cred refresh. - Cross-machine sync: Push and pull the credentials folder through a private GitHub repo using evo cred sync, with automatic backups and permission hardening. - Use Case: Your rclone Google Drive token expired mid-backup. Run evo cred refresh --service rclone to renew the access token, recompile the flat config, and resume without touching any JSON by hand. ## Quick Start Ask the agent to check which credentials in the omelet store are expired by running evo cred doctor.
