infra-setup
Non-user-invocable provider/setup reference for evo backend switching, prerequisite checks, and auth/install guidance.
npx skills add evo-hq/evo --skill infra-setup --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Infra Setup Use this when the user wants to change where experiments run: local worktrees, pool slots, or a remote provider such as Modal, E2B, Daytona, AWS, Azure, SSH, manual, or a custom dotted-path provider. ## Goals - Be explicit about the target backend/provider. - Check prerequisites before mutating evo config. - Never install provider SDKs silently. - Give one actionable auth command per provider. - Keep provider credentials separate from benchmark runtime env. ## Flow 1. Identify the target: - `worktree` or `pool` means local backends. - `modal`, `e2b`, `ssh:...`, or another remote spec means `backend=remote`. 2. If the target is remote, parse the provider choice the same way evo CLI does: - `modal` - `e2b` - `daytona` - `aws` - `azure` - `manual` - `ssh:user@host[:port]` - another built-in provider name - dotted import path for a custom provider 3. Check whether `evo` is on PATH and whether it is the expected `evo-hq-cli` package (`evo --version`). If the provider SDK is missing, evo's provider loader prints the provider-specific extra or SDK package to install; use that message rather than guessing. 4. For SDK-backed providers, verify the SDK import only when you can r
- Goals
- Flow
- Pre-assumptions
- Provider notes
evo config backend remote --provider <provider> --provider-config ... evo config backend worktree evo config backend pool --workspaces /abs/slot-a,/abs/slot-b
What does the infra-setup skill do?
Non-user-invocable provider/setup reference for evo backend switching, prerequisite checks, and auth/install guidance.
How do I install it?
Run `npx skills add evo-hq/evo --skill infra-setup --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From evo-hq/evo, a repository with 1,359 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.