New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Infra Setup

by evo-hq in evo-hq/evo

Non-user-invocable provider/setup reference for evo backend switching, prerequisite checks, and auth/install guidance.

Apache-2.0Auto-check passedAgent Workflows

Install Infra Setup

skills CLI
$ npx skills add evo-hq/evo --skill infra-setup -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install evo-hq/evo infra-setup --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/evo-hq/evo.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/evo/skills/infra-setup .claude/skills/infra-setup && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
infra-setup
GitHub stars
1.5k
Token cost
~1k tokens
SKILL.md length
508 words
Files
2 (incl. references)
Skills in repo
7
Repo updated
First seen
Licence
Apache-2.0

At a glance

Non-user-invocable provider/setup reference for evo backend switching, prerequisite checks, and auth/install guidance.

  • Works in 2 steps: Identify the target → If the target is remote, parse the…
  • Agent Workflows work in your project
  • SKILL.md covers Goals, Flow, Pre-assumptions and Provider notes
  • Calls uv, python and pipx

What it does

Infra Setup is an agent skill from evo-hq/evo. Non-user-invocable provider/setup reference for evo backend switching, prerequisite checks, and auth/install guidance.

Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/provider-matrix.md`).

It sits in Agent Workflows. The repository describes itself as: turns your codebase into an autoresearch loop — discovers what to measure, instruments the benchmark, then runs tree search with parallel subagents. The licence is Apache-2.0.

When your agent uses it

  • Agent Workflows work in your project

Example prompts

  • “/infra-setup”

Requirements

  • Python 3

Workflow steps

2 steps, taken from the first numbered list in SKILL.md.

  1. Identify the target
  2. If the target is remote, parse the provider choice the same way evo CLI does

What it can do on your machine

Read from SKILL.md and the folder at commit c70c04b. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • uv
    • python
    • pipx

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use uv and pipx, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Infra Setup loads about 1k tokens when it runs, and up to ~1.8k if it reads all its reference files. Until then it costs about 33 tokens; SKILL.md has 508 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~33
When it runs · the whole SKILL.md, loaded when a task matches
~1k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~1.8k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from evo-hq/evo at commit c70c04b, republished under its Apache-2.0 licence (© evo-hq). 508 words, ~1,012 tokens.

Download SKILL.mdSave it as .claude/skills/infra-setup/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
infra-setup
description
Non-user-invocable provider/setup reference for evo backend switching, prerequisite checks, and auth/install guidance.
evo_version
0.8.0

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
  1. 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.
  2. For SDK-backed providers, verify the SDK import only when you can run the check in the same environment that owns the evo executable. If missing, ask the user before installing it.
    • If evo was installed with uv tool or pip/venv, prefer the matching extra on evo-hq-cli:
      • uv-tool: uv tool install --reinstall 'evo-hq-cli[<provider-extra>]'
      • venv / pip: python -m pip install 'evo-hq-cli[<provider-extra>]'
    • If evo was installed with pipx, inject the provider SDK into the same evo-hq-cli environment:
      • pipx: pipx inject evo-hq-cli <provider-sdk>
  3. Check auth and show exactly one provider-specific auth command or setup step. Use references/provider-matrix.md.
  4. Once prerequisites are satisfied, run the explicit config command:
bash
evo config backend remote --provider <provider> --provider-config ...

Or for local backends:

bash
evo config backend worktree
evo config backend pool --workspaces /abs/slot-a,/abs/slot-b
  1. Be explicit that incomplete provider setup usually surfaces on evo new --remote <provider> ..., because that is where remote allocation and bootstrap actually happen.
  2. If the benchmark itself needs application keys, configure runtime env separately with evo env load <path> --all or evo env load <path> --allow KEY1,KEY2. Provider auth provisions the sandbox; runtime env is what benchmark/gate processes see.
Show full SKILL.md (175 more words)Show less

Pre-assumptions

Before trying to switch a workspace to a remote provider, confirm the basics:

  • the target backend is clear from the user's request; only ask if the intent is genuinely ambiguous between worktree, pool, and remote
  • the machine running evo has the right provider SDK or transport installed
  • the user has auth for that provider available now, not "somewhere else"
  • the provider-specific minimum config exists
    • modal: auth + optional config
    • e2b: API key + optional config
    • daytona: API key and API URL/target if needed
    • aws: creds, region, image, SSH key pair/private key, and usually network config
    • azure: subscription, resource group, region, SSH key/private key, and VM/image choices
    • ssh: reachable host, working SSH user, and key/port if needed
    • manual: reachable remote endpoint URL and bearer token
  • for SSH-backed VM providers, the guest assumptions are plausible before allocation:
    • the image enables SSH
    • the SSH user matches the image
    • the image architecture matches the selected instance type
    • the host can run evo's remote workspace runtime

Provider notes

See references/provider-matrix.md for the compact provider summary, common config, and provider-specific setup/auth command.

© evo-hq, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (references) in plugins/evo/skills/infra-setup of evo-hq/evo.

  • SKILL.md
  • references/provider-matrix.md

Open the folder on GitHubat commit c70c04b

Compare with similar skills

Infra Setup next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Infra Setup compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Infra Setup this skillevo-hq/evo1.5k—~1kAutomated safety check: PassApache-2.0
MCP Server Builderanthropics/skills180k63 repos~2.3kAutomated safety check: PassApache-2.0
Hook Development for Claude Code Pluginsanthropics/claude-plugins-official38k10 repos~4.1kAutomated safety check: NotesApache-2.0
Using Superpowersfarm-fe/farm5.6k35 repos~1.4kAutomated safety check: PassMIT
Executing Plans Inlineobra/superpowers297k2 repos~5.1kAutomated safety check: PassMIT
Skill CreatorAzure/azqr79589 repos~8.2kAutomated safety check: PassApache-2.0

Similar skills

  • MCP Server Builder

    anthropics/skills

    Official

    Guides the design and implementation of Model Context Protocol servers in TypeScript or Python, from tool naming and error messages to evaluation.

    180k GitHub starsUsed in 63 repos~2.3k tokens
    Agent WorkflowsAuto-check passed

  • Hook Development for Claude Code Plugins

    anthropics/claude-plugins-official

    Official

    Explains how to write Claude Code plugin hooks, both prompt-based checks and bash commands, for events such as PreToolUse, Stop and SessionStart.

    38k GitHub starsUsed in 10 repos~4.1k tokens
    Agent WorkflowsAuto-check: notes

  • Using Superpowers

    farm-fe/farm

    A skill your agent uses when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions

    5.6k GitHub starsUsed in 35 repos~1.4k tokens
    Agent WorkflowsAuto-check passed

  • Executing Plans Inline

    obra/superpowers

    Has the agent carry out an implementation plan itself, task by task in the current session, keeping a ledger, proving each step with a test and ending with one whole-branch review.

    297k GitHub starsUsed in 2 repos~5.1k tokens
    Agent WorkflowsAuto-check passed

  • Skill Creator

    Azure/azqr

    Official

    Create new skills, modify and improve existing skills, and measure skill performance.

    795 GitHub starsUsed in 89 repos~8.2k tokens
    Agent WorkflowsAuto-check passed

  • Claude Code Agent Development

    anthropics/claude-plugins-official

    Official

    Explains how to write agents for Claude Code plugins: the markdown file with YAML frontmatter, trigger descriptions, model and color settings, and system prompt design.

    38k GitHub starsUsed in 7 repos~2.8k tokens
    Agent WorkflowsAuto-check passed

More from evo-hq/evo

  • Discover

    evo-hq/evo

    Initialize evo for the current repository by exploring the codebase, proposing unexplored optimization dimensions, constructing the benchmark inside a baseline worktree, and running the first…

    1.5k GitHub stars~12k tokensUpdated 4 days ago
    Auto-check: notes

  • Finetuning

    evo-hq/evo

    This skill should be used when picking or diagnosing a training move (SFT, LoRA, DPO/KTO/ORPO, RFT, GRPO/PPO/RLOO, RLHF), or when the user mentions fine-tuning, post-training, training recipe…

    1.5k GitHub stars~4.5k tokensUpdated 4 days ago
    Auto-check passed

  • Report

    evo-hq/evo

    Read-only evo run reporting. An agent skill from evo-hq/evo.

    1.5k GitHub stars~1k tokensUpdated 4 days ago
    Auto-check passed

  • Ship

    evo-hq/evo

    Land the winning experiment from an evo run as a clean, mergeable change -- open a PR when the repo has a remote, otherwise merge into the working branch.

    1.5k GitHub stars~1.7k tokensUpdated 4 days ago
    Auto-check passed

  • Optimize

    evo-hq/evo

    Drive structured autoresearch iteration after evo:discover and the baseline commit.

    1.5k GitHub stars~13k tokensUpdated 4 days ago
    Auto-check passed

  • Subagent

    evo-hq/evo

    Protocol that evo optimization subagents follow when dispatched from /optimize.

    1.5k GitHub stars~7.1k tokensUpdated 4 days ago
    Auto-check: notes

Categories

Questions about Infra Setup

What does Infra Setup do?

Non-user-invocable provider/setup reference for evo backend switching, prerequisite checks, and auth/install guidance. Infra Setup is an agent skill from evo-hq/evo. Non-user-invocable provider/setup reference for evo backend switching, prerequisite checks, and auth/install guidance.

When should I use Infra Setup?

Infra Setup fits situations like: agent Workflows work in your project.

How do I install Infra Setup in Claude Code?

Run `npx skills add evo-hq/evo --skill infra-setup -a claude-code`. Or copy the skill folder (plugins/evo/skills/infra-setup in evo-hq/evo) into .claude/skills/infra-setup in your project. Claude Code loads it when a task matches its description.

How do I install Infra Setup in Codex?

Run `npx skills add evo-hq/evo --skill infra-setup -a codex`. Or copy the skill folder (plugins/evo/skills/infra-setup in evo-hq/evo) into .agents/skills/infra-setup in your project. Codex loads it when a task matches its description.

Can I use Infra Setup in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add evo-hq/evo --skill infra-setup -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/infra-setup, .gemini/skills/infra-setup, .github/skills/infra-setup and .opencode/skills/infra-setup in your project.

What does Infra Setup need to run?

Going by SKILL.md and its folder, Infra Setup needs the command-line tools its instructions call (uv, python and pipx). Our summary lists: Python 3.

Does Infra Setup access the network?

SKILL.md contains no URLs. Its commands use uv, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Infra Setup safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Infra Setup use?

Infra Setup is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Infra Setup use?

About 1k tokens (SKILL.md is roughly 4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 752 tokens, read only when the agent opens those files.

What are the alternatives to Infra Setup?

Skills that share tags, products or a category with Infra Setup: MCP Server Builder (anthropics/skills, 180k stars), Hook Development for Claude Code Plugins (anthropics/claude-plugins-official, 38k stars), Using Superpowers (farm-fe/farm, 5.6k stars) and Executing Plans Inline (obra/superpowers, 297k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Infra Setup?

evo-hq (a GitHub organization) maintains it in evo-hq/evo, which has 1,466 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on October 5, 2026.

Source: evo-hq/evo on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.