Reminder to self: build an agent / Claude Code skill for envx so agents can drive it end-to-end without spelunking --help each time.
Why: setting up envx on a fresh macOS (arm64) machine today meant discovering the whole flow by hand.
What a skill should cover:
- Install:
curl -fsSL https://get.envx.sh | sh, or grab the envx-project/cli release tarball into ~/.local/bin when there's no sudo for /usr/local/bin.
- New-device onboarding:
envx gen -u <handle> -p <pass> → create an invite on an already-authed machine (envx invite create --project-id <id>) → envx invite accept <code> on the new device.
- Non-interactive
envx run story: keyring caching vs envx config set unsafe-password / password-command.
- Everyday commands:
link, run, list-projects, project add-user, whoami.
Filed by an agent at Alex's request.
Co-Authored-By: Claude Opus 4.8 (1M context) noreply@anthropic.com
Reminder to self: build an agent / Claude Code skill for
envxso agents can drive it end-to-end without spelunking--helpeach time.Why: setting up envx on a fresh macOS (arm64) machine today meant discovering the whole flow by hand.
What a skill should cover:
curl -fsSL https://get.envx.sh | sh, or grab theenvx-project/clirelease tarball into~/.local/binwhen there's no sudo for/usr/local/bin.envx gen -u <handle> -p <pass>→ create an invite on an already-authed machine (envx invite create --project-id <id>) →envx invite accept <code>on the new device.envx runstory: keyring caching vsenvx config set unsafe-password/password-command.link,run,list-projects,project add-user,whoami.Filed by an agent at Alex's request.
Co-Authored-By: Claude Opus 4.8 (1M context) noreply@anthropic.com