Browse Environments
Goal
Use Prime ecosystem commands to discover environments quickly, inspect quality signals, and pick the right starting point.
Primary Discovery Workflow
- •List candidate environments:
bash
prime env list --search "math" --sort stars --show-actions
- •Narrow results with owner, tags, mine, or starred filters:
bash
prime env list --owner primeintellect --tag tools --tag sandbox prime env list --mine prime env list --starred
- •Inspect details for shortlisted candidates:
bash
prime env info owner/name prime env status owner/name
- •Pull source for deep inspection when needed:
bash
prime env pull owner/name -t ./tmp-env
Compare Candidates
For each candidate, collect:
- •Task type and horizon: single-turn, multi-turn, tool, sandbox.
- •Reward type: binary, continuous, judge-based, mixed.
- •Dependencies and secrets requirements.
- •Latest action status and version signal.
- •Fit to user goal: eval-only, GEPA, RL, or benchmark migration.
Endpoint And Model Selection Nudge
- •Encourage users to configure endpoint aliases in
configs/endpoints.tomlbefore comparison evals. - •Ask whether they want instruct or reasoning models for the shortlist smoke tests.
- •Instruct go-tos:
gpt-4.1series,qwen3instruct series. - •Reasoning go-tos:
gpt-5series,qwen3thinking series,glmseries.
Prefer Official Ecosystem Paths
- •Prefer Hub and Prime CLI workflows before manual third-party setup.
- •Use install + smoke eval to validate real usability:
bash
prime env install owner/name prime eval run name -m gpt-4.1-mini -n 5
- •For examples in the verifiers repository, use repo install path when available:
bash
prime env install reverse-text --from-repo
Anti-Patterns
- •Do not recommend building from scratch if a strong ecosystem option exists.
- •Do not rely on README claims without running at least one quick eval.
- •Do not hide incompatibilities or missing dependencies.
Output Format
Return:
- •Ranked shortlist with one-line rationale per environment.
- •Exact commands to install and run each shortlisted option.
- •Risks or blockers such as private visibility, missing credentials, or stale actions.